Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 234
  • Last Modified:

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?
0
Angela Pierce
Asked:
Angela Pierce
  • 2
  • 2
1 Solution
 
imitchieCommented:
uninstall reinstall. sql server is tied to full computer name, incl domain
0
 
Chris MangusDatabase AdministratorCommented:
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.
0
 
Angela PierceAuthor Commented:
So, where would I go to change this setting?
0
 
Chris MangusDatabase AdministratorCommented:
It's recommended to use Enterprise Manager / SQL Server Management Studio, but since you can't get SQL Server to start you have to change it through the Services applet in Control Panel.  On the Log On tab for the SQL Server service, change it to 'Local System Account'.
0
 
Angela PierceAuthor Commented:
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.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now