I’ve installed and used MSDE enough times to realize that these 2 steps / options are quite important to me, and often forgotten during the command line install.
1. Allow mixed mode authentication
By default, the MSDE setup allows only Windows authentication, even though a strong password is supplied with the command line install.
Modifying this after install requires a change to a registry key. Depending on whether or not you specified an instance name, it would require a change of value from 1 to 2 in:
HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode (if default instance)
or
HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name \MSSQLServer\LoginMode (if named instance)
To avoid this, I use the SECURITYMODE=SQL parameter in the command line.
2. Allow TCP/IP connection
The default install actually prevents any TCP/IP connection to MSDE, meaning you cannot remotely connect to it from another computer in Enterprise Manager, nor connect to it from applications outside the local computer. I understand that MSDE is just for development purposed, but sometimes I just need to test application connectivity from a remote machine.
To change this after installation requires you to run a file called SVRNETCN.EXE within
C:\Program Files\Microsoft SQL Server\80\Tools\Binn (if default install, otherwise similar directory based on your install), where you add the TCP/IP protocol
To set this up at install, I use the DISABLENETWORPROTOCOLS=0 parameter in the command line.
So my usual MSDE command line installation goes like this:
setup sapwd=”” securitymode=”sql” disablenetworkprotocols=”0″
Saves me the time of having to do those extra steps afterwards.
Technorati Tags : MSDE, Microsoft Desktop Engine
Powered By Qumana
Average Rating: 4.4 out of 5 based on 153 user reviews.
RSS