July 1, 2003 at 3:19 pm
Hi to all:
I was planning to implement replicating the execution of the stored procedures in my schema, so I starting practicing a bit with this
because I have never use it. I use transactional replication.
So what I did was this. Create a publication and add a sp to replicate the execution of it. up to here it worked fine and the execution replicated with no problem
to all my subscribers. Then I modified
the sp, and notice that this din't reinitialize my publication, and even if I re execute the sp again, in my subscribers, it would execute the
old sp.
Then I run sp_addscriptexec to change the sp at the subscribers, with the correct .sql script.
When I run the distributor, it worked fine with sps sincronized.
After that I ran again the sp_addscriptexec, but before syncronizing, I manually delete the script to be applied.
And every time I run the distributor, it fails because it can find the script to apply it at my subscribers with osql.
And also, it doesn't return any error number that I can use to skip.
So far, the only way I find to continue, it to drop and recreate my publication.
This is a test environment, so there is no problem. But anyone know if this type of error can be skipped?
thanks in advanced.
July 1, 2003 at 3:32 pm
If you change the stored proc, u have to regen the snapshot. Otherwise the subscriber will not have the same proc
July 1, 2003 at 3:44 pm
I know that is why I used sp_addscriptexec. This is almost the same as re applying the snapshot, but much easier. I just add the new version of the sp, and it applies to all the subscribers.
I also realized, that I can skip the error, re creating the directory and the fyle name. But can be another way?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy