Good morning!
I am not a SQL person so this might be a bit of a silly question. Anyway,
here goes:
Is there a problem moving a SQL Server from DomainA to DomainB?
Here is the situation.
Client has one subnet (10.10.x.x) but two Domains (one WIN2000 AD and one
WINNT 4.0) reside in that one subnet. Not a problem. The WINNT 4.0 PDC is
also a SQL Server (running SQL 7.0 - but my question does not pertain to
this instance of SQL. I have included this information just in case it is
important to the question). However, there is a computer account that is a
member of this WINNT 4.0 domain that is running Windows 2000 Professional.
It is also running SQL Server 2000. We would like to remove that WIN2000
Pro system from the WINNT 4.0 domain and join it to the WIN2000 Domain.
Again, that part is easy. But, what happens to SQL (specifically the SQL
running on this computer) if I were to blindly do that. There is a lot of
critical data on that SQL2000 "server" that we can not afford to loose.
BTW - I inherited this environment so I do not know why things were done
this way. I *think* that it is an evolution thing that was simply
ignored/forgotten/not wanted.....that is, until now!
Thank you all!
--
Cary W. Shultz
Roanoke, VA 24012Set the SQL Server Service to NOT start on system startup.
Move the computer to the new domain.
Grant the new service account administrator rights on the server.
Use the services applet to change the login accounts for the MSSQLServer and
the SQLAgent services
start the sql server. Start the SQL Agent
If the SQL server accessed any network resources such as file shares, you
will need to replace the old service account with the new one.
Test and go.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Cary Shultz" <cwshultz@.mvps.org> wrote in message
news:eoeH4AL3GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Good morning!
> I am not a SQL person so this might be a bit of a silly question. Anyway,
> here goes:
> Is there a problem moving a SQL Server from DomainA to DomainB?
> Here is the situation.
> Client has one subnet (10.10.x.x) but two Domains (one WIN2000 AD and one
> WINNT 4.0) reside in that one subnet. Not a problem. The WINNT 4.0 PDC
> is also a SQL Server (running SQL 7.0 - but my question does not pertain
> to this instance of SQL. I have included this information just in case it
> is important to the question). However, there is a computer account that
> is a member of this WINNT 4.0 domain that is running Windows 2000
> Professional. It is also running SQL Server 2000. We would like to remove
> that WIN2000 Pro system from the WINNT 4.0 domain and join it to the
> WIN2000 Domain. Again, that part is easy. But, what happens to SQL
> (specifically the SQL running on this computer) if I were to blindly do
> that. There is a lot of critical data on that SQL2000 "server" that we
> can not afford to loose.
> BTW - I inherited this environment so I do not know why things were done
> this way. I *think* that it is an evolution thing that was simply
> ignored/forgotten/not wanted.....that is, until now!
> Thank you all!
> --
> Cary W. Shultz
> Roanoke, VA 24012
>|||Geoff,
Man, that sure sounds simple! I will do this. Thank you for the road map.
Thanks,
Cary
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%235olO1L3GHA.1288@.TK2MSFTNGP03.phx.gbl...
> Set the SQL Server Service to NOT start on system startup.
> Move the computer to the new domain.
> Grant the new service account administrator rights on the server.
> Use the services applet to change the login accounts for the MSSQLServer
> and the SQLAgent services
> start the sql server. Start the SQL Agent
> If the SQL server accessed any network resources such as file shares, you
> will need to replace the old service account with the new one.
> Test and go.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Cary Shultz" <cwshultz@.mvps.org> wrote in message
> news:eoeH4AL3GHA.1288@.TK2MSFTNGP03.phx.gbl...
>> Good morning!
>> I am not a SQL person so this might be a bit of a silly question.
>> Anyway, here goes:
>> Is there a problem moving a SQL Server from DomainA to DomainB?
>> Here is the situation.
>> Client has one subnet (10.10.x.x) but two Domains (one WIN2000 AD and one
>> WINNT 4.0) reside in that one subnet. Not a problem. The WINNT 4.0 PDC
>> is also a SQL Server (running SQL 7.0 - but my question does not pertain
>> to this instance of SQL. I have included this information just in case
>> it is important to the question). However, there is a computer account
>> that is a member of this WINNT 4.0 domain that is running Windows 2000
>> Professional. It is also running SQL Server 2000. We would like to
>> remove that WIN2000 Pro system from the WINNT 4.0 domain and join it to
>> the WIN2000 Domain. Again, that part is easy. But, what happens to SQL
>> (specifically the SQL running on this computer) if I were to blindly do
>> that. There is a lot of critical data on that SQL2000 "server" that we
>> can not afford to loose.
>> BTW - I inherited this environment so I do not know why things were done
>> this way. I *think* that it is an evolution thing that was simply
>> ignored/forgotten/not wanted.....that is, until now!
>> Thank you all!
>> --
>> Cary W. Shultz
>> Roanoke, VA 24012
>|||Hello - I have the same problem, but another question: What will happen with
the "Integrated Windows Accounts"?. I have some accounts, which are not
sql-accounts, but coming from the windows domain. The new domain will be a
small business server domain, which does not allow trusts.
Do I have to recreate all accounts within the new domain?
Thanks
Michael
"Cary Shultz" wrote:
> Geoff,
> Man, that sure sounds simple! I will do this. Thank you for the road map.
> Thanks,
> Cary
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%235olO1L3GHA.1288@.TK2MSFTNGP03.phx.gbl...
> > Set the SQL Server Service to NOT start on system startup.
> > Move the computer to the new domain.
> > Grant the new service account administrator rights on the server.
> > Use the services applet to change the login accounts for the MSSQLServer
> > and the SQLAgent services
> > start the sql server. Start the SQL Agent
> > If the SQL server accessed any network resources such as file shares, you
> > will need to replace the old service account with the new one.
> > Test and go.
> >
> > --
> > Geoff N. Hiten
> > Senior Database Administrator
> > Microsoft SQL Server MVP
> >
> >
> > "Cary Shultz" <cwshultz@.mvps.org> wrote in message
> > news:eoeH4AL3GHA.1288@.TK2MSFTNGP03.phx.gbl...
> >> Good morning!
> >>
> >> I am not a SQL person so this might be a bit of a silly question.
> >> Anyway, here goes:
> >>
> >> Is there a problem moving a SQL Server from DomainA to DomainB?
> >>
> >> Here is the situation.
> >>
> >> Client has one subnet (10.10.x.x) but two Domains (one WIN2000 AD and one
> >> WINNT 4.0) reside in that one subnet. Not a problem. The WINNT 4.0 PDC
> >> is also a SQL Server (running SQL 7.0 - but my question does not pertain
> >> to this instance of SQL. I have included this information just in case
> >> it is important to the question). However, there is a computer account
> >> that is a member of this WINNT 4.0 domain that is running Windows 2000
> >> Professional. It is also running SQL Server 2000. We would like to
> >> remove that WIN2000 Pro system from the WINNT 4.0 domain and join it to
> >> the WIN2000 Domain. Again, that part is easy. But, what happens to SQL
> >> (specifically the SQL running on this computer) if I were to blindly do
> >> that. There is a lot of critical data on that SQL2000 "server" that we
> >> can not afford to loose.
> >>
> >> BTW - I inherited this environment so I do not know why things were done
> >> this way. I *think* that it is an evolution thing that was simply
> >> ignored/forgotten/not wanted.....that is, until now!
> >>
> >> Thank you all!
> >>
> >> --
> >> Cary W. Shultz
> >> Roanoke, VA 24012
> >>
> >
> >
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment