By default, the value of the LoginMode Windows registry subkey is set to 1 for Windows Authentication. To turn on Mixed Mode authentication after you install MSDE, you must change this value to 2. The location of the LoginMode subkey depends on whether you installed MSDE as the default MSDE instance or as a named instance.
If you installed MSDE as the default instance, the LoginMode subkey is located in the following registry subkey:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode
If you installed MSDE as a named instance, the LoginMode subkey is located in the following registry subkey:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name \MSSQLServer\LoginMode
To change the value of LoginMode to 2, follow these steps:
In Control Panel, open the Services tool, and then stop MSSQLSERVER and all other related services (such as SQLSERVERAgent).
On the Start menu, click Run, type regedt32, and then click OK to start Registry Editor.
Locate either of the following subkeys (depending on whether you installed MSDE as the default MSDE instance or as a named instance):
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\
-or-
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Instance Name\MSSQLServer\
In the right pane, double-click the LoginMode subkey.
In the DWORD Editor dialog box, set the value of this subkey to 2, verify that the Hex option is selected, and then click OK.
Restart the MSSQLSERVER service and the SQLSERVERAgent service for this change to take effect.
======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Thank you! I think that is exactly what I needed. I changed the mode, but am still not able to log onto the sql server The network is set up in an odd way - the sql server I'm trying to connect to is actually on a workstation, with an MSDE installation. I am trying to connect through EM installed on the server. The workstation in not joined to the domain. I am not familiar with networking, or how that might affect the situation - maybe it won't work because of that?
The ODBC driver would connect using sql authentication after following your directions, so it must have worked. Thank you so much
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.