Thank you so much, Aravin. You have just saved me from hours of pulling my hair out! I did exactly what you did and was able to replicate between my 2000 and 2008 servers.
Post by Query BuilderI have 2 instance of SQL Servers.
Instance A : SQL Server 2000 Enterprise Edition running on Windows
2003 (32 Bit).
Instance B : SQL Server 2008 Enterprise Edition running on Windows
2008 (64 Bit Cluster).
These servers both reside on different domains but have connectivity
between them using SQL Authentication.
I need to setup Transactional Replication from Server A to Server B.
I have reviewed the following MS KB: http://msdn.microsoft.com/en-us/library/ms143241.aspx
It States : "Using a SQL Server 2005 or SQL Server 2008 Distributor
with a Publisher Running SQL Server 2000
SQL Server 2005 and SQL Server 2008 can be used as a remote
Distributor for Publishers that are running SQL Server 2000. To change
agent properties in this scenario, execute the following stored
procedures at the Distributor. These procedures let you change
properties that were introduced in SQL Server 2005:"
I have tried executing the procedures but still am not able to make a
connection to the Publisher from The Subscriber.
Has anyone successfully implemented a SQL 2000 to SQL 2008
Transactional Replication? If so, can you please advise the steps you
had performed in order to set it up?
Thanks In advance..
Aravin Rajendra.
Post by Jay KonigsbergI did a little digging for you and found a relevent page.
Using Multiple Versions of SQL Server in a Replication Topology
http://msdn.microsoft.com/en-us/library/ms143241.aspx
"SQL Server 2000 and SQL Server 2005 can both participate in replication
topologies with SQL Server 2008. For SQL Server 2000 the minimum version is
Service Pack 3 (SP3). For SQL Server 2005 the minimum version is Service
Pack 2 (SP2)."
also
"For all types of replication, the Distributor version must be no earlier
than the Publisher version. (Frequently, the Distributor is the same
instance as the Publisher.)"
Which means that you cannot use a 2008 instance as a distributor for your
2000 publisher, it must be 2000.
Good luck.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by Jay KonigsbergI did a little digging for you and found a relevant page.
Using Multiple Versions of SQL Server in a Replication Topology
http://msdn.microsoft.com/en-us/library/ms143241.aspx
"SQL Server 2000 and SQL Server 2005 can both participate in replication
topologies with SQL Server 2008. For SQL Server 2000 the minimum version is
Service Pack 3 (SP3). For SQL Server 2005 the minimum version is Service
Pack 2 (SP2)."
also
"For all types of replication, the Distributor version must be no earlier
than the Publisher version. (Frequently, the Distributor is the same
instance as the Publisher.)"
Which means that you cannot use a 2008 instance as a distributor for your
2000 publisher, it must be 2000.
Good luck.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by Jay KonigsbergHere is the relevant man page.
Using Multiple Versions of SQL Server in a Replication Topology
http://msdn.microsoft.com/en-us/library/ms143241.aspx
"SQL Server 2000 and SQL Server 2005 can both participate in replication
topologies with SQL Server 2008. For SQL Server 2000 the minimum version is
Service Pack 3 (SP3). For SQL Server 2005 the minimum version is Service
Pack 2 (SP2)."
also
"For all types of replication, the Distributor version must be no earlier
than the Publisher version. (Frequently, the Distributor is the same
instance as the Publisher.)"
Which means that you cannot use a 2008 instance as a distributor for your
2000 publisher, it must be 2000.
Good luck.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by Jay KonigsbergHere is the relevant man page.
Using Multiple Versions of SQL Server in a Replication Topology
http://msdn.microsoft.com/en-us/library/ms143241.aspx
"SQL Server 2000 and SQL Server 2005 can both participate in replication
topologies with SQL Server 2008. For SQL Server 2000 the minimum version is
Service Pack 3 (SP3). For SQL Server 2005 the minimum version is Service
Pack 2 (SP2)."
also
"For all types of replication, the Distributor version must be no earlier
than the Publisher version. (Frequently, the Distributor is the same
instance as the Publisher.)"
Which means that you cannot use a 2008 instance as a distributor for your
2000 publisher, it must be 2000.
Good luck.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by Jay KonigsbergTwo things.
1) Make sure your 2000 instance is SP3.
2) The distributor cannot be a higher version than the publisher, in this
case 2000 SP3.
Using Multiple Versions of SQL Server in a Replication Topology
http://msdn.microsoft.com/en-us/library/ms143241.aspx
Good luck.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by Jay KonigsbergTwo things.
1) Make sure your 2000 instance is SP3.
2) The distributor cannot be a higher version than the publisher, in this
case 2000 SP3.
Using Multiple Versions of SQL Server in a Replication Topology
http://msdn.microsoft.com/en-us/library/ms143241.aspx
Good luck.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by Jay KonigsbergTwo things.
1) Make sure your 2000 instance is SP3.
2) The distributor cannot be a higher version than the publisher, in this
case 2000 SP3.
Search BOL for: "Using Multiple Versions of SQL Server in a Replication
Topology"
Good luck.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
.
Post by Jay KonigsbergTwo things.
1) Make sure your 2000 instance is SP3.
2) The distributor cannot be a higher version than the publisher, in this
case 2000 SP3.
Post by Jay KonigsbergOK Sorry guys, I was replying from the SQL Server group and none of the
replies were showing up. It was driving me nuts and I was determined to
figure it out.
Somehow, the server was not dealing with the multiple groups correctly and
showing the replies in all the groups (specifically
microsoft.public.sqlserver.sqlserver).
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by Jay KonigsbergThe OP specified "microsoft.public.sqlserver.replication" in the "Follow-Up"
field. I had forgotten that friggin field was even there.
--
Jay Konigsberg
SQL Server DBA in Sacramento, CA
http://www.linkedin.com/in/jaykonigsberg
Live in Sacramento, CA?
Join the Sacramento SQL Server User Group on LinkedIn
http://www.linkedin.com/groups?home=&gid=2825448&trk=anet_ug_hm&goback=%2Emyg
Post by AravinThanks..
So, I did a test from a SQL 2000 to SQL 2008 and I am able to
replicate. I guess my issue is that they both reside in 2 separate
Domains (which should not be a problem as I can clearly ping the SQL
IP) but to make it worse, the 2008 is a named instance. !!
So, the only way for me to get thru to the SQL Instance is via IP and
when I go to configure the replication subscriber, I have no way to
specify the Server instance.
In Case anyone is going thru what I went thru, This is how I managed
I tried to create a connection to the SQL 2008 Instance from the SQL
2000 EM. I went and gave the SQL Name, Userid, PWD on the connection
manager and it will try to connect and fail saying the SQL server does
not exists or access denied. Just simply say accept the connection
strings. It will appear on your EM but will say Disconnected. (The key
is to make sure you can ping the server and the UserID/PWD should be
correct).
Then on your publisher, add a push subscriber and pick this as your
subscriber. Simply add a push subscriber and re-int... It works...
Thanks again
Aravin Rajendra.
Up"
com/groups?home=3D&gid=3D2825448&trk=3Danet_ug_hm&gobac...
nd
bac...
.
Submitted via EggHeadCafe - Software Developer Portal of Choice
Using the ASP.NET CustomValidator Control
http://www.eggheadcafe.com/tutorials/aspnet/e622d48f-2787-4906-b97f-1ef8037a688f/using-the-aspnet-customvalidator-control.aspx