I have asked this before, but it was a while back and then the project got
put on hold, and I can't find the replies - sorry.
Is there any problems (operationally wise, or conflict wise) with putting
MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
server also has Exchange 2000 and ISA 2000 installed on it)?
I can obviously restrict the memory it can use so that's not a problem, but
I wondered if it would create problems or serious performance issues for the
DC.
Also, if it is OK to install on a DC, is the installation straightforward or
are there any special switches or settings I should use? Or do I just do a
plain install as I would on any machine?
Thanks
Keith
Anyone?
"Keith" <@..> wrote in message news:ehizqISKEHA.3436@.tk2msftngp13.phx.gbl...
> I have asked this before, but it was a while back and then the project got
> put on hold, and I can't find the replies - sorry.
> Is there any problems (operationally wise, or conflict wise) with putting
> MSDE 2000 A on a Windows 2000 Server which is a domain controller (the
> server also has Exchange 2000 and ISA 2000 installed on it)?
> I can obviously restrict the memory it can use so that's not a problem,
but
> I wondered if it would create problems or serious performance issues for
the
> DC.
> Also, if it is OK to install on a DC, is the installation straightforward
or
> are there any special switches or settings I should use? Or do I just do
a
> plain install as I would on any machine?
> Thanks
> Keith
>
|||A no-one responded yet...
Yes, you should be fine. One thing to consider is that your service account is now a domain account. I.e., a
potential security issue. (This is because a DC doesn't have any local accounts.)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith" <@..> wrote in message news:e2TJLgDLEHA.3704@.TK2MSFTNGP11.phx.gbl...
> Anyone?
>
> "Keith" <@..> wrote in message news:ehizqISKEHA.3436@.tk2msftngp13.phx.gbl...
> but
> the
> or
> a
>
sql
Showing posts with label controller. Show all posts
Showing posts with label controller. Show all posts
Wednesday, March 21, 2012
Monday, March 19, 2012
MSDE newbie question: connection strings
I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
domain controller.
If I access this database via ADO, how do I construct the connection
string? As I understand it, this is of the form:
Provider=SQLOLEDB; Data Source=server_name; Initial
Catalog=database_name; User ID=username; Password=password;
Is the server name just the name or IP address of the PC running MSDE?
Are there any other subtleties I should be aware of?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:OuUGwZwQEHA.3580@.TK2MSFTNGP11.phx.gbl...
> I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
> domain controller.
> If I access this database via ADO, how do I construct the connection
> string? As I understand it, this is of the form:
> Provider=SQLOLEDB; Data Source=server_name; Initial
> Catalog=database_name; User ID=username; Password=password;
> Is the server name just the name or IP address of the PC running MSDE?
> Are there any other subtleties I should be aware of?
if the MSDE instance has been installed as the default intance, it's name
will just be the ComputerName and/or it's IP address... if it has been
installed as a named instance, it's name will be
ComputerName\InstanceName...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
domain controller.
If I access this database via ADO, how do I construct the connection
string? As I understand it, this is of the form:
Provider=SQLOLEDB; Data Source=server_name; Initial
Catalog=database_name; User ID=username; Password=password;
Is the server name just the name or IP address of the PC running MSDE?
Are there any other subtleties I should be aware of?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:OuUGwZwQEHA.3580@.TK2MSFTNGP11.phx.gbl...
> I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
> domain controller.
> If I access this database via ADO, how do I construct the connection
> string? As I understand it, this is of the form:
> Provider=SQLOLEDB; Data Source=server_name; Initial
> Catalog=database_name; User ID=username; Password=password;
> Is the server name just the name or IP address of the PC running MSDE?
> Are there any other subtleties I should be aware of?
if the MSDE instance has been installed as the default intance, it's name
will just be the ComputerName and/or it's IP address... if it has been
installed as a named instance, it's name will be
ComputerName\InstanceName...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE Named Service Connection Problem
I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
patched), and operating as the only domain controller. I have also run the
IISLockdown Tool on this server.
I originally ran setup using the following parameters:
setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
with the following parameters:
setup sapwd="xxxxxxx" instancename=WSUS
I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
connect to any service and appears in the task bar with a blank icon. When I
open the Service Manager, all fields (server,services) are blank. Pressing
start button will give me:
"The service control action cannot be completed as no
service has been selected"
I entered the server's name in the server field, but no services can be
resolved.
I see MSSQL$WSUS service has started. Further down I noticed
SQLAgent$TESTING service had not started. I started that up, but no change.
Also tried to startup MSSQLServerADHelper but it gave me an error.
I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
keys and SQL Server folder under Program Files.
I again re-installed using the sapwd and instancename parameters but to no
avail.
Can anyone tell me how I can get this working properly?
Thanks!
You could have tried to enter "ComputerName\WSUS" in the service manager
when showed nothing in the server list, and then clicked "Start" button.
Somethimes, for some reason, service manager could not detect any running
SQL/MSDE on the computer/network.
"stantm1" <stantm1@.discussions.microsoft.com> wrote in message
news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
> patched), and operating as the only domain controller. I have also run the
> IISLockdown Tool on this server.
> I originally ran setup using the following parameters:
> setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
> I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
> with the following parameters:
> setup sapwd="xxxxxxx" instancename=WSUS
> I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
> connect to any service and appears in the task bar with a blank icon. When
> I
> open the Service Manager, all fields (server,services) are blank. Pressing
> start button will give me:
> "The service control action cannot be completed as no
> service has been selected"
> I entered the server's name in the server field, but no services can be
> resolved.
> I see MSSQL$WSUS service has started. Further down I noticed
> SQLAgent$TESTING service had not started. I started that up, but no
> change.
> Also tried to startup MSSQLServerADHelper but it gave me an error.
> I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
> keys and SQL Server folder under Program Files.
> I again re-installed using the sapwd and instancename parameters but to no
> avail.
> Can anyone tell me how I can get this working properly?
> Thanks!
|||Thanks, Norman. I'll give it a try.
"Norman Yuan" wrote:
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
>
|||Actually it found the instance of sql server just fine. My machine was in
the list of sql servers but when i try to connect to it i have problems.
Just to let you know im using Windows Authentication and i am an
administrator on this machine.
Brent
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:usGQBJbLGHA.3496@.TK2MSFTNGP14.phx.gbl...
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
patched), and operating as the only domain controller. I have also run the
IISLockdown Tool on this server.
I originally ran setup using the following parameters:
setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
with the following parameters:
setup sapwd="xxxxxxx" instancename=WSUS
I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
connect to any service and appears in the task bar with a blank icon. When I
open the Service Manager, all fields (server,services) are blank. Pressing
start button will give me:
"The service control action cannot be completed as no
service has been selected"
I entered the server's name in the server field, but no services can be
resolved.
I see MSSQL$WSUS service has started. Further down I noticed
SQLAgent$TESTING service had not started. I started that up, but no change.
Also tried to startup MSSQLServerADHelper but it gave me an error.
I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
keys and SQL Server folder under Program Files.
I again re-installed using the sapwd and instancename parameters but to no
avail.
Can anyone tell me how I can get this working properly?
Thanks!
You could have tried to enter "ComputerName\WSUS" in the service manager
when showed nothing in the server list, and then clicked "Start" button.
Somethimes, for some reason, service manager could not detect any running
SQL/MSDE on the computer/network.
"stantm1" <stantm1@.discussions.microsoft.com> wrote in message
news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>I installed SQL 2000 MSDE 2000RelA on Win2K Adv. Server w/ Win2K SP4 (fully
> patched), and operating as the only domain controller. I have also run the
> IISLockdown Tool on this server.
> I originally ran setup using the following parameters:
> setup sapwd="xxxxxxx" and SQL Service Manager was connecting properly.
> I later uninstalled MSDE 2000 RelA and re-installed (no reboot in between)
> with the following parameters:
> setup sapwd="xxxxxxx" instancename=WSUS
> I then installed SQL2000 MSDE SP4, and the Service Manager can no longer
> connect to any service and appears in the task bar with a blank icon. When
> I
> open the Service Manager, all fields (server,services) are blank. Pressing
> start button will give me:
> "The service control action cannot be completed as no
> service has been selected"
> I entered the server's name in the server field, but no services can be
> resolved.
> I see MSSQL$WSUS service has started. Further down I noticed
> SQLAgent$TESTING service had not started. I started that up, but no
> change.
> Also tried to startup MSSQLServerADHelper but it gave me an error.
> I then uninstalled SQL2000 MSDE and deleted each of the relevant Registry
> keys and SQL Server folder under Program Files.
> I again re-installed using the sapwd and instancename parameters but to no
> avail.
> Can anyone tell me how I can get this working properly?
> Thanks!
|||Thanks, Norman. I'll give it a try.
"Norman Yuan" wrote:
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
>
|||Actually it found the instance of sql server just fine. My machine was in
the list of sql servers but when i try to connect to it i have problems.
Just to let you know im using Windows Authentication and i am an
administrator on this machine.
Brent
"Norman Yuan" <NotReal@.NotReal.not> wrote in message
news:usGQBJbLGHA.3496@.TK2MSFTNGP14.phx.gbl...
> You could have tried to enter "ComputerName\WSUS" in the service manager
> when showed nothing in the server list, and then clicked "Start" button.
> Somethimes, for some reason, service manager could not detect any running
> SQL/MSDE on the computer/network.
> "stantm1" <stantm1@.discussions.microsoft.com> wrote in message
> news:5BF4C64E-8D57-4CC1-837B-CB143CCB6329@.microsoft.com...
>
Friday, March 9, 2012
MSDE installation/connection issues
I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured to
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg
> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg
> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Subscribe to:
Posts (Atom)