Knowledgebase

Search:     Advanced search

Using Replication with TestTrack Projects Stored in a SQL Server 2000 Database

Article ID: 391  |  Last updated: 31 Dec, 2014

SQL Server 2000 data replication is based on a publishing model where one server (called a Publisher) shares it databases (called Articles) with other servers (the Subscribers). Processes called "agents" run in the background to keep the data in check and, depending on the selected replication method, send a snapshot of the data from the Publisher to the Subscribers, send all new transactions from the Publisher to the Subscribers, or merge the data from the Publisher and all Subscribers together and keep the data synchronized on all servers.

You can use snapshot and transactional replication if you need to move the reporting off of the main server or if you need to use data warehousing. This is useful for reporting and analytical purposes and these two replication options will work. Keep in mind that you cannot connect the TestTrack application to the Subscriber database because it will not load the data.

Merge replication will not work with the TestTrack application and should not be enabled. Enabling merge replication will cause severe issues at the main Publisher database because it adds a new column to every table that acts as the global identifier. TestTrack will not work properly if this column is added because it changes the table structure.

Article ID: 391  |   Last updated: 31 Dec, 2014
Tags
SQL Server replication

Prev   Next
Changing the Response Buffer Limit in Microsoft IIS 7 and Later     External Reports Are Not Displayed in Internet Explorer on...