Click here to Skip to main content
15,867,141 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
We have an interesting situation in our company. We are boing taken over by two different companies starting on Tuesday. On Friday we made plans to make a copy of the virtual server that our sql server database is running on, so that one company could export the server onto there network. Of course the domain will change at the other company, but not till Monday and re-add them using the new domain. Put since the original database was created on another domain, will this cause issues with the developer having issues with adding himself or someone at the new company as the new administrator/sa? I will have to do the same thing on tue as the second company hired me to work for them, so I'm hoping we will not have an issue.
Any advice?
Thanks michael
Posted

1 solution

SA user is defined on the SQL Server instance and has nothing to do with individual databases.

Users are also defined on the SQL Server instance, but are used in a database.

So SA is available on all databases if "mixed mode authentication" is enabled.

The server/domain admin can always login and create/change users on a database, applications that depend on specific users may fail if those users are not defined on moved databases.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900