IN THIS ARTICLE
- MORE INFORMATION
System administrators and developers must consider security and authentication issues because users who are not authorized can destroy, steal, or otherwise gain access to data. This article gives you an overview of Microsoft Desktop Engine (MSDE) Security and Authentication and some helpful tips about how to make your data more secure.
To learn more about Users, Groups, and Roles, see the SQL Server Books Online. To add Users, Groups, and Roles on an MSDE database, use the OSQL utility.
To change the SA account password on your MSDE database, follow these steps:
- On the computer that is hosting the instance of MSDE that you are connecting to, open a command prompt window.
- Type the following command, and then press ENTER:
osql -U sa
This command connects you to the local, default instance of MSDE by using the SA account.
- Type the following commands on separate lines, and then press ENTER:
Note Replace 'mynewpassword' with the new password.
Note that you receive the following message, which indicates that your password was changed successfully:Password changed.
325003 How to manage the SQL Server Desktop Engine (MSDE 2000) by using the Osql utilityFor more information, click the following article number to view the article in the Microsoft Knowledge Base:
176377 Accessing SQL Server with Integrated Security from ASP
Microsoft Security Bulletin MS02-034
Note We recommend that you install SQL Server 2000 Service Pack 3 (SP3) or SQL Server 2000 SP4. Service packs include more updates, and Microsoft Security Bulletin MS02-034 is included in the two service packs. For more information about how to obtain SQL Server 2000 SP3 or SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
This is a cumulative patch that includes the functionality of all of the patches that have been released previously for SQL Server 2000. Also, this patch fixes the following three newly discovered vulnerabilities that affect SQL Server 2000 and SQL Server Desktop Engine (also known as MSDE 2000). (These vulnerabilities do not affect any previous versions of SQL Server or MSDE.):
- A buffer overrun vulnerability in a procedure that is used to encrypt SQL Server credential information. A user who is not authorized can use this vulnerability to gain significant control over the database. It is possible for the user to gain control of the server itself, but this depends on the account that SQL Server uses.
- A buffer overrun vulnerability in a procedure that relates to the bulk insert of data in SQL Server tables.
A user who is not authorized can use this vulnerability to gain significant control over the database. It is possible for the user to gain control of the server itself.
- An administrative credentials elevation vulnerability that occurs because of incorrect rights on the Registry key that stores the SQL Server service account information.A user who is not authorized can use this vulnerability to gain more rights on the system than system administrator has give to the user's account. It is possible for the user to get the same rights as the operating system. For more information, visit the following Microsoft Web site:Microsoft Security Bulletin MS02-035
SQL Server 2000 also includes the ability to record an unattended install to the Setup.iss file without your having to actually perform an installation. The administrator who sets up the computer running SQL Server can give a password to the installation routine under the following circumstances:
- If you set up SQL Server to have Mixed Mode Authentication, you must give a password for the SQL Server administrator account (the SA account).
- Whether you run SQL Server in Mixed Mode or in Windows Authentication Mode, you can require a User ID and a password to start up a SQL Server service account.
This command parameter causes MSDE to install with Mixed Mode authentication. With this authentication mode, you can connect to MSDE by using Windows Authentication or SQL Server Authentication.
Note By default, for Windows NT and later, MSDE installs by using Windows Authentication. On computers running Windows 98, MSDE uses SQL authentication.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
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
- 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\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.
For more information, visit the following Microsoft Web sites:
Security & Privacy
Managing Microsoft SQL Server Security with Microsoft Access
SQL Server 2000 Security White PaperFor more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
259710 PRB: SQL Server Agent Fails to start on Windows 9x when you change the SA password
319930 How to connect to Microsoft Desktop Engine
313418 PRB: Unsecured SQL Server with blank (NULL) SA password leaves vulnerability to a worm
285097 How to change the default login authentication mode to SQL while installing SQL Server 2000 Desktop Engine by using Windows Installer
248683 Microsoft Data Engine Security recommendations for ISVs
321698 Cannot connect to MSDE 2000 by using ADO.NET with SQL Authentication
Article ID: 325022 - Last Review: Jun 19, 2014 - Revision: 1