In this product review Andy takes a look at Data Compare, the second of three products in the SQL Bundle available from Red-Gate software. It's a very handy program that lets you compare data between two tables and optionally generate sql statements to syncronize the data. An interesting alternative to replication!
2001-10-31
8,792 reads
This paper examines performance in transactional replication and demonstrates ways in which you can improve the performance of your applications. (30 printed pages)
2001-10-08
1,868 reads
The SQL Server 7.0 Data Transformation Services (DTS) Object Transfer feature transfers logins and users between two servers, but it does not transfer the passwords for SQL Server authenticated logins. (DTS in Microsoft SQL Server 2000 does transfer passwords.)
2001-10-01
1,650 reads
In our environment, we needed to create and drop replication over and over in our test environment and I got realy tired of having to manualy go to each table with an identity column to set its ranges. This sproc will create or drop the publications and/or subscriptions for all or some of the objects […]
2006-11-15 (first published: 2001-09-05)
743 reads
Microsoft® SQL Server™ 2000 allows you to restore transactional replication databases without reinitializing subscriptions or disabling and reconfiguring publishing and distribution. You can set up replication to work with log shipping, enabling you to use a warm standby server without reconfiguring replication.
2001-08-21
2,176 reads
If you have Microsoft Windows 2000 or Microsoft Internet Explorer 5.0, Pull subscribers can use the Windows Synchronization Manager (WSM) to synchronize with the publisher.
2001-06-11
1,664 reads
An introductory article from Microsoft on the newest version of SQL Server: SQL Server CE designed for Windows CE devices. Includes some ideas for where this version fits in your architecture.
2001-05-30
1,721 reads
Replicating continuously minimizes latency, but at a cost. If you're replicated a lot of databases, read this article for some ideas about how to trade latency for overhead by runnig your agents in non-continous mode.
2001-05-15
4,717 reads
If you allow users write access to replicated tables on the subscriber, you can run into cases where a record is inserted on the wrong server - which will result in a replication stopping error if the same primary key is later inserted on the publisher. Find out how to fix it without pushing a new snapshot.
2004-10-15 (first published: 2001-05-04)
9,637 reads
Need to make changes to table that is an article in a publication? Read this article to get step by step instructions on how to do it without doing a new snapshot!
2001-05-02
8,242 reads
I did a couple of posts previously on dumping/restoring Azure PostgreSQL databases and also...
By Brian Kelley
Most of us know that spending a lot of time on social media and...
By Steve Jones
Redgate Monitor is growing to include more than just Microsoft SQL Server monitoring. We...
Comments posted to this topic are about the item Hash Joins IV
Comments posted to this topic are about the item How to Load a Fabric...
Comments posted to this topic are about the item Adding the Right Value