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 |
|
dhw
Constraint Violating Yak Guru
332 Posts |
 Posted - 2003-04-13 : 12:26:09
|
| Hello...we have transactional replication already set up and working. Now...we added some new stored procs and made a couple of changes to existing stored procs. I see there are sp_repl* stored procs to add or drop columns in a table...but I don't see any replication sp's for altering/adding/dropping a stored procedure. If there aren't...how can we propagate changes to our clients database?thanks for any advice...dhw |
|
|
PiecesOfEight
Posting Yak Master
200 Posts |
Posted - 2003-04-14 : 21:33:57
|
| You cannot replicate incremental changes to procs using transactional replication. Your best bet is to put the procs into a separate snapshot publication that you synchronize at a reasonable interval: "reasonable" will depend on how frequently you make changes and how quickly those changes need to be propagated. You could set it to run nightly, and also synchronize on demand if you have changes that are more time sensitive. |
 |
|
|
dhw
Constraint Violating Yak Guru
332 Posts |
Posted - 2003-04-15 : 01:48:20
|
| Thanks for the information. I didn't realize that replication won't support changes to stored procs. Your suggestion sounds like a good solution. We won't be changing the stored procs all of the time...but every now and then it would be good to get the subscribers updated.thanks again. |
|
|
|
|
|
|
Replicating a new/changed Stored Proc