SQLEXPRESS SA default password

This site is best viewed in a modern browser with JavaScript enabled.

alexsts

Hey guys,
just for fun I run installation of SQLEXPRESS.
To my surprise it went relatively painless. I can connect to it but only with windows authentication.:eek:
Does anyone know what default password for SA is, since it did not asked me to provide one during installation....

NogDog

Maybe no password?

alexsts

nope.
As far as I know Microsoft fixed that bug back in 2005. You can not use blank as password unless you unchecked couple boxes in settings.

svidgen

I think you can just change it. Log in (using windows auth), expand Security / Logins, right click the sa user, and just enter a new password.

svidgen

That said, you shouldn't ever need to use the sa account. You should really just create an account for each or application or "function" that needs access. OR, if all the apps run locally, use Trusted_Connection=True; in the connection string and give the appropriate privileges the account (the IIS user, for instance) that runs the application.

alexsts

Stickman,
do you think I would post question here if SQLEXPRESS allowed me to just change password or even create new user?:rolleyes:
Eat some meat to calm your anger...

That is the reason why I want to connect to it as SA. So I could create new user and go on from there.
Basically right now I have database where I can not do anything but just to connect to it using windows authentication and that is it. Read only access.

svidgen

alexsts;1210388 wrote:
Stickman,
do you think I would post question here if SQLEXPRESS allowed me to just change password or even create new user?:rolleyes:
Eat some meat to calm your anger...

That is the reason why I want to connect to it as SA. So I could create new user and go on from there.

Yes, that's precisely how you attract help in a forum ...

All I can say then is, you're doing it wrong. Good luck.

svidgen

Damn my better nature ...

http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/16706dec-209f-42c4-8dc7-4ee4dd5df482/

This little security issue is generally avoided during installation, at which point windows auth should have been selected as the authentication mode, and at which point your user would have been granted full administrative access to to instance. In the even that you don't have admin access, the more appropriate question is really, "why don't i have admin access to my sql server instance?"

And to that I say, reinstall the software, and pay close attention to your initial configuration options. Use windows auth. And be sure to add your user as an admin when/if prompted to do so.

alexsts

That what was my choice during installation of the package.
SQL Express is a part of that package and I cannot remove it.
For me it is just a matter of curiosity about next Microsoft screw ups rather than necessity since I am using full version of SQL for all my projects...
So, does anyone knows what is default SA password for SQLEXPRESS 2008

alexsts

and all suggestions how to change SA password fail right here:
1. Go to SQL Server Properties/Security tab and change the mode to SQL Server authentication mode

Produces error message: access denied; User not authorized to perform this action.

svidgen

If you read the link, the prevalent belief is there, if you choose windows auth, the SA account isn't even enabled. If I recall, the one time I installed it w/ SQL auth, I was prompted to pick the SA password.

This isn't the M$ screwup you think it is. It's user error.

And I find this hard, if not impossible, to believe:

SQL Express is a part of that package and I cannot remove it.

You should always have the option to remove it from the add/remove software pane in the control panel. If it's not there, you don't even have the software installed. If it was part of another software packed, it's likely that have the embedded version installed.

alexsts

svidgen;1210397 wrote:
.. the prevalent belief is ...

That is all what it is and it is not always based on actual software behavior.
And by the way if you did not notice original question was about SQLEXPRESS but most of the posting refer to straight SQL 2008 (R2) which is not exactly the same. Yes both using same engine but functionality and some of the other characteristics completely different.

Package also build by Ms, if I remove one it automatically kills entire package. I tried more than once already.
And on 3 different systems to make sure that I did not missed option to enable SA account.
So problem is not between chair and keyboard.

svidgen

Whelp. If I have time outside the office, I'll re-run the installation so I have concrete steps to give you. Maybe someone who has them committed to memory can chime in meanwhile ...

svidgen

alexsts;1210398 wrote:
And by the way if you did not notice original question was about SQLEXPRESS but most of the posting refer to straight SQL 2008 (R2) which is not exactly the same.

The thread I linked pertained to "SQL Server 2008 R2 Express."

ADDENDUM: And it should be noted, the only significant differences between the Express and edition and the "normal" editions are arbitrary memory, disk, and CPU core limitation. Just about everything else should function identically.

alexsts

svidgen;1210401 wrote:
... should function identically.

Once again should off, would off, could off but in reality is not.
Thanks for your time and efforts.
See you in cyberspace.

svidgen

I maintain: user error.

I've certainly never had an issue with it!

alexsts

ok, thanks.

Maramor

First of all, depends on the way you selected the options.
As stated previously, if you selected windows authentication then "sa" is disabled. If you have mixed you still might have to enable the "sa" and "sa" can not be blank. There is no default password for "sa", if SQL express comes with a applications ask the applications support team.

You can put the SQL Server in single user mode and then any member of computer's local administrator can gain access to SQL server as sysadmin.

http://msdn.microsoft.com/en-us/library/dd207004.aspx

Try:
Go to SQL Server Properties/Security tab and change the mode to SQL Server authentication mode

Go to security/logins, open SA login properties

Uncheck "Enforce password policy" and "Enforce password expiration" check box there if you decide to use weak password

Assign password to SA user
If you get "Cannot set a credential for principal 'sa' . (Microsoft SQL Server, Error: 15535)" then "Map To Credential" check box on the General tab of the Login Properties - sa dialog box.

If “User is not associated with a trusted sql server connection"
In SQL Server Management Studio, Right-click the Server name, select Properties > Security
Under Server Authentication, select SQL Server and Windows Authentication Mode
The server must be stopped and re-started before this will take effect.
Make sure the sa (at status tab of sa properties) is enabled after restart the server.

-Matt Stone
DBA

alexsts

Matt,
as I stated before- any attempt to change anything in SQL property end up same way - user not authorize to perform this action.
I going to reinstall entire package one more time (already did this 3 times) to see if I missed anything where I can setup password for SA or any user at all for database.:mad:
And if it is not there I am going to report this as a bug to Microsoft on MSDN.:rolleyes:

svidgen

I'd be interested to know what particular package is giving you so much trouble.