Angela Pierce
asked on
Why is it that when the Domain is changed, SQL server won't start?
I have a test server with SQL 2005 loaded on it and 2 applications that utilize the SQL server. I need to change the domain to a test domain to keep the machine off the main network. When I change the domain, though, the SQL server refuses to start, and therefore renders the Symantec inoperable. How can I adjust it so that the SQL server either is domain independent or at least recognizes the new domain instead?
uninstall reinstall. sql server is tied to full computer name, incl domain
I've never heard that SQL Server is "tied" to a domain.
It's likely that your SQL Server service is set to start with a domain account vs. a local system account. It can't see the old domain so it can't start.
Change the service account to a local system account.
It's likely that your SQL Server service is set to start with a domain account vs. a local system account. It can't see the old domain so it can't start.
Change the service account to a local system account.
ASKER
So, where would I go to change this setting?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I had to change all of the SQL services to local logon but it worked; I can now get into my Symantec and ATTACC installations. Thank you.