It could create some server overhead but I am not sure it will be critical although cleanup jobs must be set up. On the other hand I do prefer the...

If you are in 2005 DISABLE/ENABLE does that for you ... if what you are looking for is to drop/load/rebuild 😉

NICE catch!

sqlcmd can be your friend!

Verify that you have updated the stats on all your tables (preferably with FULLSCAN)

and you should also run DBCC UPDATEUSAGE on each DB.

By this time I think the PO is not longer with us (no pun intended)

Swirl80 (10/14/2008)

---

Thanks for that. Unfortunately i cannot afford any latency (well, as little as possible!) so sync with backup on the publication DB is not an option.

Since the replicated...

You are going to need a script but because you are in a "2005" forum and the suggested script above uses DMO I should warn you that you MUST...

That is basically the NOT FOR REPLICATION setting in the definition of the FKs. You will have to drop them and re-create them without the NFR part.

Now, make sure that...

You need to read a bit in BOL about Backing up replicated databases but in short all you need to do is to set the sync-with-backup option on the publication...

Here is a shot at it 🙂

declare @tbl TABLE ( person int, [Type] varchar(20), id int, [Start_Date] datetime, End_Date datetime)

insert into...

A little advice: Can you move the logic on the trigger into an sp or a multi-statement transaction handled by the client-side ?

I, Like others believe this should be better handled on the client-side but ...

for your benefit you can find here examples of both.

You maybe also running queries with "MAXDOP=1" and in that case you are out of luck ( unless you fix them )

Or create a format file to skip the column!