November 20, 2009 at 3:55 pm
[font="Tahoma"]
Hi All,
While I find no specific link or documentation that specifically debars anyone from implementing replication between two databases in the same instance, I have been getting recurrent errors in this experiment.
Currently we have a need to replicate a single publication from a publishing (source) database to 2 or more subscribing databases in the same instance. While there certainly are other methods to use to achieve the purpose, my client is averse to using triggers for such a need. Besides, if replication is successful (transactional and (luckily) unidirectional), the SQL Server would take care of the process without any extra effort.
Am I missing anything? Does any other kind of information provided be helpful? The error code displayed is the general 15517! (relating mostly to permissions and the like, but I am sure that there are no problems on this end with that...
Any help or pointers to look for/research would be greatly appreciated.
Thanks in advance,
Venky
[/font]
November 25, 2009 at 7:39 am
Setting up transactional replication is quite easy in SQL 2008. Couple of things to keep in mind is that the Service and agents should run under a domain account and the snapshot folder permission is set up correctly. It is usually the snapshot folder that throws the permission errors.
-Roy
November 29, 2009 at 12:44 pm
Hi Roy,
Thanks for your reply. However, after some research and assiduous poring over MSDN-bestowed articles, I found that the culprit was the restored database! I had restored one of the databases from our client's backup file and the database context therefore was awry (the 'credentials' were pointing to the account on the client's server). Once I changed the database ownership to one on my local machine, the replication seemed to pick up the thread 🙂
Thanks again for your response.
Regards,
Venky
November 29, 2009 at 1:16 pm
Hi
Please review this article.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply