Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Replicating/Update Remote Server Expand / Collapse
Author
Message
Posted Wednesday, September 19, 2012 7:10 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 11:23 PM
Points: 114, Visits: 186
Hi everyone

I was wondering what the best solution/practice would be for the following scenario:

We have a complex data structure with many tables creating one product, there are +- 20 million records. These products get updated on a daily basis and anywhere from 100K - 1 million records are affected each day.

We have a online read only database as well that holds a watered down version of the product record, a basic flat structure of the most crucial fields.

What would be the best way to keep the online version up to date, but have it updated outside of working hours?

I have 2 ideas, but not sure if either are the best or even plausible.

1. Create the update/insert queries that will populate the online version and that will connect form our internal system to the online version and run it as a job each night at a certain time.

2. Setup some sort of replication, Log shipping? I realize that in this option, I will need to create a local version of the online table(s) and populate it with the same queries used in step 1, but then the replication will handle the actual data transfer etc.

Or is there another way of simplifying this task?

Thank you.
Post #1361307
Posted Tuesday, September 25, 2012 10:42 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:21 AM
Points: 7,135, Visits: 12,749
Have you explored Change Tracking?

Change Tracking Overview


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1364430
Posted Tuesday, September 25, 2012 11:01 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, November 23, 2014 5:13 AM
Points: 231, Visits: 759
Maybe SSIS execute sql task
Post #1364432
Posted Wednesday, September 26, 2012 12:16 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, August 18, 2014 3:04 AM
Points: 1,331, Visits: 15,269
ESAT ERKEC (9/25/2012)
Maybe SSIS execute sql task


This gets my vote as what you after is a denormalised version of the data which logshipping and replication is not going to give you (without a lot of development anyway).

With some sort of change tracking, timestamp etc you can update only what has changed as well.
Post #1364450
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse