Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
martind10
Starting Member
6 Posts |
 Posted - 2004-10-11 : 06:19:25
|
| This looks like the right forum - so here goesOur customer has a SQL-Server database that acts as a 'mirror' for reporting purposes from the transactional production system, which is actually a multi-value database (D3). We are moving the production system to our data centre, but our customer needs reporting available locally in real-time. The 'mirroring' process (using ODBC) is too slow to keep up with the volume of new data being mirrored, even across a 2MB line, so my solution is this:~'Mirror' the production database to a SQL-Server at the data-centre. Use either replication or DTS to transfer the mirrored SQL data to the existing SQL Server at the customer end. (assuming this must be faster).My problem is this - transactional replication (and snapshot) both require a unique primary key on every table - the sub-tables spawned by the multi-value database do not have a unique primary key, which leaves me with 'Merge'. There are no transactions on the subscriber database at the customer end, but merge requires a two-way integrity check, and would appear to be too slow. Is there a way of using DTS to keep the remote database up to date with the master database at the data-centre?A delay of a few minutes would be acceptable, but our customer requires quite heavy reporting in pretty much real-time.Martin |
|
|
martind10
Starting Member
6 Posts |
Posted - 2004-10-11 : 07:55:36
|
| Or Should I consider using log-shipping?Martin |
 |
|
|
|
|
|
Ongoing DTS or replication