I'd like to be able to poll a SQL 2000 subscriber database to obtain the current replication status. For example, I'd like to know when the subscriber is sitting idle (e.g. "waiting for changes..."), when it is actively replicating (e.g. "applying script..."), or when it is in an error state (e.g. "The Merge Agent failed...").
I realize I can query the table MSmerge_history which contain a comments and error_id field that may be useful. However, there is no status field that I could easily code against.
I need to know how can i see the replication status. I have 4 servers with ms sql 200 standard server and hundreds of commnad to replicate. Sometime is important to know how mush of this commnads is replicated. Thank You.
I currently have a transactional replication between SQL Server 2000 and an Oracle database. Once a week on Monday mornings we have a process that drops replication, uploads data to the SQL Server database from Oracle, does some manipulation of the data and then recreates replication.
We came across the thought of what would happen if replication had erred out and there were still transactions within the distribution database to be replicated across. Then our job just came about and dropped the replication.
We are looking for a way to tell what the status is of replication through Transact-SQL. This way we can check the status and if it contained an error that we could abort the job, so as to not lose any transactions.
Does anyone have an idea of how to accomplish this?
Does anyone know how to check when a distribution job has finished distributing a snapshot programatically?
I am writing an app that adds subscribers programatically. It first add the subscription (which creates a new snapshot) and after the snapshot is done, the distributor gets invoked automatically. Because I need to access the subscriber database after the publication is pushed I need to wait until the distributor has finished its work.
Hi. I have setup an SQL Server 2005 Merge Replication. Now I need to display the status of the replication programatically from the subscriber side, I have checked the documentation which mentions MergeSubscription & MergeSubscriberMonitor but I couldn't know how to use them!! Any Help ? Thanks
To monitor the status of replication in SQL 2000 we insert the resuts of sp_MShelp_replication_status into a temp table and review the status. In SQL 2005 this stored procedure has changed and now does it's own insert into execute command. Since insert execute commands can not be nested we must find another way to programically monitor replication using TSQL. We could call sys.sp_replmonitorhelppublisherhelper but we can't seem to find it in the distribution database. It must be hidden somehow. Any ideas?
Hi guys , may I know is there any examples of store procedure/scripts for monitoring replication status and performance ? I just know about sp_replmonitorhelppublisher. Thx for the assistance.
Hi, I have no idea of SQL2000.Can anyonetell me steps /precuations involved in going for Replication in SQL2K. Also,How do we do log shipping in SQL2K? TIA pd
I am trying to set up transactional replication (not immediate updating) via a push subscription between a SQL 7.0 Server and a SQL 2000 Server. The SQL 7 server is the Publisher / Distributor, and the SQL 2000 server is the subscriber. Replication will not work between the two, I have removed then setup replication to no avail. The SQL 7 server always reports that it can't connect to the SQL 2000 server. Same problems the other way if I try a pull subscription.
I'm trying to replicate a sql 7.0 table to a sql 2000 server. Does anyone know how I can register a sql 2000 box through Ent. Manager onto 7.0? I've been told that I need to upgrade my production server's Ent. Manager to 2000 but I not sure if that is a real safe bet. Can anyone give me any insight to this?
I am trying replication on sql 2000 I want to do replication using two databases. suppose say Db1 and Db2 if new record is added in db1.table1 then the same record should get added to Db2.table1 and vice versa.
using enterprise manager I have successfully created replication from Db1 to Db2.
how to do it from Db2 to Db1? any suggestion would be helpful. thanks
How do I know whether the record in a row was insert,update and delete that replicated to a subscriber? Is there a flag or an indicator in msmerge_contents,msmerge_tombstone ,msmerge_genhistory tables or any other msdb/replication system tables?
I would like some simple input on achieving true two-way replication with SQL 2000. We have need to load balance our website between two sites and since it is SQL based, would need to have dual DB servers at each site with two-way replicated data. They would need to be replicated at real-time. Will the built in SQL replication tools work OK? Has anyone done this? Thanks in advance.
Here is what we are trying to solve:-We have a SQL 6.5 server (version 6.50.258) we will call SQL65-A, onan NT 4.0 machine (version 4.00.1381), on Domain-A-We are trying to replicate directly to a SQL 2000 server (version8.00.818) we will call SQL2000-A, on a Windows 2000 machine (version5.00.2195), on Domain-B-We also have a SQL 6.5 server we will call SQL65-B in Domain-B-The domains are trusted-We get the error that it cannot connect to the SQL 2000 server whentrying to replicate, even though I can register the SQL 2000 server asa Remote ServerThe work-around we have right now is replicating from SQL65-A toSQL65-B, then using SQL65-B as a subscriber as well as adistributor/publisher to SQL2000-A.
I doing a transactional replication with two servers. Server A, the Publisher and Distributor. Server B, the Subcriber. I did the replication using a dummy DB for practice purpose and it works fine. When I try to implement the replication in original DB, I found that some tables don't have primary keys and to be able to implement transactinal replication all the replicated tables need to have a primary key. I want to add the primary keys to those tables and also implement the replication but the problem is those tables have data in it. I'm thinking in create the new table and do a DTS to import the data to the new table or it's fine just to modify the table in design to add the primary key "Those table have record in it".
I am using MSDE 2000 for replication of my Data. I have one publisher and two subscribers. but i need t filter rows for publications. Problem is that for filtering, i need host_name and in push replication host_name is name of system in which Agents are running but in MSDE all agents are running in publisher system ( distributor System). so everytime for any publication i get only id of server. i am facing same problem in pull replication also.
Any suggestions on how to replicate from AS/400 to SQL Server 2000?
Data is stored on a AS/400, but applications use a SQL Server 2000 DB. Currently, DTS packages drop the SQL DB, rebuild the tables from a script, copy the data, and then rebuild the indexes as a nightly batch job. Is there a better way to do this? Also is there a clean way to replicate daily transactions as well?
This may be in the wrong forum, but I have a database in SQL Server SP3a that I will be replicating out to SQL Mobile 5.0. The setup of the replication will not be a problem, however, once replication is setup, I will have to change the DTS Package that creates these tables.
I have created a DTS Package that drops the tables and recreates them from a DB2 database. My problem is that I won't be able to drop these tables once a publication has been established.
I really don't need to drop the tables if I can create a script to pull just the new records from the DB2 database.
Does anyone know of an easy way to do this? Are there any products out there that would make this easier? Has anyone else out there had to create a publication with this scenario?
Just a little background, I originally created the DTS Package from an import, and then modified it. I added the DROP TABLE scripts so that I wouldn't just append the same data over and over. Perhaps there is a better way of doing this than a DTS Package.
This would probably be a lot easier to handle if I weren't pulling from a DB2 database because I would probably be able to create a trigger or something on the source database, however I know nothing about DB2 datasets other than how to pull the data out. I would appreciate any input on this.
I'm trying to determine if it is possible to do many to many replication in sql server 2000.
What i basically want is to have n databases share the same basedate (share a common database) and allow updates in any database to be replicated to all the other databases (with a simple conflict resolution, like last update wins).
My goal is total autonomy, without a single point of failure. If any node goes down, the other nodes will continue to work and continue to replicate their data to the remaining nodes. When a node comes back up it will catch up with the over nodes (or get reinitialized if it was a serious crash).
The amount of data i want to replicate is not that big (less than 100MB) and does not change that often. All servers are sql server 2000 instances connected by a gigabit network and the number of nodes involved is less than 10. Some latency is also acceptable.
the question is: is this at all possible? I have read i bit in 'SQL Server High Availability By Paul Bertucci' and some other resources and it looks like a multiple publishers or multiple subscribers with merge replication setup should work, but i'm not too sure if it will work for n > 2 nodes (where all nodes publish and subscribe to each other) and it also mentions constraints on which data a given node is allowed to update (i hope this could be handled by simple conflict resolution).
And if it is not possible in 2000, could it be accomplished en 2005?
