how to enable replication from 2000 to 2005

Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.server:423927
I have never done replication before, so treat me like a novice, even though
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?
1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>

how to enable replication from 2000 to 2005

Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.server:423927
I have never done replication before, so treat me like a novice, even though
I'm otherwise familiar with SQL Server.
I have a database on a SQL 2000 machine. Soon, I want to port the database
to SQL 2005, but in the meantime, I want to do some testing against our new
2005 box. I thought I should enable replication from the 2000 box to the
2005 box. This will allow us to do queries on each, test the data and
security settings are the same, and then *instantly* transfer the
application to pull from the 2005 box when testing is complete.
1) If the 2005's database starts as blank, will it copy over all existing
data, or just the data for new inserts/updates/deletes?
2) How do I enable replication, and of what type, on each box? I have a
book on the 2005 beta, which helps a little bit, but I'm still pretty lost
on what to set up on both boxes.
3) Will I have to reboot the 2000 box anytime in this process? I can't do
that. It's live 24/7.
4) What happens if the receiving box, the 2005 one, is rebooted? Will it
catch up with that couple minutes of lost data when it is back online?1. The replication engine will generate a snapshot of the 2000 machine, data
and structure, and apply it to the 2005 machine. Changes will then be sent
from publisher to subscriber. You may need to manually transfer other
objects such as procedures, views, triggers, etc. You will have to transfer
logins and users yourself.
2. There is a replication wizard which can take you through the process.
You should be able to use transactional replication. You'll want to
configure the distributor on the 2005 machine.
3. No, it does not require a reboot.
4. If either the publisher or subscriber goes down, replication will pick up
where it left off. The amount of time to catch up is dependent upon the
volume of data needing to be sent and the bandwidth available to send it.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"HK" <replywithingroup@.notreal.com> wrote in message
news:vMOIf.8366$Jg.7375@.tornado.socal.rr.com...
>I have never done replication before, so treat me like a novice, even
>though
> I'm otherwise familiar with SQL Server.
> I have a database on a SQL 2000 machine. Soon, I want to port the
> database
> to SQL 2005, but in the meantime, I want to do some testing against our
> new
> 2005 box. I thought I should enable replication from the 2000 box to the
> 2005 box. This will allow us to do queries on each, test the data and
> security settings are the same, and then *instantly* transfer the
> application to pull from the 2005 box when testing is complete.
> 1) If the 2005's database starts as blank, will it copy over all existing
> data, or just the data for new inserts/updates/deletes?
> 2) How do I enable replication, and of what type, on each box? I have a
> book on the 2005 beta, which helps a little bit, but I'm still pretty lost
> on what to set up on both boxes.
> 3) Will I have to reboot the 2000 box anytime in this process? I can't
> do
> that. It's live 24/7.
> 4) What happens if the receiving box, the 2005 one, is rebooted? Will it
> catch up with that couple minutes of lost data when it is back online?
>