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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-03-15 : 10:04:07
|
| Eric writes "I'm trying to use transactional replication to push data from our production server (SQL1) to our web server (SQL3) for lookups by going through a distribution server (SQL2). I have a publication on SQL1 and a pull subscription to SQL2. I then have a publication on SQL2 (basically the same publication that's on SQL1) and a push subscription to SQL3 (trying to offload the work to the distribution server). The publications on SQL1 and SQL2 both make use of the TRUNCATE table option for the snapshot initialization. When I set it up for the first time, everything runs fine. But if there's a problem between SQL1 and SQL2, I can't reinitialize the subscription because I get the error 'cannot truncate table Customer because it is being published for replication' Is there a way to get around this? Or is there a better replication model?Thanks for your help." |
|
|
Tom.ameye@ita.be
Starting Member
1 Post |
Posted - 2002-04-30 : 05:15:07
|
| Tese are tips for SQL 7.0 (I don't know if this is the same for 2000)You can not truncate a table when the is a replication on. But eavon is you delete the replication SQL Server does not always clean the replication on the subcriber. You can do this yourself.After you deleted the replication on the publication:Go on the subcriber. Open table sysObjects. If the field 'ReplInfo' is set to 128 for the table that was in the replication, The server did not clean correctly. You can change the value to '0'.Then you will be eable to change the table of truncate it. |
 |
|
|
|
|
|
Transactional Replication - Central Distributor