SQL uses Windows Auth only causing login to fail for 'phoenixUser'


roger commented on January 5, 2008 1:49 AM
How to determine if a password is strong: http://technet.microsoft.com/en-us/library/ms161962.aspx
roger commented on January 5, 2008 1:46 AM
Before creating the database we could run this command to see if Mixed mode is enabled. SELECT SERVERPROPERTY('IsIntegratedSecurityOnly') If 1 then enable the sa account like this: ALTER LOGIN sa ENABLE ; GO ALTER LOGIN sa WITH PASSWORD = '<password>' ; GO
roger commented on November 10, 2007 1:31 PM
Not sure how to remedy this.... we could enforce that users must choose Mixed mode when installing SQL Express (or have them change it manually vis EM or MS). Ditch the phoenixUser altogether (why are we using it again)


SQueek wrote Mar 22, 2010 at 3:36 PM

I have mixed mode enabled. But don't use the sa account for my webapps. Do I have the possibility to use another user for SQL access instead of the sa account?

rhelliwell wrote Mar 23, 2010 at 4:35 AM

The sa account is only used by the installer to create the database, tables and a 'phoenixUser' account. The webapp runs under the phoenixUser account. However, I think the sa account is hardcoded in the installer (you enter the password). I could be wrong there -- it's been a while.

wrote Feb 13, 2013 at 11:33 PM