21 replies
by paultalb
I think service pack 2 takes care of some of the replication issues. Make sure you at least have SP1, we have been using SP2 without issue for a month.
Good Luck!
by mrushing
by msullivan
Your problem seems to be related to a specific table.
Here are a few suggestions.
Check permissions for the table in question. The distributor agent account must be able to access the table. As a general rule, use the same NT account for ALL SQL Server services on ALL computers.
Make sure you have enough room on the distributor to replicate the table. A large table being distributed by a resource challenged distributor will fail when it runs out of room.
Snapshots script thedatabase and BCP the data. Try scripting the table manually and see if the script works. If not, run DBCC as suggested earlier. If you cannot script the database out and then run the script on another box, snapshot replication will not work.
Hope this helps you.
Mike
by mrushing
by otura
Be sure to be using an account with administrative rights for the domain in which both servers reside. If you're using a local system account or an account without domain administrator rights you'll be having errors...
I hope this helps you...
by mrushing
by ike_sanabria
by mrushing
by kalufos
Check Your Tables Structure.
Are you replicating all the colums or part of the table?
We have a similar problem a few months ago and found that SQL 7 had a prblem when you replicate a numeric filed followed by a text field, This only happens whenyou are replicating a part of the table
by mrushing
by jbelina
BTW, if you don't get an answer that fixes your problem, you might want to check the SQL 7 discussion list at SWYNK.COM and the SQL Admin List at Sunbelt Software. You can find the links to both in a list of resources I've compiled for studying forthe MCSE and MCDBA...
Thanks,
Jeff
by mrushing
by sonnysan
by mrushing
by mrushing
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending