February 13, 2006 at 7:31 am
Looking for opinions - I need to make some changes to a database and am looking into staging tables and replication. I know very little about either of them. I am looking to get real time results from some servers that monitor production machines run and down times. Currently we are using a data pump to get the data across but the time has come that we need to get the information closer to real-time rather than hourly updates. Any articles or publications that would help me through this process and what would be the preferred option? Thanks
Kurt Kracaw
February 15, 2006 at 2:41 am
Not quite sure what you mean by changes to a database?
If you want to copy data from one SQL box to another, and the second box requires a read-only copy (i.e. will not make changes to the data), then I suggest using snapshot replication. Just search this site and you will find several useful articles.
Just note that once replication is enabled on a table, you cannot easily modify the structure of the table, which is why I ask about changes to a database.
February 15, 2006 at 6:19 am
Sorry for the confusion. ‘CHANGES’ was the wrong term to use here. We have not made any changes to the structure of the table for a long – long time. What I was referring to was, the fact that we need to change the way we pull the data across to a server (DTS) we need the information to be real time or as close to real time as possible. Currently we have 3 servers pulling data from the production floor and then the data is put into a master server. On another server we pull information from 3-4 other servers plus the information from the master server, some of the information is placed directly in tables other information is combined with information from other servers to create a table. Is snapshot the way to go with this. Certain tables get dropped and recreated hourly some once a data. On a previous post I was told this was a normal Data Warehouse function but is seems to be slow and is getting slower al of the time. Is replication the way to go?
Kurt Kracaw
February 15, 2006 at 6:49 am
I would certainly like to hear other views, but my 2 pennies is that snapshot replication would be more efficient than dropping/recreating tables. As long as the vast majority of the data does not change often, you could set up the initial snapshot and then synchronise the data as often as you like (we run some syncs every 1 minute).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply