SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Multiple DB's to central location


Multiple DB's to central location

Author
Message
DHeath
DHeath
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3942 Visits: 779
If i have lets say 5 databases all around 2-5 GB and 30 tables on 5 different servers (SQL 2012 to 2017 and 2 Oracle tables) these all are to be moved to a central location on 1 server with SQL Server 2017. I also want to update certain tables but not all tables to keep the central location as current as possible with no more than a 30 minute delay between the different sources and central location. Initially i can take full backups of all 5 and restore to central location and from that point i am trying to figure out what is my best option for longevity after the initial build to keep central location current as possible. Just a note... when all said and done these will grow for approximately 3-5 years and most likely in that time the 100GB allotted to the drive will not be maxed out(but can grow it if the need be).

Options:
1. Transaction Replication on the particular tables to push to the central location when it takes place so that the update is almost immediately?
2. Use of triggers upon inserts or deletes
3. Always On..Could be used but i also know this is NOT the intended use for this feature but is also extremely easy to set up

Just looking for some ideas as to what might be my best bet to set this up and have it run with little to no intervention once setup properly.

All reply's and comments are welcome and appreciated. Thank you
Subramaniam Chandrasekar
Subramaniam Chandrasekar
Hall of Fame
Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)

Group: General Forum Members
Points: 3358 Visits: 531
DHeath - Wednesday, February 7, 2018 12:58 PM
If i have lets say 5 databases all around 2-5 GB and 30 tables on 5 different servers (SQL 2012 to 2017 and 2 Oracle tables) these all are to be moved to a central location on 1 server with SQL Server 2017. I also want to update certain tables but not all tables to keep the central location as current as possible with no more than a 30 minute delay between the different sources and central location. Initially i can take full backups of all 5 and restore to central location and from that point i am trying to figure out what is my best option for longevity after the initial build to keep central location current as possible. Just a note... when all said and done these will grow for approximately 3-5 years and most likely in that time the 100GB allotted to the drive will not be maxed out(but can grow it if the need be).

Options:
1. Transaction Replication on the particular tables to push to the central location when it takes place so that the update is almost immediately?
2. Use of triggers upon inserts or deletes
3. Always On..Could be used but i also know this is NOT the intended use for this feature but is also extremely easy to set up

Just looking for some ideas as to what might be my best bet to set this up and have it run with little to no intervention once setup properly.

All reply's and comments are welcome and appreciated. Thank you

Will third party tools be allowed ? WinkSmile

DHeath
DHeath
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3942 Visits: 779
No third party tools are to be used in this solution. Jut trying to make it happen with the capabilities of SQL Server.

Thanks for the comment
Alexander Zhang
Alexander Zhang
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1077 Visits: 264
I think you can consider Replication/CDC/CT. BTW, if SQL 2012 is not enterprise edition, forget about CDC.

GASQL.com - Focus on Database and Cloud
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search