Showing posts with label workingok. Show all posts
Showing posts with label workingok. Show all posts

Sunday, March 11, 2012

can sqlsvr2005 replicate tables to sqlsvr2000?

Hello,
I have replication in place between 2 sqlsvr2000 DBs. Everything is working
OK. I am looking to upgrade the publishing sqlsvr from sqlsvr2000 to
sqlsvr2005. The subscription sever will remain as a sqlsvr2000 server
because I don't own that one. If I were to go ahead an perform the upgrade
on my end, will I still be able to replicate my table to the sqlsvr2000
subscriber?
Thanks,
Rich
Absolutely. The only caveat is that if you are using merge replication the
snapshot will have to be sent again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:DEE16A4E-CCF9-4D6A-9A4C-4F4A69FDBD24@.microsoft.com...
> Hello,
> I have replication in place between 2 sqlsvr2000 DBs. Everything is
> working
> OK. I am looking to upgrade the publishing sqlsvr from sqlsvr2000 to
> sqlsvr2005. The subscription sever will remain as a sqlsvr2000 server
> because I don't own that one. If I were to go ahead an perform the
> upgrade
> on my end, will I still be able to replicate my table to the sqlsvr2000
> subscriber?
> Thanks,
> Rich
|||Thanks. The folks over my way are a little reluctant to move forward with
the upgrade - but hey! We have an MSDN subscription and I already downloaded
all of sqlsrv2005 enterprise. They were trying to use the Replication angle.
Glad that won't be an issue.
Rich
"Hilary Cotter" wrote:

> Absolutely. The only caveat is that if you are using merge replication the
> snapshot will have to be sent again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:DEE16A4E-CCF9-4D6A-9A4C-4F4A69FDBD24@.microsoft.com...
>
>