October 8, 2011 at 4:24 am
Hi
I am going to describe my requirement first:
I have a central SQL server which must be synched to other SQL clients. I need a mechanism to synchronize every database with the corresponding SQL database in the central server. Lets name the servers and describe the requirement with an example: Lets call the central server as "C" and 4 remote and geographically scattered SQL servers called "A,B,D,E" . At the beginning I need to create 4 databases in C and only one of them will be automatically created in the others (they are all the same but every database for every remote site). Afterwards, when any changes happens to those databases it will be synched to the corresponding database as well.That means if we call them C.db1, C.db2, C.db3 and C.db4 the synchronization required would be C.db1 with A, C.db2 with B, C.db3 with D, and C.db4 with E.
It will be very efficient if I can configure the central server to be synched in specified period of times but if the synchronization must be live (and not say every 10 minutes) that's OK.
So considering above scenario in the mind, should I go for Log Shipping solution or I require other means as well.
Thanks for your time and effort.
October 8, 2011 at 5:54 am
That sounds like a classic candidate for replication. Transactional if one way, perhaps merge if the central needs to be updated from the secondaries as well
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 8, 2011 at 7:09 am
yassermat (10/8/2011)
HiI am going to describe my requirement first:
I have a central SQL server which must be synched to other SQL clients. I need a mechanism to synchronize every database with the corresponding SQL database in the central server. Lets name the servers and describe the requirement with an example: Lets call the central server as "C" and 4 remote and geographically scattered SQL servers called "A,B,D,E" . At the beginning I need to create 4 databases in C and only one of them will be automatically created in the others (they are all the same but every database for every remote site). Afterwards, when any changes happens to those databases it will be synched to the corresponding database as well.That means if we call them C.db1, C.db2, C.db3 and C.db4 the synchronization required would be C.db1 with A, C.db2 with B, C.db3 with D, and C.db4 with E.
It will be very efficient if I can configure the central server to be synched in specified period of times but if the synchronization must be live (and not say every 10 minutes) that's OK.
So considering above scenario in the mind, should I go for Log Shipping solution or I require other means as well.
Thanks for your time and effort.
so, am i correct in saying
server C database 1 would replicate to server A
server C database 2 would replicate to server B
server C database 3 would replicate to server D
server C database 4 would replicate to server E
If this is correct I would implement separate log ship plans for these databases. You could use replication if your database schema supports this.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 8, 2011 at 10:55 pm
Thanks. Now I can step forward for sure.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply