Thursday, March 29, 2012
DATABASE MOVE
This is my situation
We got a Transactional Replication set up between Server A and Server B.
Server A is the Distributor and B the Subscriber.
Recently we moved the database in Server A to another server , say Server C
and linked the Replication back to Server B
Before the move, one of my replicated table, say myTable got 2 records .
Now when I delete this 2 records , this deletion is not getting replicated
back to server B. All new changes (including INSERT/DELETE/UPDATE)
are getting replicated correctly..
Any thoughts/suggestions
ShamimTurn on logging of the Distribution agent and run profiler on both the
Publisher/Distributor and Subscriber.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Thursday, March 22, 2012
Database Mirroring & Replication Considerations
Hi all,
Can a publisher be mirrored? What are the implications, issues, gotchas? Transactional, Merge or Transactional w/ Updating Subscribers is what I'm considering.
Bottom line is I would like to use mirroring, but only one mirror will not suffice.
Thank you in advance.
Ray Nichols
I am using this configurationServer 1 - data 1 - DR (Mirroring)
Server 1 - Data 1 - Publisher (Replication - Transactional)
also you could refer http://msdn2.microsoft.com/en-us/library/ms151799.aspxsql
Wednesday, March 21, 2012
Database Mirror + Snapshot + Replication Questions
All,
We have SQL 2005 db mirror configured with a witness server for high availability. Node 1 is the principal and Node 2 is the mirror. A nightly job creates a snapshot on Node 2. The snapshot is used for previous day reporting queries. We have now been asked to present another copy of the database for near-time reporting. I thought about possibly adding a peer-to-peer replication as part of my environment but was hoping to see what everyone else out there is doing.
Regards,
Ian
I tend to use transactional replication with a pollinginterval of 1 and replicate the execution of stored procedures as much as possible.Wednesday, March 7, 2012
Database maintenance on replicated database
Hi,
I have transactional replication set up on a DB and run database maintenance scripts (index defrag, update stats, etc) on this DB daily.
Will the maintenance job/scripts also be propagated to the replica (subscriber) causing these maintenance operations to be performed on the replica OR do I need to create separate jobs on the replica DB (subscriber) also? I'm guessing the latter but wanted to verify to make sure I wasn't missing something. Thanks!
You need to run separate job on the replica DB. The only operations that are replicated are: DML (insert/update/delete) and certain DDL (ALTER table/proc/function).
Peng
|||Thanks Peng.Database maintenance (SQL Server 2000)
Could someone here clarify the difference between replication and mirroring?
What I want to do is to be able to make a back-up of my database to a different computer, what are the things I need to do? Is it replication or mirroring?
TIA
Are do you looking to develop a high availability solution for your database from a primary server to secondary server.1. Database Mirroring (SQL 2005 SP1 only) allows real-time synchronous mirroring of the data.
2. Log Shipping allows mirroring of the log to a secondary machine
3. Replication (Merge & Transactional) allow alot more flexibility then the first two. They have a notion of a publisher and potentially many subscribers.
It is best to ask in the other (Mirroring or Replication) forums if you have more questions.