The postings on this site are my own and do not represent my Employer's positions, advice or strategies.

LifeAsBob

  Saturday, November 18, 2017

lifeasbob.com




Home
Blog
bob tech
Calendar
Contact Bob
Pictures
VW Buses
HomeBrew
Cook Book

 

Halloween_PumkinPatch 2007 _71.JPG

  bob Links
Formatting Overview
I think this would be a good time for a beer. - Franklin D. Roosevelt
Wider View Insert

Cluster
DOS
IBM - AS400
MOM
Performance Counters
Service Broker
SQL Server
     Temporary Database
     Views
     Backup
     SQL Mail
     DTS - Data Transformation Services
     Memory
     Security
     Excel
     Jobs SQL Agent
     MSDE
     Install
     DBCC
     User Management
     System Databases
     BCV
     Deadlocks
     Temp Tables
     Find the physical se...
     Enable xp_cmdshell
     Intermittent Connect...
     Connection String Pr...
     Login Error ( State)...
     Turn Default Tracing...
     Re-index fails when ...
     SMO AND DMO
     Tracing of Errors
     Extra carriage Retur...
     Query to find Object...
     Named Instance Port ...
     Adding Domain Login ...
     Rename Logical File ...
     Error 3624 Delete st...
     SQL DMO Error 21776
     NetworkConnections
     SQL Server Service m...
     Trace Flags for Dead...
     Change Server Name
     Alternate to Count(*...
Windows OS

Insert Category

Will be added as a sub-category of, SQL Server
NetworkConnections
MSDE Does not accept network Connections. http://support.microsoft.com/default.aspx?scid=kb;EN-US;q285097 SUMMARY When using SQL Server 2000 Desktop Engine Windows Installer Merge Modules, an option named SECURITYMODE can be used to change the default login authentication mode from Windows NT authentication to SQL authentication. MORE INFORMATION The authentication mode can also be changed at the time of the installation by using the following command-line setup parameter for SQL Server 2000 Desktop Engine: SECURITYMODE=SQL For more information, refer to the "3.1.4 Desktop Engine Setup Parameters" section in the Readme.txt file for SQL Server 2000 Desktop Engine installation. By default, SQL Server 2000 installation sets the login authentication to Windows authentication mode. This can be easily changed after the install by connecting to the server by using any installation of SQL Server Enterprise Manager (SEM). For more information regarding changing authentication mode by using SEM, refer to the "Authentication" topic in SQL Server Books On-Line. Another way to change the security mode after installation is to stop SQL Server and set the appropriate registry key for your installation: Default instance: HKLM\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode Named instance: HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name\MSSQLServer\LoginMode to 0 or 2 for mixed-mode or 1 for integrated. (Integrated is the default setup for the SQL Server 2000 Data Engine.) Note The 0 and 2 values have the same functionality. They both set the security to mixed-mode. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To set this key to mixed-mode, follow these steps: Stop SQL Server and all related services, such as SQLAgent, from the Services control panel. Click Start, click Run, type regedt32, and then click OK. Find the HKEY_LOCAL_MACHINE window on the local computer. Navigate to the following registry key for the default instance: HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer Navigate to the following registry key for a named instance: HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name\MSSQLServer\LoginMode On the right-hand pane, find the value LoginMode and double-click it. In the DWORD Editor window, set the value to 0 or 2. Also, make sure that the Hex radio button is selected. Click OK. Restart SQL Server and SQL Server Agent services for this change to take effect.