Merge Replication Issue With Records Not Being Copied To Subscriber
I have an issue with merge replication between sql2005 sp2 and spl2000 sp4
the merge replication runs fine to 6 other sql servers
but the sql2000 sp4 server has a lot of locking going on, but the merge replication doesnt fail it just loses several hundred records without notifying me
I have to manually copy the missing records every week or so
I have dropped the replication and rebuilt it twice but it still happens
View Complete Forum Thread with Replies
Related Forum Messages:
Purging Records From Subscriber/publisher Database In Merge Replication
Are there any standard approaches used to purge records from databasein merge replication senario ?We are using merge replication between two sql server 2000 databases.These databasess have differnt purging frequencies ( purging frequencyof subscriber database is 6 month where as that of publisher is year).Is there anyway to purge data from subscriber and publisher withoutgetting these deletion reflected in replication ( basically deletingrecord bypassing the replication).
View Replies !
Merge: Records Associated By A JOIN Filter Not Being Sent To A Subscriber
Hi, I have a merge (SQL 2005 Standard -> Express) topolgoy which is having problems The main problem is that the join filters don't seem to work for one area and I am hoping someone can help me with some troubleshooting advice There are 140+ tables in the topology but the ones causing particular pain are a parent child relationship where the child is actually a bridge/linking table to another table. Therefore although it is a parent child in the replication filters it is the reverse. i.e. the child has the paramterised filter on it and the parent is one level down joined by it's id. There are other tables joined to this parent table but it stays at three levels deep. The @join_unique_key therefore is set to 0 as is the partition options for the parent /child relationship. However, when we synchronise we have a problem. The rows get inserted in to the database in RI order but only the child records are replicated down to the subscriber. The child table with the parameterised filter has 13 articles joined to it in total and one of the other branches of join filters go down as deep as four levels. Most though do not. Does anyone have any suggestions as to why this might be happening? Any help would be greatly appreciated. Cheers, James P.S. I should add this problem only occurs when the edits are made at the publisher. If new records are added at the subscriber everything is fine.
View Replies !
Merge Replication Subscriber
SQL Server 7.0 SP3 I am using the "Pull Subscription Wizard" to set up merge replication. I go through all the steps of the wizard and then I hit "Finish" at the end. When it gets to the third step (Creating the Subscription), I get the old: __________________________________________________ _________ mmc.exe has generated errors and will by closed by Windows. You will need to restart the program. An error log is being created. __________________________________________________ _________ This happens whether I try to do this from my PC or from the actual server I am creating the subscription on. Has anyone else had this issue? Is there a hotfix I need? Any help is appreciated. Thanks, Craig
View Replies !
Push Subscriber In Merge Replication
I am using merge replication with a push subscription type. I am wondering if the updates of the tables on the subscriber side are push to the publisher from the subscriber or pulled from the subscriber by the publisher when the syncronisation takes place. this makes a big diferrence for me and i can't find the answer to this question anywhere... if anyone could answer it would be really appreciated Thanks
View Replies !
Merge Replication Subscriber Status
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
View Replies !
Merge Replication - Subscriber Error
Hi, I have setup merge replication between SQL Server 2005 and SQL Server Express. The setup uses web synchronization. (And the setup uses dynamic filter HOST_NAME) On some of the client machines, replication fails with the following error (when initializing the subscription): from subscriber merge agent verbose log: A dynamic snapshot will be applied from 'D:DOCUME~1JBAUMG~1.CORLOCALS~1TempDB101-EQA-SCL_BQDB_BQ_PUB_BQDB' Validating dynamic snapshot 2007-04-1819:39:45.434 OLE DB Subscriber 'FRG-BAUMGARTENJSQLEXPRESS': sys.sp_MSregisterdynsnapseqno @snapshot_session_token=N'\XXX.XX.XX.XXSnapshotuncDB101-EQA-SCL_BQDB_BQ_PUB20070417180079dynsnap', @dynsnapseqno='5599F67E-A1A9-4573-A14F-9851F6FE4B51' (Note: XXX.XX.XX.XX is a proper IP of DB, I have just masked it in the post) The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file.When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. I enabled verbose logging for the snapshot agent for the subscriber, but there was no error there. It is obvious from the log info above that the error occurs only after downloading the snapshot to the client and during applying it to the subscriber by the merge agent. After I got this error, I tried running the subscriber program again and it successfully replicated on the third attempt. But this behavior is not consistent and it fails for most of the time on some of the machines Any info on this error?
View Replies !
Deletes On Subscriber In Merge Replication
Using Merge replication between SQL Server 2000 and SQL Server CE, is there any way that row deletes could occur on the subscriber without a reinitialize or explicit delete of row on publisher. More specifically, if there is a row filter that returns a days worth of data with each days pull, for example, and the filter looked like select <columns> from Table where UpdateDate < GETDATE() and UpdateDate >= DATEADD(d,1,GETDATE()) would there be some implicit delete at subscriber each day because data sent changed? My research indicates this does not happen, but I have a colleague who thinks differently.
View Replies !
Merge Replication SQL Mobile Subscriber To Cluster (What Is Best)
Hi All I have been using some of the basic feature of merge replication from an sql mobile subcriber for some months now with good success. We need to however create a cluster server scenario for other requirements of the project. We have tester our system with both NLB and MSCS cluster setups. What is the best option for compact merge replication and how can this best be achieved to attain load balancing and failover using a cluster server? Nick
View Replies !
Merge Replication, Subscriber Can Only Download But Not Upload??
Hi, I need a urgent help! The problem is that every synchronization only transfer data from subscriber to publisher, but not the other direction. The publisher is sql server 2005 standard edition, and the subscriber is 2005 express. Is that any stored-procedure to deal with such a problem? Thanks for any commnet.
View Replies !
Merge Replication: Missing Rows At Subscriber With No Conflicts
Hi all, We are using a mix of SQL 2005 and 2000 servers and our "main" database server is running SQL 2005 x64 (SP2 ver. 3042). Our system has run perfectly for months, then subsequent to an SP2 update we are seeing several instances where the data record counts are different for several tables among all the servers. We are using Merge Replication, with no filters and published every 2 minutes. Any ideas? TIA, Michael
View Replies !
Merge Replication Error: The Schema Script '....sch' Could Not Be Propagated To The Subscriber
I tried setting up a Merge Replication between a MSDE (PullSubscription) and Sql Server 2000 (Publisher) and got the followingerror:The process could not enumerate changes at the 'Subscriber'.Then I created another subscription, but this time, a PUSH, and thistime I got the error "The process could not connect to Subsciber".I tried creating a second PULL Subscription, but the error I got was:The schema script '....sch' could not be propagated to the subscriberAnyone have any ideas how to fix this?Thank you.
View Replies !
Merge Replication Subscriber Error: Invalid Cursor State
These errors occur at the subscriber. First, "The merge process could not query the last sent and received generations" is generated, then immediately afterwards, "invalid cursor state" is generated. We are trying to pull a new subscription snapshot from the republisher. The subscriber has been added and removed from the replusher's pull subscriptions a number of times for testing. Now, we cannot get the subscriber to re-sync with the republisher. Any ideas?
View Replies !
Merge Replication: Initial Merging Of Data On Subscriber And Publisher
Hi All, I am trying to start a merge replication whereby i have data on both subscriber and publisher that needs to be merged initially. I tried starting the subscription and specified that the subscriber already has schema and data. And it seems that it didnt do the initial merging of data in the subscriber and the publisher. Is there a way to do this ? Thank you in advance, Adrian
View Replies !
Error While Propagating Initial Snapshot To Subscriber (Merge Replication)
Hi all. I get the following error when trying to run a pull subscription from the subscriber: The schema script '' could not be propagated to the subscriber. (Source: Merge Replication Provider (Agent); Error number: -2147201001) --------------------------------------------------------------------------------------------------------------- The process could not connect to FTP site 'ftp://ESOFTSERVER.NO-IP.INFO' using port 21. (Source: ESOFT (Agent); Error number: 0) --------------------------------------------------------------------------------------------------------------- The connection with the server was reset (Source: (OS); Error number: 12031) --------------------------------------------------------------------------------------------------------------- I've tried everything I could to solve this problem, but I can't get it working. Thanks for any advise. Fabio Reynoso
View Replies !
URGENT Merge Replication: Missing Rows At Publisher And Subscriber: No Conflicts
We have SQL Server 2000 with merge replication at a Publisher and subscriber. We have some records getting deleted at Publisher and Subscriber and no conflicts are logged. We have tried the compensate_for_errors setting and this has had no effect. This is causing serious data corruption and has now become an URGENT issue. Out tech team are almost out of ideas. Has anyone experienced this or have any ideas as to what to check next?
View Replies !
Merge Replication Issue
Hello, I have a merge replication problem. I have one publisher/distributor and roughly about 40 subcribers to a replicated database of about 10 gig in size. I'm using SQL 2000 and have Sql sp3 on all my machines. I wanted to do some maintenance on my publsher and so I changed in the subscriber's job schedule the "Start Date" to be the next day. I don't know why but this caused the replications between the subscribers and the publishers to fail. The error message I received stated the following, "The process could not check the existence of the generation at the 'Publisher'". This message would appear after a 10 minute delay. So, I decided to change the "Start Date" back to the original date and just synch one of my subscriber. It started synching alright, but it seems to be going through several generations. It has taken the subscriber over six hours to synch and it has it not finished. I need to know if this is normal and how can I shorten the process. I thought it would just synch back with the publishers and upload the 1-day changes and not go through all the generations. Thanking you in advance for any assistance with this issue
View Replies !
Merge Replication Issue
Hi, I am trying to delete a Merge Publication on SQL Server 2000 SP3 and it won't work because an article (a table) that was part of the publication was deleted and recreated before dropping the publication and now when I run sp_dropmergepublication or sp_dropmergearticle, it fails because of that table. Please Help
View Replies !
Merge Replication Dropping Records
Hello, I have SQL server 7.0 sp3 running on a small business server. This server has several remote Small Business Server SQL 7 databases connected to it through merge replication via FTP pull subscriptions. All data is being input at the remote locations. For some reason during the replication process some of the records are being deleted at a couple of the branches. I first thought is was related to only one table, but now I find that it is happening in another table.
View Replies !
Sql Server Merge Replication Deleting Records
Hello, I am having problems with my sql merge replication. Whenever a user syncs up to my main database, most of their records are deleted instead of being merged. Or the records on the main database are inserted and it replaces the whole table with the records on the remote laptops. Is there a way to prevent this from happening? Someone please help me. Corey
View Replies !
Merge Replication Issue - One Column Not Replicating
We're running merge replication between to SQL Server 2000 servers. Theapplication isn't very high volume the setup is pretty vanilla (ie nofilters, etc).We have a push subscription set up and we seem to replicating databetween publisher and subscriber, with one exception:When we update a particular int column at the publisher, the updatewon't propogate to the subscriber. Updating the same column at thesubscriber does result in an update at the publisher.All other columns in this article seem to replicating without aproblem.Anyone have any insight as to why this would be happening?Thanks,Joe
View Replies !
Merge Replication Alter Table Issue
Hi all, I would just like to know is that possible that to alter the table (as in add in new columns to tables or changing the field type) in a published merge replication? Currently what I have to do is stop the replication, delete the subscription, take the table out from the published list, alter the table and put everything back on, but its kinda slow as the snapshot agent needs to run again which then copy all the data across again (I know I can assume the subscription have the schema and data so not copying the data across). But I'm sure there should be some other ways to do it, since I should be able to change the shema of in the published tables and it should flow through to all other server isn't it? Or is there any other method to do this? Thanks for all the help. Westley
View Replies !
SQL Merge Replication - Remote Connections Issue
Hi, I need to perform merge replication between 2 Win 2k3 machines. Both machines use SQL server standard edition 2005. I have set up a publication on server A. When I tried to do a subscription on server B i encounter a remote connections not allowed message. I have made both Server A and Server B remote connections available via named pipes and TCP/IP. I can verify that remote connections to Server A is working perfectly cause I have a C# program that writes to Server A database via a connection string, and this C# code resides on a remote machine. Please advise me on how to perform merge replication since I am unable to resolve the remote connections issue and what settings I should use to minimise my security risk (eg: maybe i only need to allow remote connections on A??) Thank you
View Replies !
Merge Replication Issue SQL Server 2005
I have set up merge replication with 1 publisher and 1 subscriber. Distribution is handled by a 3rd server. I can generate a snapshot at the publisher and apply it to my subscriber. But when I insert some data (approx 30,000 rows) , the Synchronization agent gives the following error when It runs: The merge process is retrying a failed operation made to article 'xxx' - Reason: 'The Merge Agent was unable to synchronize the row due to one or more unanticipated errors in the batch of changes. When troubleshooting, increase the -OutputVerboseLevel setting, restart the agent, and check for and resolve any errors generated by the database engine. '. I have increased the OutputVerboseLevel setting and specified a file path in the -OutputMessageFile but the File is not being populated. All the references on books online say to put the file path in the -Output parameter but when I do it says it can only hold an integer value. So I cant see the errors generated by the database engine. Could anybody please assist with this issue? Thanks
View Replies !
Issue With Join Filters In Merge Replication
hi guys ..hope you all doing well... I am new to Merge Replication and I am having an issue using Merge Replication filters... I am sure somebody here must have come across the issue... I have 3 tables in my Publication Users, Orders, OrderItems... Users have 1-* relationship with Orders and Orders have 1-* relation ship with OrderItems. In my application, Users create Orders and Order Items. While creating Order Items, an item can be assigned to a different user to review it. So OrderItems table also have AssignedUserID (foreign key with Users table) in it. Now when the user syncs, I want to filter out all the Orders and OrderItems that belongs to that User. To do this, In my Publication i have got a root parameterisze filter on Users table based on UserID. The Users table have a join filter with Orders tables which in turns joins with OrderItems. This is fairly simple and works smoothly. The join filters looks like Users filter: Users.UserID = HostName() ---Orders filter: Users.UserID = Orders.UserID ---OrderItems filter: Orders.ID = OrderItems.OrderID Now in addition to this, what i also want is to filter out all the OrderItems that have been assigned to the user. For this i put an OR condition in OrderItems to check on AssignedUserID. The filters look like this Users filter: Users.UserID = HostName() ---Orders filter: Users.UserID = Orders.UserID ---OrderItems filter: Orders.ID = OrderItems.OrderID OR OrderItems.AssignedUserID = HostName() ...but when i sync, the OrderItems with AssignedUserID doesnot get downloaded. I am not sure how to achieve this? Deos anyone have any idea how can i do this? I have treid different combinations of Joins but no joy. somestimes it gives me foriegn key violation error and sometimes it downloads all the Users, Orders and OrderItems without performing any filtering.
View Replies !
Change A Merge Subscriber To Become A Merge Publisher
Hi, I'm using merge replication to maintain a backup copy of my main (publisher)MSDE database. A push subscription periodically (1 per minute) updates the backup DB. It's intended that if the main db goes down then the backup (subscription) db can be configured as a publisher. This must all be performed via scripting. The initial configuration of the main publisher and subscription is controlled via scripting, which works fine. The problems occur when I try to configure the subsciber to become a publisher. A script is executed on the subscriber but fails at the point when it's configuring the publisher detail. The error is something like "unable to configure a publication for a database setup as an anonymous subscription". I'm guessing that there are subscritpion artifacts added to the database which need to be removed before it can be configured as a new publisher. Please help, Jez W
View Replies !
Replication SPs Copied W/CRLF In Names
Hi folks - New DBA (longtime developer) here. I've just noticed something strange on a couple of my databases (SQL 2k). There are some stored procs that have a CRLF or CR+CRLF prefixing the name (they show up as unprintable-char black squares in EM). They all appear to be replication-related SPs (e.g. ). The names are as follows: sp_MSdel_<replicated_table_name> sp_MSins_<replicated_table_name> sp_MSupd_<replicated_table_name> There are corresponding normally-named SPs. Not all the replication-related SPs have been copied this way. The create date of all the new SPs is the same, and is (IIRC, I wasn't involved then...) the date of the SP4 application to the server. Anyone ever seen this? More importantly, is there a way to determine if these SPs are being used? I'd like to delete them if I can, but not until I'm sure of what's happened. TIA for any input.
View Replies !
Merge Process Could Not Enumerate Changes At The Subscriber
Hi, I've seen quite a few posts about this error message but so far no answers. I'm merge replicating between SQL Server 2005 SP2 and SQL Server 2005 Mobile. Everything seems to run really well until at some point I get the above error message while running the replication from the device. It seems to happen just after I've made a schema change on the server e.g. the latest one was adding some new columns (which allow nulls) to replicated tables. I've switched on verbose logging and I get the following: 2007/04/27 13:57:06 Hr=00000000 Compression Level set to 1 2007/04/27 13:57:06 Hr=00000000 Count of active RSCBs = 0 2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 Total Compressed bytes in = 846 2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 Total Uncompressed bytes in = 1442 2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 Responding to OpenWrite, total bytes = 846 2007/04/27 13:57:06 Thread=B04 RSCB=15 Command=OPWC Hr=00000000 C:Program FilesMicrosoft SQL Server 2005 Mobile Editionserverctmobilesql30.7AABD0FB7460_010309C7-9030-4CF9-7D60-A64608CD62F7 0 2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SYNC Hr=00000000 Synchronize prepped 0 <PARAMS RSCB="15" HostName="" Publisher="WINSERVER" PublisherNetwork="" PublisherAddress="" PublisherSecurityMode="1" PublisherLogin="" PublisherDatabase="CompacTimesheet_Staging" Publication="CompacTimesheet_Staging" ProfileName="DEFAULT" SubscriberServer="CTimeMobile - 7aabd0fb7460" SubscriberDatabasePath="Program FilesCompac TimesheetDataCompacTimesheetMobile.sdf" Distributor="WINSERVER" DistributorNetwork="" DistributorAddress="" DistributorSecurityMode="1" DistributorLogin="" ExchangeType="3" ValidationType="0" QueryTimeout="300" LoginTimeout="15" SnapshotTransferType="0" DistributorSessionId="452"/> 2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SYNC Hr=80045019 The merge process could not enumerate changes at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. -2147200999 2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SYNC Hr=80045645 The process was successfully stopped. -2147199419 2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SCHK Hr=80004005 SyncCheck responding 0 2007/04/27 13:57:06 Thread=E54 RSCB=15 Command=SCHK Hr=00000000 Removing this RSCB 0 The error message doesn't seem very helpful. Is there another way to find out what is causing the problem? I've tried reinitializing all subscriptions and generating a new snapshot but it makes no difference. The only way I've found to fix this is to delete the database on the subscriber and synchronise again (losing all subscriber data since the last sync). Regards, Greg
View Replies !
The Merge Process Could Not Enumerate Changes At The 'Subscriber'.
I have two SQL 2005 Standard servers using merge replication, and out of the blue started getting failure notices regarding "The merge process could not enumerate changes at the 'Subscriber'." I turned on verbose logging and noticed the following section: 2006-04-19 12:53:33.227 Category:NULL Source: Merge Replication Provider Number: -2147200999 Message: The merge process could not enumerate changes at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write. 2006-04-19 12:53:33.227 The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent. 2006-04-19 12:53:33.227 The merge process was unable to update last synchronization information at the Publisher. Using Profiler on both sides, I don't see anything out the ordinary during the replication process until there are two calls in a row to the stored procedure sp_MSadd_merge_history90, where the second one is storing the error message listed above. Any ideas? Thanks, Scott Davis
View Replies !
Finding Valid Identity Range On Merge Subscriber
I am using merge replication with automatic identity range management I want to be able to give a disconnected subscriber a warning message if a certain percentage of the allocated subscriber identity range has been used - so that they can make sure they reconnect soon to obtain a new identity range I can get the current identity value OK, but I can't find a good way of finding the current permitted primary and secondary ranges The information is available in the check constraint, but I don't really want to have to parse this! CONSTRAINT [repl_identity_range_0DF907AC_40CF_4849_9BD0_2173C90A3805] CHECK NOT FOR REPLICATION (([ContactID]>(10000040000.) AND [ContactID]<=(10000050000.) OR [ContactID]>(10000050000.) AND [ContactID]<=(10000060000.))) I can't find any system view which will provide this information Is there a recommended way of doing this? Thanks aero1
View Replies !
Subscriber Orphan Records
Dear all, I am trying to replace our in-house replication system with sql server 2005 replication, however I have encountered the following issue. Our client lists are to be filtered by state in the publication and then calls etc are joined to the client table based on the clientid. I cannot use the logical record option in these joins as I am using web synchronization and logical records are incompatible with this. When I initialise the subscription it creates a perfectly valid database, however if I was to change the state for a client, it removes him from the subscriber database, but leaves the orphaned call records. If I then edit the call records on the publisher it changes them and sends the change out to the subscriber blissfully unaware it has an orphan record. I do have referential integrity on the suscriber database, however I have had to mark it not for replication in order to allow the replication to work. I assume this problem is happening because I do not have the logical record box ticked, but as previously stated I cannot use this option. Is there another way around this? Thanks in advance David
View Replies !
Merge Replication Error - The Merge Process Could Not Retrieve Column Information
I had merge up and running fine. All of the sudden, the agent took a dive. This is what I get from the agent log. Any help would be greatly appreciated. Thanks in advance. [10/12/2006 9:00:18 AM]VBSERVE19.LTS_Efile: {call sp_MSgetversion } Percent Complete: 3 Retrieving publication information Percent Complete: 4 Retrieving subscription information Percent Complete: 4 The merge process is cleaning up meta data in database 'LTS_Efile'. Percent Complete: 4 The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in MSmerge_contents, and 0 row(s) in MSmerge_tombstone. Percent Complete: 4 The merge process is cleaning up meta data in database 'LTS_Efile'. Percent Complete: 4 The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in MSmerge_contents, and 0 row(s) in MSmerge_tombstone. Percent Complete: 4 Uploading data changes to the Publisher Connecting to Subscriber 'FO-DB-003.LTS_Efile' Server: FO-DB-003 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:23 AM]FO-DB-003.LTS_Efile: {call sp_MSgetversion } Connecting to Publisher 'VBSERVE19.LTS_Efile' Server: VBSERVE19 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:24 AM]VBSERVE19.LTS_Efile: {call sp_MSgetversion } Connecting to Subscriber 'FO-DB-003.LTS_Efile' Server: FO-DB-003 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:24 AM]FO-DB-003.LTS_Efile: {call sp_MSgetversion } Connecting to Publisher 'VBSERVE19.LTS_Efile' Server: VBSERVE19 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:24 AM]VBSERVE19.LTS_Efile: {call sp_MSgetversion } Connecting to Subscriber 'FO-DB-003.LTS_Efile' Server: FO-DB-003 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:24 AM]FO-DB-003.LTS_Efile: {call sp_MSgetversion } Connecting to Publisher 'VBSERVE19.LTS_Efile' Server: VBSERVE19 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:25 AM]VBSERVE19.LTS_Efile: {call sp_MSgetversion } Connecting to Subscriber 'FO-DB-003.LTS_Efile' Server: FO-DB-003 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:25 AM]FO-DB-003.LTS_Efile: {call sp_MSgetversion } Connecting to Publisher 'VBSERVE19.LTS_Efile' Server: VBSERVE19 DBMS: Microsoft SQL Server Version: 08.00.2039 user name: dbo API conformance: 2 SQL conformance: 1 transaction capable: 2 read only: N identifier quote char: " non_nullable_columns: 1 owner usage: 31 max table name len: 128 max column name len: 128 need long data len: Y max columns in table: 1024 max columns in index: 16 max char literal len: 524288 max statement len: 524288 max row size: 524288 [10/12/2006 9:00:30 AM]VBSERVE19.LTS_Efile: {call sp_MSgetversion } The process could not enumerate changes at the 'Subscriber'. The process could not enumerate deletions at the 'Subscriber'. The process could not enumerate changes at the 'Subscriber'. The merge process could not retrieve column information for table 'dbo.cmsReturn'. The process could not deliver delete(s) at the 'Publisher'. The process could not deliver delete(s) at the 'Publisher'. The process could not deliver delete(s) at the 'Publisher'. Percent Complete: 0 The process could not enumerate changes at the 'Subscriber'. Percent Complete: 0 Category:NULL Source: Merge Replication Provider Number: -2147200999 Message: The process could not enumerate changes at the 'Subscriber'. Percent Complete: 0 Category:COMMAND Source: Failed Command Number: 0 Message: {call sp_MSenumchanges(?,?,?,?,?,?,?,?)} Percent Complete: 0 Category:SQLSERVER Source: FO-DB-003 Number: 208 Message: Invalid object name 't'. Percent Complete: 0 Category:NULL Source: Merge Replication Provider Number: -2147200988 Message: The process was successfully stopped. Disconnecting from Subscriber 'FO-DB-003' Disconnecting from Publisher 'VBSERVE19' Disconnecting from Subscriber 'FO-DB-003' Disconnecting from Subscriber 'FO-DB-003' Disconnecting from Subscriber 'FO-DB-003' Disconnecting from Subscriber 'FO-DB-003' Disconnecting from Publisher 'VBSERVE19' Disconnecting from Publisher 'VBSERVE19' Disconnecting from Publisher 'VBSERVE19' Disconnecting from Publisher 'VBSERVE19' Disconnecting from Publisher 'VBSERVE19' Disconnecting from Distributor 'VBSERVE19'
View Replies !
Performance Issue Of Adding A New Subscriber
I Have a replication, that has a publication and a few pull-subscriptions. The replication passes a data to subscribers. New data or update of existed data on a publication database are happen often. Each time a one subscription pulls from the publisher, it gets a new data or updates. All pull occurs every 2 minutes. I need to add a new subscription. Usually a synchronization of new subscription takes 1.5 hour. I see that a synchronization of a new subscription reduces performance of existed subscriptions. 1.How can I monitor influence of synchronization on existed subscriptions? 2.If I use alternate snapshot location, does it reduce an influence of a synchronization on existed subscribers? 3. Does a subscription, that was configured to use snapshot from alternative location, use it always? Can I configure that a subscription does first synchronization from alternative snapshot location and all followed synchronization from default place?
View Replies !
Issue: Sql2k As Subscriber, Sq2005 As Publisher
Hi Everyone, I plan to do transactional replication. The publisher/distributor is sql2005 and subscriber is sql 2000. Is that possible. Because When I setup subscriber, I keep getting "The directory service is currently unavailable" in finding sql server replications. Thank you in advance
View Replies !
Large MSMerge_History, MSMerge_genhistory,MSRepl_errors Tables In SQL Server 2005 Express Edition (Merge Push Subscriber)
SQL Server 2005 Standard Edition act as publisher and distributor. All subscribers are SQL Server 2005 Express Edition. According to 2005 book online, "MSMerge_History table exists in distribution database". Howevey I found this table in Subscriber database which is in SQL Server 2005 Express Edition. The problem is this table (MSMerge_History) and other two tables (MSMerge_genhistory, MSRepl_errors) are quite large. We want to keep SQL Server 2005 Express database as small as possible so we can put more data into it. Is there anyway (Manually or automatically) to clean those tables in SQL Server 2005 Express? Please help.
View Replies !
Replication Insert From Subscriber
:confused: I want to call a stored procedure to do the insert into my published arcticle/table. Is this possible? I know you can call a stored procedure to insert into the subscriber arctiles. The problem is the published database has a generated primary key (max +1 )that is calculated via a stored procedure during all inserts. I would bring the stored procedure over to the subscriber but that would not help since the values in the target table will not be 'current' because the subscriber database is only updated nightly. Thoughts?
View Replies !
Replication: Cannot Enumerate Changes At Subscriber
Hi all! I hope anyone here can help me with this tough problem: I have a replication enviroment with several subscribers. Publisher:MSSQL 2000, SP3 Subscribers: MSSQL200, SP3 and MSDE2000, SP3 Since a few weeks, one of the subscribers fails when synchronizing with the message "This process could not enumerate changes at the subscriber" The erroroutput with verboselevel 3 doesn't help me much, I append it to the end of this posting. (unfortunately german) I heard that this error can be caused by a "blank" in an image column or different Service Pack Versions - definitely not possible in this case! The only strange detail is that the SQL Server Versionnumber of this MSDE shown via EM is not the same as the number shown in controlpanel->software. By the way, is it ok that here are two lines for the MSDE? SP3 is definitely installed on all machines! Any help would be greatly appreciated - i'm already losing hope... Best Regards, Gert Microsoft SQL Server-Merge-Agent 7.00.623 Copyright (c) 1998 Microsoft Corporation Percent Complete: 0 Verbindung mit Abonnent 'MyServerAT074' Connecting to Abonnent 'MyServerAT074.MyDB' MyServerAT074.MyDB: {call sp_MSgetversion } Percent Complete: 0 Verbindung mit Verteiler 'MyServer1s' Connecting to Verteiler 'MyServer1s.' MyServer1s.: {call sp_MSgetversion } MyServer1s.: {call sp_helpdistpublisher (N'MyServer1s') } MyServer1s.distribution: select datasource, srvid from master..sysservers where srvname = N'MyServer1s' MyServer1s.distribution: select datasource, srvid from master..sysservers where srvname = N'MyServerAT074' MyServer1s.distribution: {call sp_MShelp_merge_agentid (0, N'MyDB', N'MyDB', 9, N'MyDB')} Percent Complete: 0 Initialisiert MyServer1s.distribution: {call sp_MShelp_profile (19, 4, N'')} Percent Complete: 1 Verbindung mit Verleger 'MyServer1s' Connecting to Verleger 'MyServer1s.MyDB' Connecting to Verleger 'MyServer1s.MyDB' MyServer1s.MyDB: {call sp_MSgetversion } Percent Complete: 3 Ruft Publikationsinformationen ab Percent Complete: 4 Ruft Abonnementinformationen ab Connecting to Abonnent 'MyServerAT074.MyDB' Disconnecting from Abonnent 'MyServerAT074' Percent Complete: 4 Uploadet Datenänderungen zum Verleger Percent Complete: 5 Ruft die Liste der Löschungen von MyServer1s.MyDB ab Percent Complete: 5 Verarbeitet Artikel 'First' ...... SNIP .... Percent Complete: 5 Verarbeitet Artikel 'LastTable' Percent Complete: 0 Der Prozess konnte die Änderungen auf dem Abonnenten nicht aufzählen. Percent Complete: 0 Category:SQLSERVER Source: MyServerAT074 Number: 0 Message: Attributverletzung eingeschränkter Datentypen Attributverletzung eingeschränkter Datentypen Disconnecting from Abonnent 'MyServerAT074' Disconnecting from Verleger 'MyServer1s' Disconnecting from Verleger 'MyServer1s' Disconnecting from Verteiler 'MyServer1s'
View Replies !
Replication SQL 7/ Adding A New Subscriber
Hello, I'm working with a fine running Replication System. Today i want to add a new subscriber to a publication. (Enterprise Manager) The following Error occurs: When Iuse SQL Query Analyzer manualy , to run the sp_addsubscriber, the following Error occurs: 7411 Server 'repl_distributor' is not configured for RPC. Server: Nachr.-Nr. 7411, Schweregrad 16, Status 1, Prozedur sp_addsubscriber, Zeile 140 Server 'repl_distributor' is not configured for RPC. What can I do ? R.Lenz
View Replies !
Replication; What Is: SqlCeReplication.Subscriber?
I am tring to use SQL Server Mobile 2005 to subscribe to a SQL Server 2005 publication from a pocketPC. In my code I have a SqlCeReplication object. One of the properties that must be set is: Subscriber, but I have no idea what that should be set to. When I was setting up the publication I don't remember specifying anything like that, and the class description of this property doesn't help: "Specifies the name of the Subscriber". Any help will be appreciated.
View Replies !
Replication - Multiple Distributors, One Subscriber
I am planning a replication project where we will be rolling up datafrom several (about 5) offices into a central database that will beused for management reporting. The tables I want to replicate areidentical in each of the offices (there are 8 tables right now).Ideally I would like the final product to be 8 tables in the Subscriberdatabase, each table containing data from the 5 offices.Since I am new to replication, I was wondering if it is possible foreach of the 5 offices to sychronize with the 8 tables in the Subscriberdatabase? Or is it necessary to have a separate set of 8 tables foreach office? If that is the case, then I would have to UNION thetables in the Subscriber database, which I would rather not do if Idon't have to.
View Replies !
SQL Server Replication And The Growth Of The Subscriber Log
Working with SQL Servers' transactional replication I am having aproblem with the subscribers log growing to the size of the fulldatabase that I am replicating. Currently I have a 53 gig databasethat I have setup as my publisher. My distributor is on another serverwith the subscriber. I am also using the "sync with backup" DB option.I have log jobs running every five minutes on the publisher and thedistributor.My snapshot agent is setup with the following profile option:BCPBatchSize = 100000, HistoryVerboserLevel = 2, LoginTimeout = 15,MaxBCPThreads = 30, QueryTimeout = 300.My Distribution Agent has the following profile options: BCPBatchSize= 100000, CommitBatchSize = 100, CommitBatchThreshold = 1000,HistoryVerboseLevel = 1, KeepAliveMessage Interval = 300, LoginTimeout= 15, MaxBCPThreads = 30, MaxDeliveredTransactions = 0, QueryTimeout =300, TransactionsPerHistory = 100Lastly I have the recovery model for the subscriber database set toSimple.As the snapshot is delivered to the subscriber the log file grows tothe same size as the database. Is this normal? I would think thatsince I am BCPing the data into the database that the log would stayat a manageable size. Does anyone have a suggestion?Thank you in advance for any suggestions submitted.
View Replies !
Bi Directional Transactional Replication And Subscriber Name
Hi, I am trying to setup bi-directional transactional replication between 2 SQL Servers, I add the subscription on both the servers using the code below. EXEC sp_addsubscription @publication = N'test', @article = N'all', @subscriber = 'AnyServer', @destination_db = N'test', @sync_type = N'none', @status = N'active', @update_mode = N'read only', @loopback_detection = 'true' GO I have defined 'AnyServer' on both the servers using cliconfg (Server1's AnyServer pointed towards Server2 and Server2's AnyServer pointed towards Server1, I need to do that because there is a restriction to run the same code on both the servers), After inserting a record on server1 in the 'test' database, the changes successfully transfers to the server2, then server2 sends it back to server1 and server1 generates the error of "Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key in object 'Table1'." It seems as if loop detection is failing if I keep the same subscriber name on both sides. It runs fine when I change the subscriber name in the subscription (@subscriber = 'Server2' for server1 and @subscriber = 'Server1' for server2). Can anybody explains this behavior to me?
View Replies !
Bi Directional Transactional Replication And Subscriber Name
Hi, I am trying to setup bi-directional transactional replication between 2 SQL Servers, I add the subscription on both the servers using the code below. EXEC sp_addsubscription @publication = N'test', @article = N'all', @subscriber = 'AnyServer', @destination_db = N'test', @sync_type = N'none', @status = N'active', @update_mode = N'read only', @loopback_detection = 'true' GO I have defined 'AnyServer' on both the servers using cliconfg (Server1's AnyServer pointed towards Server2 and Server2's AnyServer pointed towards Server1, I need to do that because there is a restriction to run the same code on both the servers), After inserting a record on server1 in the 'test' database, the changes successfully transfers to the server2, then server2 sends it back to server1 and server1 generates the error of "Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key in object 'Table1'." It seems as if loop detection is failing if I keep the same subscriber name on both sides. It runs fine when I change the subscriber name in the subscription (@subscriber = 'Server2' for server1 and @subscriber = 'Server1' for server2). Can anybody explains this behavior to me?
View Replies !
|
TRACKER
