June 11, 2009 at 2:30 pm
Good afternoon, I have a SQL server setup as a distributor, with a merge publication setup to replicate to 4 subscribers up and running.
What i need now is to setup a uni directional replication to a test database for testing so that the main database does not have data changed from testing.
i know transcational replication is only one way, can i have an additional publication on the distributor for transational replication?
(so having two publications)
or
can i setup another distributor/publication off one of the replicated databases for a transactional replication?
(replicating of a replicated database)
Thanks
June 11, 2009 at 9:15 pm
Hello,
It is possible to have multiple Publications from the same database.
How up-to-date does the data on the test DB need to be? I am just wondering if Snapshot replication might be enough? (Or even an old fashioned restore of your live DB).
Regards,
John Marsh
www.sql.lu
SQL Server Luxembourg User Group
June 12, 2009 at 9:03 am
I have a restored database already setup, the problem is that the person needs live data to test with.
When i setup a new publication i get an error and its says
Creating Publication Test server Success
Adding article 154 of 154 error (sql error 21231)
Starting the sbanshot agent stopped
What i am thinking is to setup another distributor/Publisher on one of the replicated databases and then push to the newe subscriber, is that possible?
June 12, 2009 at 9:25 am
mfullbrook (6/11/2009)
i know transcational replication is only one way, can i have an additional publication on the distributor for transational replication?Thanks
Even though it might not be of use in your scenario, just wanted to mention that you can setup peer to peer replication wherein it acts like a 'two-way' replication.
Also, it's very much possible to setup multiple publications on the same database, as metioned in the previous post.
June 12, 2009 at 9:28 am
mfullbrook (6/12/2009)
What i am thinking is to setup another distributor/Publisher on one of the replicated databases and then push to the newe subscriber, is that possible?
A subscriber can act as a publisher, like the below mentioned scenario -
server1 - original db(db1)
server2(db2) - subscriber for server1(db1). can be setup as publisher of the same db(db2)
server3(db3) - subsriber for server2(db2).
June 12, 2009 at 10:38 am
Thank you all for the help.
Martin
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply