| Thread | Last Post | Replies |
|
| how to force metadata cleanup | 29 Sep 2007 04:08 GMT | 1 |
We have a merge replication system with: 1 (2K5) Publisher 100+ Pull (2K) subscribers (U.S. & Canada) 89 tables replicated
|
| transactional repl - what's behind the scene | 29 Sep 2007 04:02 GMT | 3 |
In the Books online it says : Replication is a set of technologies that allows you to keep copies of the same data on multiple sites... Could someone give me an answer on what is the 'set of technology' that keeps the transactional replication running. Does it use DTS packages (or ...
|
| Basic questions about choice of replication methods | 29 Sep 2007 03:57 GMT | 1 |
Here's out situation: We have a database with about 50 million records, full text indexing is enabled for one column. About 200,000 new records are added every day replacing an equal number of records that expire. All updates to the
|
| Mod Primary Key | 29 Sep 2007 03:40 GMT | 1 |
I have a table in a merge publication with 11 subscrber. I need to modify the primary key of the table. Now the table have a primary key of one column. I need a primary key of two column. How can I do ?
|
| Reinitialization count | 29 Sep 2007 03:39 GMT | 1 |
Does anybody know the best way to query the system tables to count reinitializations that have occurred? We are beginning to have some performance issues with our replication setup, and we are trying to find some trends (we have been archiving off the data from the system tables ...
|
| Changing the data type of a table that is a part of replication sc | 29 Sep 2007 02:27 GMT | 1 |
I have a replication table. However one of the field's datatype needs to be changed. The system does not allow me to do so. However I must change the field. How can I do so? Thanks
|
| How to Replicate an SQL Server 2000 Database | 28 Sep 2007 21:50 GMT | 12 |
Hi, i am new to this so really need some helpfull and easy to follow information so that i can successfully replicate my SQL Server Database. Here is my dilema. I have a working SQL Server 2000 Database which has an IP address and alias so can be connected to by the outside world. ...
|
| Replication - Disk to Disk | 28 Sep 2007 19:48 GMT | 1 |
I'm at a place where they are (SS 2000 SP4) replicating from one drive to a different drive. But, come to find out, that really the way the SAN is laid out, these drives could very easily all share the same spindles/heads. Now that's madness isn't it? Even with cache, isn't ...
|
| History retained at subscriber - msmerge_contents | 27 Sep 2007 21:58 GMT | 2 |
I have a sql server 2000 SP4 publisher and a sql server MSDE SP4 subscriber. After applying the initial snaphot I can see the inserted record information remains in the msmerge_contents table. Is this normal behaviour? Is there a way to prevent this. Our database is approximately ...
|
| Publish from duplicate databases | 27 Sep 2007 16:13 GMT | 2 |
are running Sageline 200 with sql 2005 backend. On out system, we have two companies,each in a seperate database, both with identical tables and schemas. I want to replicate some of these tables inro a single table on a remote
|
| Business Logic in a mergue replication | 27 Sep 2007 16:03 GMT | 1 |
I have a merge replication scheme, where the synchronization request makes the clients. I need that when finishing the synchronization, in the publisher executes a procedure. Somebody knows since I can do this? Thanks Miguel
|
| Merge Replication nested view replication problem | 27 Sep 2007 16:03 GMT | 1 |
I am using SQL 2005 as pub and SQL EXPRESS as sub with Merge replication. Got the following error message The schema script 'CD_InTransit_v_153.sch' could not be propagated to the subscriber.
|
| Getting error 14294 when creating a snapshot publication from db | 27 Sep 2007 15:15 GMT | 1 |
I'm getting the error: Error 14294: Supply either @job_id or @job_name to identify the job. Any idea to solve this problem. Thanks,
|
| stop table replication | 27 Sep 2007 15:10 GMT | 1 |
I deleted about 3 million rows out of a table that is being replicated. So now, it is sitting replicating those 3 millison deletes to the 2 subscribers. What can I do to get it to stop replicating all of those deletes and start replicating the actual changes that have occured over
|
| Merge Replication - Column level tracking doesn't work properly - SQL Server 2000/2005 | 26 Sep 2007 14:33 GMT | 1 |
I've a problem regarding the merge replication process when using the column level tracking, on either SQL Server 2000 or 2005 (the behaviour is exactly the same). I don't know exactly what I'm doing wrong here.
|