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 |
|
colin.graham@stylo.co.uk
Starting Member
8 Posts |
 Posted - 2008-07-30 : 03:27:03
|
| Good Morning,I have a potential situation with a replicated database and am looking for some advice.I have a Table on the Publisher that will, occasionally, require to re-built completely using a bulk load. The current method is to DROP and Re-CREATE the table, but I think that this will crate problems.Would TRUNCATE or DELETE all rows be a possible solution; or is there any other technique commonly used for this situation. It seems to me that this is not an usual situation, so I was wondering how other people normally handle this.RegardsColin |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-30 : 17:08:51
|
| Truncate table command will not replicate to subscriber. What about exporting fresh copy of that table to subscriber everyday? |
 |
|
|
colin.graham@stylo.co.uk
Starting Member
8 Posts |
Posted - 2008-07-31 : 05:01:35
|
| Thanks very much for the suggestion to Export this file rather than include it in replication. I will try this.ColinColin |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-31 : 21:07:20
|
quote:
Originally posted by colin.graham@stylo.co.uk
Thanks very much for the suggestion to Export this file rather than include it in replication. I will try this.ColinColin
I am saying Exporting table |
|
|
|
|
|
|
Replication with DROP and/or TRUNCATE table