100supersport
Posts: 3
Joined: 29.Dec.2002
Status: offline
|
Hi, Here is some info from Microsoft KB:
How To Verify and Change the MSDE System Administrator Password
View products that this article applies to.
Article ID : 322336
Last Review : July 1, 2004
Revision : 1.0
On This Page
SUMMARY
How to Verify If the SA Password is Blank
How to Change Your SA Password
How to Determine or Change Your Authentication Mode
Security Best Practices for a SQL Server Installation
REFERENCES
APPLIES TO
SUMMARY
This step-by-step article discusses the steps you can use to change the SQL Server sa (system administrator) password.
You can configure Microsoft SQL Server Desktop Engine (MSDE) versions 2000, or earlier, to run in Mixed Authentication mode. The sa account is created during the installation process and the sa account has full rights in the SQL Server environment. By default, the sa password is blank (NULL), unless you change the password when you run the MSDE Setup program. To conform with the best security practices, you must change the sa password to a strong password at the first opportunity.
Back to the top
How to Verify If the SA Password is Blank
1. On the computer that is hosting the instance of MSDE to which you are connecting, open a command prompt window.
2. At the command prompt, type the following command, and then press ENTER:
osql -U sa
This connects you to the local, default instance of MSDE by using the sa account. To connect to a named instance installed on your computer type:
osql -U sa -S servername\instancename
You are now at the following prompt:
Password:
3. Press ENTER again. This will pass a NULL (blank) password for sa.
If you are now at the following prompt, after you press ENTER, then you do not have a password for the sa account:
1>
Microsoft recommends that you create a non-NULL, strong password to conform with security practices.
However, if you receive the following error message, you have entered an incorrect password. This error message indicates that a password has been created for the sa account:
"Login Failed for user 'sa'."
The following error message indicates that the computer that is running SQL Server is set to Windows Authentication only:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection.
You cannot verify your sa password while in Windows Authentication mode. However, you can create a sa password so that your sa account is secure in case your authentication mode is changed to Mixed Mode in the future.
If you receive the following error message, SQL Server may not be running or you may have provided an incorrect name for the named instance of SQL Server that is installed:
[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen (Connect()).
Back to the top
How to Change Your SA Password
1. On the computer that is hosting the instance of MSDE to which you are connecting, open the command prompt window.
2. Type the following command, and then press ENTER:
osql -U sa
At the Password: prompt, press ENTER if your password is blank or type the current password. This connects you to the local, default instance of MSDE by using the sa account. To connect by using Windows authentication, type this command: use osql -E
3. Type the following commands, on separate lines, and then press ENTER:
sp_password @old = null, @new = 'complexpwd', @loginame ='sa'
go
NOTE: Make sure that you replace "complexpwd" with the new strong password. A strong password includes alpha-numeric and special characters, and a combination of upper and lower case characters.
You will receive the following informational message, which indicates that your password was changed successfully:
Password changed.
Regards,
Steve
|
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
Password to SA on MSDE - 
RE: Password to SA on MSDE - 
RE: Password to SA on MSDE - ![[Smile]](/image/smiles/smile.gif)
From memory I had to change the port that SQL was using, so that you don't have 2 instances of SQL server that try to use the same port. I think they should automatically use the next available port, but I thought I'd just mention what I had to do go gain access to my FW MSDE. (I changed the TCP port that the normal SQL server listens to so that it's out of the way)
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread