All,
I have the task of separating our AD into 2 domains due to selling one of
our companies off. Unfortunately, one of the SQL 2000 servers belongs to this
company and that needs to be moved to the new domain.
The machine in question is a windows 2003 server running SQL server 2000
sp3a. There are 3 databases on the machine, and there are domain accounts
that have permission to 2 of them.
The project will include creating the new domain and creating a trust
between them so that I can migrate user accounts with SID history, for
Exchange reasons.
How would I be able to move the server to the new domain? Do I just use the
Active Directory Migration Tool to move the server to the domain after the
user accounts have been moved, then assign the new domain user accounts to
the databases?
Any help would be appreciated
Thanks
Andoni
"Andoni" <Andoni@.discussions.microsoft.com> wrote in message
news:D3F1B0F8-53BA-43DB-8EB3-6A1E5C40AE33@.microsoft.com...
> How would I be able to move the server to the new domain? Do I just use
> the
> Active Directory Migration Tool to move the server to the domain after the
> user accounts have been moved, then assign the new domain user accounts to
> the databases?
After you migrate everything with ADMT, bounce the server into the new
domain, reset the service account and I do not believe you need to do
anything with login's based on domain accounts because they are sid based.
|||Hi Jason,
I have migrated the server, the user accounts were migrated beforehand. By
reset service account do you mean if SQL runs under a domain account? Also,
In the enterprise manager under security/logins, it's still showing domain
users in the old domain instead of the new one. will i need to create new
domain users?
thanks
A
"jason" wrote:
> "Andoni" <Andoni@.discussions.microsoft.com> wrote in message
> news:D3F1B0F8-53BA-43DB-8EB3-6A1E5C40AE33@.microsoft.com...
>
> After you migrate everything with ADMT, bounce the server into the new
> domain, reset the service account and I do not believe you need to do
> anything with login's based on domain accounts because they are sid based.
>
sql
Showing posts with label companies. Show all posts
Showing posts with label companies. Show all posts
Wednesday, March 21, 2012
Moving SQL Server to a new domain
All,
I have the task of separating our AD into 2 domains due to selling one of
our companies off. Unfortunately, one of the SQL 2000 servers belongs to this
company and that needs to be moved to the new domain.
The machine in question is a windows 2003 server running SQL server 2000
sp3a. There are 3 databases on the machine, and there are domain accounts
that have permission to 2 of them.
The project will include creating the new domain and creating a trust
between them so that I can migrate user accounts with SID history, for
Exchange reasons.
How would I be able to move the server to the new domain? Do I just use the
Active Directory Migration Tool to move the server to the domain after the
user accounts have been moved, then assign the new domain user accounts to
the databases?
Any help would be appreciated
Thanks
Andoni"Andoni" <Andoni@.discussions.microsoft.com> wrote in message
news:D3F1B0F8-53BA-43DB-8EB3-6A1E5C40AE33@.microsoft.com...
> How would I be able to move the server to the new domain? Do I just use
> the
> Active Directory Migration Tool to move the server to the domain after the
> user accounts have been moved, then assign the new domain user accounts to
> the databases?
After you migrate everything with ADMT, bounce the server into the new
domain, reset the service account and I do not believe you need to do
anything with login's based on domain accounts because they are sid based.|||Hi Jason,
I have migrated the server, the user accounts were migrated beforehand. By
reset service account do you mean if SQL runs under a domain account? Also,
In the enterprise manager under security/logins, it's still showing domain
users in the old domain instead of the new one. will i need to create new
domain users?
thanks
A
"jason" wrote:
> "Andoni" <Andoni@.discussions.microsoft.com> wrote in message
> news:D3F1B0F8-53BA-43DB-8EB3-6A1E5C40AE33@.microsoft.com...
> >
> > How would I be able to move the server to the new domain? Do I just use
> > the
> > Active Directory Migration Tool to move the server to the domain after the
> > user accounts have been moved, then assign the new domain user accounts to
> > the databases?
> After you migrate everything with ADMT, bounce the server into the new
> domain, reset the service account and I do not believe you need to do
> anything with login's based on domain accounts because they are sid based.
>
I have the task of separating our AD into 2 domains due to selling one of
our companies off. Unfortunately, one of the SQL 2000 servers belongs to this
company and that needs to be moved to the new domain.
The machine in question is a windows 2003 server running SQL server 2000
sp3a. There are 3 databases on the machine, and there are domain accounts
that have permission to 2 of them.
The project will include creating the new domain and creating a trust
between them so that I can migrate user accounts with SID history, for
Exchange reasons.
How would I be able to move the server to the new domain? Do I just use the
Active Directory Migration Tool to move the server to the domain after the
user accounts have been moved, then assign the new domain user accounts to
the databases?
Any help would be appreciated
Thanks
Andoni"Andoni" <Andoni@.discussions.microsoft.com> wrote in message
news:D3F1B0F8-53BA-43DB-8EB3-6A1E5C40AE33@.microsoft.com...
> How would I be able to move the server to the new domain? Do I just use
> the
> Active Directory Migration Tool to move the server to the domain after the
> user accounts have been moved, then assign the new domain user accounts to
> the databases?
After you migrate everything with ADMT, bounce the server into the new
domain, reset the service account and I do not believe you need to do
anything with login's based on domain accounts because they are sid based.|||Hi Jason,
I have migrated the server, the user accounts were migrated beforehand. By
reset service account do you mean if SQL runs under a domain account? Also,
In the enterprise manager under security/logins, it's still showing domain
users in the old domain instead of the new one. will i need to create new
domain users?
thanks
A
"jason" wrote:
> "Andoni" <Andoni@.discussions.microsoft.com> wrote in message
> news:D3F1B0F8-53BA-43DB-8EB3-6A1E5C40AE33@.microsoft.com...
> >
> > How would I be able to move the server to the new domain? Do I just use
> > the
> > Active Directory Migration Tool to move the server to the domain after the
> > user accounts have been moved, then assign the new domain user accounts to
> > the databases?
> After you migrate everything with ADMT, bounce the server into the new
> domain, reset the service account and I do not believe you need to do
> anything with login's based on domain accounts because they are sid based.
>
Wednesday, March 7, 2012
Moving Replication over to a new Server?
Hello.
We are currently replicating data over for
serveral companies on a win2k server with
sql2000. We just bought a new 2003 server
with sql2000. Being two different 0S's and
service packs and two different server
names. What is the best way to move
replication from the 2k server to the 2003
server with the least amount of disruption?.
We were thinking of doing this one company
at a time. However, a few of these
companies move across large amounts of
replicated data. Does any one have any
links on moving replication from a 2kserver
machine to a 2003 server machine? Or am I
just going to have to create new packages
for all of them and start from scratch.?
Our sql ninja is out on vacation, but the
current box is having hardware issues and we
cannot wait for him to get back in town to
do this move. Hince, i have been put in
charge to do this and am not the best with
tsql
Any help would be appreciated.
Thanks,
comb
Combfilter,
when you backup and restore databases to copy a database there is an option
to KEEP_REPLICATION. In my experience this won't work unless the servers
have identical names. Have a look at this article for more info:
http://msdn.microsoft.com/library/de...ckup_8enn.asp.
In your case your server have different names, different OSs and different
sps, so you are obliged to start from scratch. You can script out the
publications and subscribers before backing up and restoring. Editing the
scripts and changing servernames and logins can be done - it takes a bit of
work but it does ultimately ensure an identical setup . After that you'll
need to drop the original publications and initialize the new ones.
HTH,
Paul Ibison
|||In article <uIaX1YXVEHA.2716
@.tk2msftngp13.phx.gbl>,
Paul.Ibison@.Pygmalion.Com says...
> Combfilter,
> when you backup and restore databases to copy a database there is an option
> to KEEP_REPLICATION. In my experience this won't work unless the servers
> have identical names. Have a look at this article for more info:
> http://msdn.microsoft.com/library/de...ckup_8enn.asp.
> In your case your server have different names, different OSs and different
> sps, so you are obliged to start from scratc You can script out the
> publications and subscribers before backing up and restoring. Editing the
> scripts and changing servernames and logins can be done - it takes a bit of
> work but it does ultimately ensure an identical setup . After that you'll
> need to drop the original publications and initialize the new ones.
> HTH,
> Paul Ibison
>
>
Thanks for the info paul. I started
completly from scratch on the smaller
companies.. I think I am going to try your
method (scripting out and changing server
names)for the bigger ones.
-comb
We are currently replicating data over for
serveral companies on a win2k server with
sql2000. We just bought a new 2003 server
with sql2000. Being two different 0S's and
service packs and two different server
names. What is the best way to move
replication from the 2k server to the 2003
server with the least amount of disruption?.
We were thinking of doing this one company
at a time. However, a few of these
companies move across large amounts of
replicated data. Does any one have any
links on moving replication from a 2kserver
machine to a 2003 server machine? Or am I
just going to have to create new packages
for all of them and start from scratch.?
Our sql ninja is out on vacation, but the
current box is having hardware issues and we
cannot wait for him to get back in town to
do this move. Hince, i have been put in
charge to do this and am not the best with
tsql
Any help would be appreciated.
Thanks,
comb
Combfilter,
when you backup and restore databases to copy a database there is an option
to KEEP_REPLICATION. In my experience this won't work unless the servers
have identical names. Have a look at this article for more info:
http://msdn.microsoft.com/library/de...ckup_8enn.asp.
In your case your server have different names, different OSs and different
sps, so you are obliged to start from scratch. You can script out the
publications and subscribers before backing up and restoring. Editing the
scripts and changing servernames and logins can be done - it takes a bit of
work but it does ultimately ensure an identical setup . After that you'll
need to drop the original publications and initialize the new ones.
HTH,
Paul Ibison
|||In article <uIaX1YXVEHA.2716
@.tk2msftngp13.phx.gbl>,
Paul.Ibison@.Pygmalion.Com says...
> Combfilter,
> when you backup and restore databases to copy a database there is an option
> to KEEP_REPLICATION. In my experience this won't work unless the servers
> have identical names. Have a look at this article for more info:
> http://msdn.microsoft.com/library/de...ckup_8enn.asp.
> In your case your server have different names, different OSs and different
> sps, so you are obliged to start from scratc You can script out the
> publications and subscribers before backing up and restoring. Editing the
> scripts and changing servernames and logins can be done - it takes a bit of
> work but it does ultimately ensure an identical setup . After that you'll
> need to drop the original publications and initialize the new ones.
> HTH,
> Paul Ibison
>
>
Thanks for the info paul. I started
completly from scratch on the smaller
companies.. I think I am going to try your
method (scripting out and changing server
names)for the bigger ones.
-comb
Subscribe to:
Posts (Atom)