April 8, 2009 at 1:29 am
Hi there,
We have a transactiional repl proces going, which runs smoothly. Last week however we had to implement a lot of changes in the databases concerned: new tables and changes in existing tables. The SQL Server instances where stopped, the changes applied, Services started again and repl proces initialized. This ment making a new snapshot, and this took 18 hours to run. This is understandable if you look at the data involved: databases are more then 100 Gb, in which 3 troublesomely very large tables with over 100 million rows each.
This snapshot proces caused a lot of performance issues. I am looking for ways to bring back this runtime for the initial snapshot creation, but sofar Googling has not given me an answer for this particular situation. I repeat: the replication proces itself is not the problem, it's the initial snapshot.
What should I look at for a solution? The databases need to be synchronized realtime, not exactly 7x24, but close to it(7x18). If ever there is a problem and these machines need to be re-initialized during the working week I know what is going to happen at the Helpdesk.
Should I look at another replication solution?
Tia,
Hans Brouwer
Greetz,
Hans Brouwer
April 14, 2009 at 2:34 am
Nobody any comments?:crying:
EDIT: Never mind, found an article on the subject: http://technet.microsoft.com/en-us/library/ms147834.aspx
Greetz,
Hans Brouwer
April 14, 2009 at 11:40 am
If you can tell which tables are going to be modified maybe you just need to snapshot "only" those tables plus the new ones and be done in a fraction of the total snapshot time.
* Noel
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply