How to configure SQL Server 2005 to use a user different than "sa".
After upgrading to StarTeam 2008 (R2) from 2005 R2 or older, it is required to upgrade from SQL 2000 to SQL 2005. The security profile does not upgrade seamlessly and there is some manual work that must be done to get a non-sa user to work properly with StarTeam server.
Note: This article is not applicable to new configurations
created with Server 2008(R2) and SQL 2005.
This issue is caused by the changes made to the SQL Server security model. The backup from SQL 2000 that was imported into SQL 2005 does not properly setup the DB user for use with StarTeam. You will get errors adding views and stored procedures to the database (see There is already an object named "syn_ServerSettings" in the database. ).
To correct this:
Create a new database user in SQL Server under Security -> Logins. Do not create a new user under the starteam databases own Security section.
*** A new schema will map the user to "dbo", but SQL Server 2005 does not allow you to map a new user to "dbo". Its a limitation in SQL Server and at this time Borland Support does not have a recommendation on how to force the Default Schema to be DBO for a non-sa user.
If the issue persists, please contact Borland Support.
Author: Daniel Rice