Re: Strong SA Password
From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 12/21/04
- Previous message: Kevin McDonnell [MSFT]: "Re: Sql users are redirected to wrong databases"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 21 Dec 2004 01:17:50 GMT
Hi Chuck,
If you're using OSQL to connect /run queries then you should type the
password . Eg.
OSQL -SmyServer -PmyPassword
Depending on how MSDE was installed with what Netlibs, your choices may be
limited. By default,
only Shared memory is used.
Things to verify:
1. Service is actually running. Check the Services applet for
MSSQL$Instance
2. Try stopping and re-starting the service. Check the NT Application
event logs for errors.
3. Try using a test ODBC DSN to connect to the server. This will give you
a better error message than OSQL.
Passwords.
During setup should have supplied a password for the 'sa' account. It
should never be blank or easy to guess like 'password'
setup SAPWD="AStrongSAPwd"
The same rules apply to SQL as they would for choosing a password policy
for your Windows domain.
http://www.microsoft.com/smallbusiness/gtm/securityguidance/articles/enforce
_strong_passwords.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
- Previous message: Kevin McDonnell [MSFT]: "Re: Sql users are redirected to wrong databases"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|