March 21, 2003 at 8:16 am
Hi,
I have multiple SQL Server Engine boxes located in different locations. I plan to setup Replication to get data from those boxes periotically like twice a day using dial up. All SQL Server Enginea are SQL 7.0. There is one table need to be replicated.
Can anyone advise the practice you like best?
Thanks!
Jie Ma
Jie Ma
March 21, 2003 at 8:39 am
If you are going to use replication with dial up you must send not too much data, so I would recommend you use Transactional replication to send only the incremental changes.
Once you configure the replication, check the job that calls the distribution agent and disable it.
Then every time you connect with your dial up connection, execute a script that start that job to start syncronising the tables. You then can check for the status of the replication in tables like distribution.dbo.MSDistribution_History and distribution.dbo.MSRepl_Errors to know when to cut the dial up connection.
March 21, 2003 at 11:23 am
Thanks Racosta!
I do not know how fast data will be increased, but I can schedule more connection per day if data size grows quick. One fact is that the table is transaction table and record in the table will not change once it is created.
Do you think Transaction Replication is the best choice or Snapshot?
Thanks agian!
Jie Ma
Jie Ma
March 21, 2003 at 11:57 am
When I say incremental changes, I meant insert, updates and deletes to replicated tables. This can be always the same, or not, it will depend of how much transactions and users are executing.
I would use Transactional, because snapshot even if it is a small database will last more time that transactional replication.
Remember, that transactional replication only delivers, all the inserts, updates and deletes executed in the tables, but if no transactions are executed, it won't deliver anytinh.
But with snapshot replication, you always "deliver" the entire database.
March 21, 2003 at 1:04 pm
Thanks Racosta!
Jie Ma
Jie Ma
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply