Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
kwilliams
194 Posts |
Posted - 2003-03-18 : 11:51:26
|
| Ok, this isn't a complicated situation (I hope), but it will take a lot to express my problem. I'll give a simple version, and a detailed one:SIMPLE VERSION:I have Transactional Replication set up for 2 tables on 2 seperate servers...one internally and one for the external website. The replication was working fine for quite a while, but recently it just stopped working. To try to fix the problem, I completely deleted all subsriptions & publications, and recreated them. But this didn't work when I tested the replication.I asked my NA about it, because he had make a couple of changes to SQL Server, and he said he only did the following:1) He installed newer SQL connectivity drivers2) He installed the SQL 2000 management consoleWould either of these changes affect replication w/SQL Server 7? If so, what should I do? Please give me a step-by-step process, as I am somewhat of a newbie to SQL Server. Thanks for any help in advance.DETAILED VERSION:I really hope someone can help me out with this, because I am truly lost. I had replication set up for 4 publications: 3 Transactional & 1 Merge Publication. One day, they all stopped working. So I tried to fix one of them at a time, and set up Under Construction pages to allow me to do this. I completely deleted all subscriptions for this one Transactional Publication, and deleted the publication itself. I also deleted the database tables related to this publication on the front-end server. Once everything was deleted, I first exported the tabes related to this Transactional publication to the front-end database that I had deleted them from. Then I created a new publication with the exact same properties. Once the publication was created, I created a Push Subscription, and reinitialized it. I then made sure the Schedule was set to automatically update the front-end server's DB table when the back-end server's table was changed, and I had it running continuously. Finally, I made sure the user had permissions for these tables.To test this, I made a small text change to the back-end server's DB table's data. I then refreshed the front-end server's DB table to see if the change had been trasferred via replication, as it had done in the past. Unfortunately, it didn't. I tried this process several other times, but it's still not working.I asked my NA about it, because he had make a couple of changes to SQL Server, and he said he only did the following:1) He installed newer SQL connectivity drivers2) He installed the SQL 2000 management consoleWould either of these changes affect replication w/SQL Server 7? If so, what should I do? Please give me a step-by-step process, as I am somewhat of a newbie to SQL Server. Thanks for any help in advance.KWilliamskwilliams@douglas-county.com |
|
|
|
|
|
|
|