![Principal Principal](/uploads/1/2/5/4/125489891/634934137.jpg)
A special static ‘sa’ user is built into GP, and it cannot be deleted nor have its password changed from inside GP. The 'sa' user is the only GP user who can perform all GP maintenance and administrative tasks inside GP. as well as all maintenance and administrative tasks in SQL. Either create an AD user and use that as the owner of the database or create an SQL Server Login. 'sa' should not be used for situations like this. Viewing 4 posts - 1 through 4 (of 4 total).
In managment studio when I go to Security - Logins - and sa properties If I try to add user sa to my Db I get the following errors:If you are going to add a user called ‘sa’, that’s forbidden since it is a built-in account for SQLServer. Generally you can find the sa account in the logins tab of security node. And you may right click on the sa account, choose “Properties”, and then switch to the ‘Status’ tab, please make sure that you have enabled the login of that account.Thanks.Michael Jin.Microsoft Online Community SupportPlease remember to mark the replies as answers if they help and unmark them if they provide no help. Hi,Thank you, I realize now that changing the compatibility level has nothing to do with it.
![Cannot Cannot](/uploads/1/2/5/4/125489891/180995471.jpg)
It's a very strange issue, I am logging into management studio using the sa account. Login is enabled for the account when I go to that tab.Even though managment studio throws that exception, it doesn't appear to be effecting anything other than management studio functionality. The problem doesn't seem to manifest itself in any other place, we use the SA account frequently on our DEV machine with no problems. I think we're just going to chalk it up to a mystery unless it manifests itself as a problem.Thanks for your response.
Hello,We've been moving a couple of databases from an old 2000 server to a new VM with SQL Server 2008 Standard. In 2008 if I right click on the 'sa' user and go to properties and then on the left go to User Mapping, I can't put a check mark beside my database that I've restored and set it to dbowner. I get the error:Cannot use the special principal 'sa' (Microsoft SQL Server, Error: 15405)But yet in the old 2000 server you could set the database role of dbowner to our databases.Is this not possible in 2008 standard or is it just 'understood' that the dbowner is 'sa'?What we need is to be able to see that 'sa' is in the dbowner role with our database.Thank you,KB5.