Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
scubadog
Starting Member
1 Post |
 Posted - 2010-11-03 : 09:06:27
|
| I believe this to be a SQL permissions problem so I hope I'm in the correct forum with Administration. Our two SQL servers have been in the Corp domain (Windows 2003) for about 6 months to a year without any problem where as the SQL client computers is in a separate trusted domain called Company1 Windows 2003). We have been told that we have to decommission the Company1 domain by the end of the year and migrate everything into the Corp domain. The Corp enterprise admins are not using any kind of Migration tool they are having us to request for new user accounts and groups in the Corp domain. We have a gateway system that has two computers setup and configured the same called prod and dev. We have created the new corp domain accounts with the same name and password as they were in the comapany1 domain. We migrated the Dev server over into the corp domain about a week ago. We changed any services that were running with company1 domain account over to corp domain accounts. Every thing appeared to be running just fine.Then the application group had to run a process that moved a script from a testing DB over to a development DB. I'm being told that the service account that runs this application and has accounts in both the corp and company1 domains are the DB owner of the four DB's that the Dev gateway system uses. But it doesn't appear to have "write" access to tables in the DB. If the company1 owner is disabled then we have no access to the DB's even though we are one of the DB owner with the corp account.Do we have something messed up in the SQL security or is this a problem on the server caused by the domain migration. Does anyone have any clues that could help us fix this issue? |
|
|
|
|
|
Corp Domain Migration of SQL Clients