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 |
|
nr
SQLTeam MVY
12543 Posts |
 Posted - 2004-06-08 : 08:43:27
|
| I'm at a site where they have installed transactional replication.Unfortunately it's not very controlled.Someone has deleted a row from the subscriber database and hence replication stopped when the row was updated on the source.Now the subscriber is unsynced. Thay have replaced the row but can't get replication to start up again (don't care whathter the update is done because they are going to delete it from the source database).Any way of starting things going again without a snaphot?I seem to recall a discussion of a method which was meant to allow replication without a resync but didn't work.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-06-08 : 13:43:42
|
| I know some people here (mistakenly) use replication.The main problem is the publisher when the snapshot is taken.I've told them to make sure that they have backups of the subscriber more recent than the distributer purge so that they can restore without the snapshot but things aren't controlled enough here to rely on it.Surprise, surprise, we are going to remove access to the servers soon but it's nice not being considered an ogre for a few days.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-06-08 : 13:52:36
|
Why not just do the snapshot? Is there too much data and the snapshot takes quite a bit?And what do you mean by mistakenly use replication?  Do you not think that replication is a good solution for a reporting environment? I looked at Vyas' Replication FAQs, but I didn't see your question answered there. You might consider sending him an e-mail. I haven't seen him post at SQLTeam in a bit.Tara |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-06-08 : 13:57:51
|
| Is there too much data and the snapshot takes quite a bit?Yep - too much impact on the publisher.>> Do you not think that replication is a good solution Never seen a site where it's a good solution - but seen a lot where it's used.Actually it wouldn't be a bad idea here I think but shouldn't be used anywhere where databases aren't controlled - it's failing quite regularly due to these sorts of problems.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-06-08 : 17:46:08
|
| From VyasYou can simply skip that error and continue replication, by usingthe -SkipErrors parameter of the distribution agent. For more info on this,see 'distribution agent utility' in BOL.Regarding 'unsync', just unsubscribe, and resubscribe by specifyingsync_type = 'none', in the sp_addsubscription call. This can be done fromGUI also, by specifying "Subscriber already has schema and data" option.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
Replication resync