MERGE REPLICATION - HIGH VOLUME OF CHANGES

Hi everybody, i wanna ask you if somebody can tell me some recomendations when you have setted a merge replication environment and you have to replicate millions of records to some suscribers.

Hi carlosadrr,
According to your description, you have setted a merge replication environment and have to replicate millions of records to some subscribers.
Based on my research, one key parameter to consider when performing batch updates against tables enabled for Merge Replication is 'generation_leveling_threshold'.  This setting controls how many data changes should be grouped into one generations (or batch).
So to improve the Merge synchronization performance:
1) Increase the BATCH size of the generation.  For 10 million changes, try with setting at 10,000.
EXEC sp_changemergepublication
@publication='<publication name>',
@property= 'generation_leveling_threshold',
@value= '10000'
2) Execute sp_MSmakegeneration to call the generation leveling process.
For more information about how to Reducing Impact of Large Updates on Merge Replication, please refer to the following article:
http://blogs.msdn.com/b/repltalk/archive/2011/04/24/reducing-impact-of-large-updates-on-merge-replication.aspx
If you have any question, please feel free to let me know.
Regards,
Jerry Li

Similar Messages

  • I have just purchased my Iphone 4s, and the volume of the sound is very low, I can hardly hear the other person. I have tried the button for higher volume, but there is no change

    I have just purcahsed my Iphone 4s, and the volume is very low, I can hardly hear the other person talk. I have tried the botton for higher volume, but it doesn`t work. Can anybody give me an answer to what is wrong?

    Did u take out the screen protection?

  • Slow merge replication over a WAN link - only downloads

    Hi all,
    We've been using SQL Server merge replication for a few years to synchronise data between our data centres, but we are now suffering with a big performance issue. This may be because the amount of data we are synchronising has increased a lot this year.
    Our publisher is an always-on data centre in the UK. Our subscriber is a mobile data centre that travels around the world and is on for periods of up to a week at a time, approx. 25 times a year. However, it also spends the same amount of time (if not more)
    switched off whilst on its travels - it is a well travelled data centre!
    We have 5 database that we synchronise on these servers. However, one of our databases has high numbers of data changes between periods of subscriber downtime and our issue is that it take days to catch up when the server is powered up - the other databases
    are fine.
    Downloads from publisher to subscriber run at about 1.5 rows a second (which is annoying when we have hundreds of thousands of rows) but strangely uploads from subscriber to publisher run about ten times faster.
    Things I have checked / tried:
    all tables have non-clustered primary keys on guid columns that have the rowguid property set
    changing the generation levelling threshold doesn't help
    setting the agent profile to high volume doesn't help
    running a trace at the publisher and subscriber shows the queries are all running very fast (less than 20 m/s generally, but there are gaps of 200 m/s or so between some batches of queries)
    analysis on our WAN link shows we have huge amounts of bandwidth spare
    analysis on our servers show we have huge amounts of Ram and CPU spare
    Some of the places the subscriber is at do suffer from high latency but this doesn't seem to have an impact - 300 m/s or 100m/s and we still get the same poor performance.
    One things I did wonder about - does the replication confirm to the publisher every time it has successfully processed a row at the subscriber? If we have thousands of rows and there is a latency on the line will this compound the issue if it confirms each
    item? If this does happen, is there a way to batch up messages between publisher and subscriber?
    Any help that you can offer will be gladly received!
    Thanks
    Mark

    1) merge replication processes the uploads/downloads in batches. So no, there is no confirmation for each row processes, but there is per batch. If there is an error/conflict a batch is retried as singletons (a single row processed at a time), so you need
    to minimize conflicts/errors.
    2) No, but you should use pull and wan accelerators for max performance and change your profile to use 2000 for the following:
    MaxDownloadChanges 
    MaxUploadChanges
    UploadGenerationsPerBatch  
    DownloadGenerationsPerBatch 
    UploadReadChangesPerBatch 
    DownloadReadChangesPerBatch 
    UploadWriteChangesPerBatch 
    DownloadWriteChangesPerBatch 
    set network packet size to a large value - you will need to work with your wan engineer to find out what works best. 32k will likely be best.
    Also you may want to copy a file of a known size from your publisher to your subscriber and then from your subscriber to your publisher to see if there is a significant difference in time. For drives will yield significant differences.
    I have found that you may have a trigger which is generating a large volume of unnessary changes. You will need to see what table/article is generating all the changes and evaluate whether the changes are legit.
    Precomputed partitions should speed up the enumeration times. Ensure you have supporting indexes - the missing indexes DMV helps here.
    Lastly you may find that a reinitialization is faster than processing the changes.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • High volume Printing for GLM?

    I understand from various sources GLM can support high volume label output provided the correct enhancements and support packs are installed and configured.  This may include updates to WWI.  We are currently running ECC6 EHP5, SAP_BASIS 10, EHSM 3, WWI 2.7
    I would like to get this communities inputs.  Our requirement is to generate >2000 identical labels via GLM.  WWI processing today is long (5+min) and the output is large.  Ideally system would generate 1 label with indication to print 2000 times.  Our labels include barcodes and symbols and can be complex.

    Dear Richard,
    The functions of GLM is well explained as Christopher said and using GLM, you can print labels more than 10000 witha  sequential data output. To support such large quanitity of data to be printed on labels, you may need a special printers like the Zebra High volume printer. The WWI server is equipped to print large volume of labels using specific printer plugins.
    High volume printers can be used to print print requests with print files that are too large or that contain more than 32,768 labels to be printed. The HVP is designed as a printer driver for Microsoft Windows and is connected to the label printer via a plug-in.
    With the HVP, only one page with all static data is sent to the printer. The HVP then receives all of the sequential data via an interface and automatically supplements the sequential data in the printout. The HVP also integrates changing bar codes or texts in the printout.
    The Zebra 170Xi4 is one of most popular, industrial-strength printers on the market. This rugged metal unit prints 1-color labels up to 6.6" wide, with 300 dpi print resolution in thermal or thermal transfer mode. Its extra processing power equates to speeds up to 12 inches-per-second. This one is perfect for tough applications including compliance labels, product labels, and shipping labels.
    For further information, please check the links below
    EHS - Continuous Improvement for Global Label Management - Logistics - SAP Library
    OSS notes in Global Label management
    New changes for GLM in EHP7.0 and ERP 6.0
    Dhinesh

  • Merge Replication Error When Initialising subscription

    I have a SQL server 2005 server with a merge publication of 6 articles all of which are tables which is also the distributor. I have two existing subscriptions one from a SQL 2005
    Server and one from a SQL Server 2008 R2 Server both of which are working fine on this publication. I am trying to setup a third subscription to another SQL Server 2008 R2 server, the only difference with this server is that it is a named instance. I have
    forced the port to 1433, and created an alias on the publisher connectivity is not an issue or at least i don't think so.
    when I try to initialise the subscription from a new snapshot I get the below error;
    Error: 14151, Severity: 18, State: 1.
    Replication-Replication Merge Subsystem: agent failed. No subscription is on this publication or article.
    I've changed the agent profile and turned on verbose logging and output the results to a file the snapshot delivery is failing on the below for the first table;
    call sys.sp_MSsetup_identity_range (?,?,?,?,?,?,?,?)
    I've checked the subscriber and the table does indeed get dropped and created, permissions / routes don't seem to be an issue. I've included some of the verbose logging output below.
    2012-01-11 12:05:40.684 Microsoft SQL Server Merge Agent 9.00.3042.00
    2012-01-11 12:05:40.700 Copyright (c) 2005 Microsoft Corporation
    2012-01-11 12:05:40.716 Microsoft SQL Server Replication Agent: replmerg
    2012-01-11 12:05:40.716 
    2012-01-11 12:05:40.731 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2012-01-11 12:05:40.747 User-specified agent parameter values:
    -Publisher PubServerName
    -PublisherDB UserDBName
    -Publication MtoC_M
    -Subscriber SubServerName
    -SubscriberDB UserDBName
    -Distributor PubServerName
    -DistributorSecurityMode 1
    -Continuous
    -OutputVerboseLevel 4
    -Output G:\CMcReplicationLogging\OUTPUT.TXT
    -XJOBID 0x5FFBC73C3A4A494A9E10C369696B1C72
    -XJOBNAME PubServerName-UserDBName-MtoC_M-SubServerName-29
    -XSTEPID 2
    -XSUBSYSTEM Merge
    -XSERVER PubServerName
    -XCMDLINE 0
    -XCancelEventHandle 000008EC
    -XParentProcessHandle 00000E9C
    2012-01-11 12:05:40.841 Percent Complete: 0
    2012-01-11 12:05:40.841 Connecting to Distributor 'PubServerName'
    2012-01-11 12:05:40.856 Repl Agent Status: 3
    2012-01-11 12:05:40.856 Connecting to OLE DB Distributor at datasource: 'PubServerName', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:42.137 OLE DB Distributor: PubServerName
    DBMS: Microsoft SQL Server
    Version: 09.00.3042
    catalog name: 
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:42.137 OLE DB Distributor 'PubServerName': {call sp_MSgetversion }
    2012-01-11 12:05:42.153 OLE DB Distributor 'PubServerName': {call sp_helpdistpublisher (N'PubServerName') }
    2012-01-11 12:05:42.169 OLE DB Distributor 'PubServerName': {call sp_MShelp_repl_agent (N'PubServerName', N'UserDBName', N'MtoC_M', N'SubServerName', N'UserDBName', 1)}
    2012-01-11 12:05:42.169 OLE DB Distributor 'PubServerName': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'PubServerName')
    2012-01-11 12:05:42.184 OLE DB Distributor 'PubServerName': {call sp_MShelp_merge_agentid (0,N'UserDBName',N'MtoC_M',null,N'UserDBName',90,N'SubServerName')}
    2012-01-11 12:05:42.184 OLE DB Distributor 'PubServerName': {call sp_MShelp_profile (29, 4, N'')}
    2012-01-11 12:05:42.184 Percent Complete: 0
    2012-01-11 12:05:42.184 Connecting to OLE DB Publisher at datasource: 'PubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:42.200 Initializing
    2012-01-11 12:05:42.200 Repl Agent Status: 1
    2012-01-11 12:05:42.216 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:42.216 Percent Complete: 0
    2012-01-11 12:05:42.231 Connecting to Publisher 'PubServerName'
    2012-01-11 12:05:42.231 Repl Agent Status: 3
    2012-01-11 12:05:42.231 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:43.153 OLE DB Publisher: PubServerName
    DBMS: Microsoft SQL Server
    Version: 09.00.3042
    catalog name: UserDBName
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:43.169 OLE DB Publisher 'PubServerName': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2012-01-11 12:05:43.169 OLE DB Publisher 'PubServerName': {call sp_MSgetversion }
    2012-01-11 12:05:43.200 Connecting to OLE DB Publisher at datasource: 'PubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:44.137 OLE DB Publisher: PubServerName
    DBMS: Microsoft SQL Server
    Version: 09.00.3042
    catalog name: UserDBName
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:44.137 OLE DB Publisher 'PubServerName': {call sp_MSchecksnapshotstatus (N'MtoC_M')}
    2012-01-11 12:05:44.153 OLE DB Publisher 'PubServerName': {call sp_helpmergepublication (N'MtoC_M')}
    2012-01-11 12:05:44.153 OLE DB Publisher 'PubServerName': {call sys.sp_MSgetreplicainfo(?,?,?,?,?,?,?,90)}
    2012-01-11 12:05:44.169 OLE DB Distributor 'PubServerName': {call sp_MShelp_repl_agent (N'PubServerName', N'UserDBName', N'MtoC_M', N'SubServerName', N'UserDBName', 1)}
    2012-01-11 12:05:44.169 Connecting to OLE DB Subscriber at datasource: 'SubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:44.747 OLE DB Subscriber: SubServerName
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: UserDBName
    user name: distributor_MtoC
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:45.122 OLE DB Subscriber 'SubServerName': {call sp_MSgetversion }
    2012-01-11 12:05:45.216 OLE DB Subscriber 'SubServerName': {call sp_MSreplcheck_subscribe}
    2012-01-11 12:05:45.309 OLE DB Subscriber 'SubServerName': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2012-01-11 12:05:45.419 Percent Complete: 0
    2012-01-11 12:05:45.419 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.419 Connecting to Subscriber 'SubServerName'
    2012-01-11 12:05:45.434 Repl Agent Status: 3
    2012-01-11 12:05:45.434 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.559 Percent Complete: 0
    2012-01-11 12:05:45.559 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.559 Retrieving publication information
    2012-01-11 12:05:45.575 Repl Agent Status: 3
    2012-01-11 12:05:45.575 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.653 OLE DB Subscriber 'SubServerName': {call sys.sp_MSmerge_upgrade_subscriber(1,?)}
    2012-01-11 12:05:45.653 Percent Complete: 0
    2012-01-11 12:05:45.669 Retrieving subscription information.
    2012-01-11 12:05:45.669 Repl Agent Status: 3
    2012-01-11 12:05:45.684 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.763 OLE DB Publisher 'PubServerName': {call sys.sp_MSgetreplicainfo(?,?,?,?,?,?,?,90)}
    2012-01-11 12:05:45.763 OLE DB Publisher 'PubServerName': {call sys.sp_MShelpmergearticles (?,9000000,?) }
    2012-01-11 12:05:45.778 OLE DB Publisher 'PubServerName': {call sp_MSenumschemachange (?,?,9000000,?,0,1) }
    2012-01-11 12:05:45.794 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.888 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.888 Percent Complete: 0
    2012-01-11 12:05:45.903 Applying the snapshot to the Subscriber
    2012-01-11 12:05:45.903 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.903 Repl Agent Status: 3
    2012-01-11 12:05:45.919 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.919 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.919 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.934 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.950 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.950 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.966 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.981 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.997 OLE DB Publisher 'PubServerName': {call sys.sp_MSallocate_new_identity_range (?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:45.997 OLE DB Subscriber 'SubServerName': {call master..sp_helpreplicationoption ('merge')}
    2012-01-11 12:05:46.091 OLE DB Subscriber 'SubServerName': {call sys.sp_MSmergesubscribedb ('true', 0) }
    2012-01-11 12:05:47.263 OLE DB Subscriber 'SubServerName': {call sp_MSpublicationcleanup (?,?,?)}
    2012-01-11 12:05:47.372 OLE DB Subscriber 'SubServerName': {call sp_MSCleanupForPullReinit (?,?,?)}
    2012-01-11 12:05:47.481 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblEmailMessages',N'dbo')}
    2012-01-11 12:05:47.606 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblUser',N'dbo')}
    2012-01-11 12:05:47.716 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblDPVLocked',N'dbo')}
    2012-01-11 12:05:47.809 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblCaptureAppToken',N'dbo')}
    2012-01-11 12:05:47.903 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblCreditThresholdNotification',N'dbo')}
    2012-01-11 12:05:48.013 OLE DB Subscriber 'SubServerName': {call sp_MSdropconstraints (N'tblCreditPot',N'dbo')}
    2012-01-11 12:05:48.106 OLE DB Subscriber 'SubServerName': {call sys.sp_MSaddinitialpublication (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:48.247 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblEmailMessages',?, 1, ?, ?)}
    2012-01-11 12:05:48.403 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblUser',?, 1, ?, ?)}
    2012-01-11 12:05:48.513 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblDPVLocked',?, 1, ?, ?)}
    2012-01-11 12:05:48.606 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblCaptureAppToken',?, 1, ?, ?)}
    2012-01-11 12:05:48.700 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblCreditThresholdNotification',?, 1, ?, ?)}
    2012-01-11 12:05:48.809 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkifneeded (N'tblCreditPot',?, 1, ?, ?)}
    2012-01-11 12:05:48.903 OLE DB Publisher 'PubServerName': {call sp_MShelpmergeschemaarticles(?)}
    2012-01-11 12:05:48.919 OLE DB Subscriber 'SubServerName': {call sp_MSaddinitialsubscription (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}
    2012-01-11 12:05:49.059 OLE DB Distributor 'PubServerName': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'PubServerName')
    2012-01-11 12:05:49.059 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_mergesubentry_indistdb (0,N'PubServerName',N'UserDBName',N'MtoC_M',N'SubServerName',N'UserDBName',0,1,0,N'',?,90)}
    2012-01-11 12:05:49.075 OLE DB Subscriber 'SubServerName': {call sp_MScreateglobalreplica (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,90)}
    2012-01-11 12:05:49.341 Connecting to OLE DB Subscriber at datasource: 'SubServerName', location: '', catalog: 'UserDBName', providerstring: '' using provider 'SQLNCLI'
    2012-01-11 12:05:49.825 OLE DB Subscriber: SubServerName
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: UserDBName
    user name: distributor_MtoC
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:50.185 OLE DB Subscriber: SubServerName
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: UserDBName
    user name: distributor_MtoC
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2012-01-11 12:05:50.325 OLE DB Subscriber 'SubServerName': {call sys.sp_MSregistermergesnappubid(?, ?)}
    2012-01-11 12:05:50.450 OLE DB Subscriber 'SubServerName': sp_MSacquiresnapshotdeliverysessionlock
    2012-01-11 12:05:50.544 OLE DB Subscriber 'SubServerName': sp_MStrypurgingoldsnapshotdeliveryprogress
    2012-01-11 12:05:50.810 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:50.966 [2%] OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    ꜻä㹒 ꜐äB 11 12:05ä谼砗꜐ä镴ĀPercent Complete: 4
    2012-01-11 12:05:50.997 Propagated 1 schema changes: 1 total
    2012-01-11 12:05:51.013 Repl Agent Status: 3
    2012-01-11 12:05:51.013 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:51.091 [6%] OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    ꜻä㹒 ꜐äB 11 12:05ä谼砗꜐ä镴ĀPercent Complete: 6
    2012-01-11 12:05:51.122 Propagated 1 schema changes: 2 total
    2012-01-11 12:05:51.153 Repl Agent Status: 3
    2012-01-11 12:05:51.153 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:51.200 OLE DB Subscriber 'SubServerName': {call sp_MSunmarkreplinfo (N'tblEmailMessages')}
    2012-01-11 12:05:51.200 [6%] Percent Complete: 6
    2012-01-11 12:05:51.231 Propagated 1 schema changes: 3 total
    2012-01-11 12:05:51.247 Repl Agent Status: 3
    2012-01-11 12:05:51.263 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:51.325 OLE DB Subscriber 'SubServerName': sp_MSissnapshotitemapplied @snapshot_session_token = N'E:\Microsoft SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\', @snapshot_progress_token = N'E:\Microsoft
    SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\tblEmailMessages_2.sch'
    2012-01-11 12:05:51.435 drop Table [dbo].[tblEmailMessages]
    go
    SET ANSI_PADDING ON
    go
    SET ANSI_NULLS ON
    GO
    SET QUOTED_IDENTIFIER ON
    GO
    CREATE TABLE [dbo].[tblEmailMessages](
    [EmailMessageId] [bigint] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
    [Guid] [nvarchar](32) NOT NULL,
    [Recipients] [varchar](8000) NOT NULL,
    [CcRecipients] [varchar](8000) NULL,
    [BccRecipients] [varchar](8000) NULL,
    [Sender] [varchar](8000) NOT NULL,
    [Subject] [nvarchar](4000) NOT NULL,
    [BodyText] [nvarchar](max) NULL,
    [BodyHTML] [nvarchar](max) NULL,
    [IsBodyEncrypted] [bit] NOT NULL CONSTRAINT [DF_tblEmailMessages_IsBodyEncrypted] DEFAULT ((0)),
    [Status] [tinyint] NOT NULL CONSTRAINT [DF_tblEmailMessages_Status] DEFAULT ((1)),
    [DateAdded] [datetime] NOT NULL CONSTRAINT [DR_tblEmailMessages_DateAdded] DEFAULT (getdate()),
    [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_207F75F229994684BC3FAAE5BE4CD6EB] DEFAULT (newsequentialid())
    GO
    GRANT DELETE ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    GRANT INSERT ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    GRANT SELECT ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    GRANT UPDATE ON [dbo].[tblEmailMessages] TO [odintermediary]
    GO
    SET ANSI_NULLS ON
    go
    SET QUOTED_IDENTIFIER ON
    go
    ALTER TABLE [dbo].[tblEmailMessages] ADD CONSTRAINT [PK_tblEmailMessage] PRIMARY KEY CLUSTERED 
    [EmailMessageId] ASC
    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
    GO
    2012-01-11 12:05:51.450 OLE DB Subscriber 'SubServerName': drop Table [dbo].[tblEmailMessages]
    2012-01-11 12:05:51.560 OLE DB Subscriber 'SubServerName': SET ANSI_PADDING ON
    2012-01-11 12:05:51.669 OLE DB Subscriber 'SubServerName': SET ANSI_NULLS ON
    2012-01-11 12:05:51.778 OLE DB Subscriber 'SubServerName': SET QUOTED_IDENTIFIER ON
    2012-01-11 12:05:51.872 OLE DB Subscriber 'SubServerName': CREATE TABLE [dbo].[tblEmailMessages](
    [EmailMessageId] [bigint] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
    [Guid] [nvarchar](32) NOT NULL,
    [Recipients] [varchar](8000) NOT NULL,
    [CcRecipients] [varchar](8000) NULL,
    [BccRecipients] [varchar](8000) NULL,
    [Sender] [varchar](8000) NOT NULL,
    [Subject] [nvarchar](4000) NOT NULL,
    [BodyText] [nvarchar](max) NULL,
    [BodyHTML] [nvarchar](max) NULL,
    [IsBodyEncrypted] [bit] NOT NULL CONSTRAINT [DF_tblEmailMessages_IsBodyEncrypted] DEFAULT ((0)),
    [Status] [tinyint] NOT NULL CONSTRAINT [DF_tblEmailMessages_Status] DEFAULT ((1)),
    [DateAdded] [datetime] NOT NULL CONSTRAINT [DR_tblEmailMessages_DateAdded] DEFAULT (getdate()),
    [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_207F75F229994684BC3FAAE5BE4CD6EB] DEFAULT (newsequentialid())
    2012-01-11 12:05:51.981 OLE DB Subscriber 'SubServerName': GRANT DELETE ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.091 OLE DB Subscriber 'SubServerName': GRANT INSERT ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.200 OLE DB Subscriber 'SubServerName': GRANT SELECT ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.294 OLE DB Subscriber 'SubServerName': GRANT UPDATE ON [dbo].[tblEmailMessages] TO [odintermediary]
    2012-01-11 12:05:52.403 OLE DB Subscriber 'SubServerName': SET ANSI_NULLS ON
    2012-01-11 12:05:52.497 OLE DB Subscriber 'SubServerName': SET QUOTED_IDENTIFIER ON
    2012-01-11 12:05:52.606 OLE DB Subscriber 'SubServerName': ALTER TABLE [dbo].[tblEmailMessages] ADD CONSTRAINT [PK_tblEmailMessage] PRIMARY KEY CLUSTERED 
    [EmailMessageId] ASC
    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON)
    2012-01-11 12:05:52.716 OLE DB Subscriber 'SubServerName': sp_MSrecordsnapshotdeliveryprogress @snapshot_session_token = N'E:\Microsoft SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\', @snapshot_progress_token = N'E:\Microsoft
    SQL Server\MSSQL.1\MSSQL\repldata\unc\PubServerName_UserDBName_MTOC_M\20120111115787\tblEmailMessages_2.sch'
    2012-01-11 12:05:52.841 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:52.966 [6%] Percent Complete: 6
    2012-01-11 12:05:52.981 Applied script 'tblEmailMessages_2.sch'
    2012-01-11 12:05:52.981 Repl Agent Status: 3
    2012-01-11 12:05:52.981 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.153 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.263 [6%] OLE DB Subscriber 'SubServerName': {call sys.sp_MSaddinitialarticle (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    ꜻä㹒 ꜐äB 11 12:05ä谼砗꜐ä镴ĀPercent Complete: 6
    2012-01-11 12:05:53.294 Preparing table 'tblEmailMessages' for merge replication
    2012-01-11 12:05:53.294 Repl Agent Status: 3
    2012-01-11 12:05:53.310 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.450 OLE DB Subscriber 'SubServerName': {call sp_MSupdatesysmergearticles (?,?,?,?,0)}
    2012-01-11 12:05:53.575 OLE DB Subscriber 'SubServerName': {call sys.sp_MSsetup_identity_range (?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.794 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.
    2012-01-11 12:05:53.825 OLE DB Subscriber 'SubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:53.966 Percent Complete: 6
    2012-01-11 12:05:53.966 No subscription is on this publication or article.
    2012-01-11 12:05:53.997 Repl Agent Status: 6
    2012-01-11 12:05:54.013 OLE DB Distributor 'PubServerName': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2012-01-11 12:05:54.216 Percent Complete: 0
    2012-01-11 12:05:54.231 Category:SQLSERVER
    Source: SubServerName
    Number: 14050
    Message: No subscription is on this publication or article.
    2012-01-11 12:05:54.247 Repl Agent Status: 3
    2012-01-11 12:05:54.372 Percent Complete: 0
    2012-01-11 12:05:54.372 Category:NULL
    Source: Merge Replication Provider
    Number: -2147201001
    Message: 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.
    2012-01-11 12:05:54.388 Repl Agent Status: 3
    2012-01-11 12:05:54.388 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.388 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.403 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.403 Disconnecting from OLE DB Subscriber 'SubServerName'
    2012-01-11 12:05:54.403 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.419 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.419 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.419 Disconnecting from OLE DB Publisher 'PubServerName'
    2012-01-11 12:05:54.435 Disconnecting from OLE DB Distributor 'PubServerName'
    2012-01-11 12:05:54.435 Disconnecting from OLE DB Distributor 'PubServerName'
    2012-01-11 12:05:54.450 The merge process will restart after waiting 30 second(s)...
    Percent Complete: 0
    Any help would be much appreciated.
    Thanks
    Chris 

    The error happens on this table every time.
    The schema of the table is below;
    CREATE TABLE [dbo].[tblEmailMessages](
    [EmailMessageId] [bigint] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL,
    [Guid] [nvarchar](32) NOT NULL,
    [Recipients] [varchar](8000) NOT NULL,
    [CcRecipients] [varchar](8000) NULL,
    [BccRecipients] [varchar](8000) NULL,
    [Sender] [varchar](8000) NOT NULL,
    [Subject] [nvarchar](4000) NOT NULL,
    [BodyText] [nvarchar](max) NULL,
    [BodyHTML] [nvarchar](max) NULL,
    [IsBodyEncrypted] [bit] NOT NULL CONSTRAINT [DF_tblEmailMessages_IsBodyEncrypted] DEFAULT ((0)),
    [Status] [tinyint] NOT NULL CONSTRAINT [DF_tblEmailMessages_Status] DEFAULT ((1)),
    [DateAdded] [datetime] NOT NULL CONSTRAINT [DR_tblEmailMessages_DateAdded] DEFAULT (getdate()),
    [rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_207F75F229994684BC3FAAE5BE4CD6EB] DEFAULT
    (newsequentialid())
    The table gets dropped and recreated each time i try to reinitialise the subscription.  I can't remove the article at the moment as two other servers subscribe to the publication.
    Thanks for your help
    Chris
    I am the master of my fate: I am the captain of my soul.

  • SQL Server Compact 3.5 Merge Replication With SQL Server 2012 - Causing IIS App Pool to Crash

    Hi, I may be the only person in the world doing this but I wanted to give this information to anyone else who may follow this path in the future, and hopefully avoid a headache, or at least a paid support call to Microsoft.
    My original scenario was we had a SQL Server 2008 Server using Merge Replication through and IIS (web server) to several Windows Mobile 6 devices.  This has worked fairly well for a few years.
    Recently we upgraded our SQL server to version 2012 SP 1.  After moving the database over to the new server, and re-setting the merge replication stuff, we couldn't get merge replication to work on the Windows Mobile 6 handheld devices.  The replication
    would appear to start, and then we would get a message saying that the device could not get to the web site.  The message on the handheld device was this:
    "The IIS service is not available."
    After doing some more research, we found that the start of the replication process was causing the Thread Pool that was running the SQLCESA35.dll to crash.  
    The SQLCESALOG.txt file had this information:
    Date Time == SQLCESA Version ==> 3.5.8088.0
    Date Time Hr=80004005 ERR:Couldn't find existing RSCB 1
    After 2 days of trying to figure out the issue on our own, we gave in and called for paid Microsoft support.  They eventually found a known issue where a cumulative update was able to fix the problem.
    We installed the update on the IIS server and everything ran smoothly again.
    FIX: Merge replication fails when you use SQL Server Compact to perform a merge replication that synchronizes changes with a publisher in SQL Server 2012
    http://support.microsoft.com/kb/2845550
    Seth O'Neal

    Hi sonealtx,
    Glad to hear that the issue is resolved. Thanks for your sharing, other community members could benefit from your solution.
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Snapshot agent showing red mark in replication monitor!!!(Merge replication)

    few days before snapshot agent showing red mark in replication monitor without any changes...
    synchronizing from publisher to subscribe working fine...
    and how to clean up snapshot agent job history...
    plz give me a solution...
    Thanks in advance.......

    error:
    The replication agent has not logged a progress message in 5 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor
    are still active.
    snapshot agent showing red mark...
    Hi Baraiya Kirit,
    According to the error message, the issue could be caused by that the agent is busy or the agent cannot log in to one of the computers in the topology.
    To troubleshoot this issue, please perform the following steps. For more details, please review this article:
    MSSQL_ENG020554.
    • If the agent has stopped, please restart it and check if the error still occurs.
    • If this error is raised frequently because the agent is busy:
    You might need to redesign your application so that the agent spends less time processing.
    You can increase the interval at which agent status is checked using the Job Properties dialog box.
    • If an agent cannot log in to one of the computers in the topology:
    We recommend that the -LoginTimeOut value be set lower than the interval at which the replication agent checkup job runs.
    There is also a similar blog for your reference.
    http://maginaumova.com/the-replication-agent-has-not-logged-a-progress-message-in-10-minutes/
    Thanks,
    Lydia Zhang

  • High volumes on receiver JDBC adapter

    Hi,
    We have a RFC ->JDBC scenario where the RFC pulls huge amounts of data from R/3 and sends to XI.
    XI needs to upload this data into 5 different Db tables.Each table contains 3000-8000 records with each record containing 10-15 fields.
    When we try to run this scenario, due to high volumes of data  the JBDC adapter hangs and msgs were in 'holding/delivering' status for long time.
    Please advice on possibilities of handling this within XI.

    Hi,
    We changed the design and now we have only 'INSERT' and we don't have concerns with table refresh now.
    I am splitting the records in XI mapping as bunches on 1000 each. But I found one of the tables have more that 1lakh records.
    The data volume that we received in RFC is 150000 records(45MB). It took 7.5 mins to process this msg in Integration Engine.
    But the messages delivery into Db tables (receiver JDBC adapter processing) is very slow.At maximum it can process 250 records in minute.
    Please provide your inputs on this design. Is it Ok to accept 45MB message into XI at one shot? Even though the message got processed(splitted) in IE, they are processing in AE for long time. I believe this will have impact on other interfaces that use JDBC adapter.
    Please provide your suggestions on how to improve the design/performance of this interface.
    Thanks!

  • SQL question in a high volume web app environment

    Hi,
    We have a high volume website used in a hospital setting. When a doc selects a patient, we have to delete all previous patient history records for the patient from a certain table and insert new records retrieved from a web svc called at runtime during patient selection.
    Our 2 options are:
    Option1:
    1. Call Web svc, and always insert the results into pt_history, even if this creates duplicates (which it normally shouldn’t, if we only call every 24 hours)
    2. Only pt claims_history records that are less than 24 hours old from app method calls
    3. Nightly batch job cleans out records older than 24 hours
    Option2:
    1. Delete all existing history recs for a patient each time before calling web svc
    2. Call web svc, and always insert the results into pt_history (no chance of duplicates here)
    3. No change to existing methods
    4. No nightly batch job
    I'm leaning to option 1 to avoid contention\locks\deadlocks on the table. Any other solutions out there?
    Also any insights into which may be a better option this being a high volume transaction (several 10s of calls every sec) and table could grow to be oretty large (2 million recs and more)
    Thanks,
    JGP

    1) Why do you need to "delete all previous patient history records"? That seems contrary to the point of having patient history records...
    We want to keep these records only for 24 hrs. Older than 24 hrs is not needed.
    2) If you are just using this table to cache results from the web service call, could you use a temporary table?
    We wan to cache across all sessions for 24 hrs. So temp table would not work.
    Thanks,
    JGP

  • SQL Server upgrade with merge replication

    We are planning to upgrade SQL Server 2005 to SQL Server 2012 and both the databases will be hosted on two different servers. SQL Server 2005 has around 25 merge publication and have around 400 laptops that subscribe to these publications. The new SQL server
    2012 will also have same replication setup as the old server. The data base size on the existing server is 66 GB and takes about 1.5 hrs for initial sync up.
    Due to various business constraints we can't move over to new server in a single switch. Instead we need to keep both the servers running for a month or two. During this process, we need to replicate (uni-directional) data from SQL server 2005 to SQL server
    2012 on a daily basis. To achieve this we have tried the following approaches so far:
    DB backup and restore from SQL 2005 to SQL 2012 server - In this approach, the publications are dropped by SQL 2012 after we restore.
    SQL native replication - Could not setup Transactional, Merge and Snapshot replication due SQL server constraints. Cannot setup merge replication between SQL 2005(publisher) and SQL 2012(subscriber)
    Microsoft Sync framework – Sync fwk expects identify column or primary key for the sync to work but database has 76 tables without any primary key
    SSIS – DB consists of 170 tables and will require significant effort to write and maintain the package to sync update and delete operations on the DB. Insert operations on the other hand are easy to support.
    We are looking for different options to setup server to server replication with given constraints. 

    You will need to use some form of change tracking to gather the changes up and replay them on the SQL 2012 server.
    You can hack into the msmerge_Contents and msmerge_tombstone to do this. It will be fairly laborious to set up, but it is doable. You can do this as a batch operation so you can run it nightly to do your syncs.
    A lower tech way of doing it would be to run tablediff between the two servers and then replay the script nightly.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • SQLSERVER Merge Replication Error: Command attempted: {call sp_MSreleasemakegenerationapplock}

    Dear Friends, I updated SQL SERVER 2k5 with SP4 and I am getting error while synchronizing merge replication.
    Here is the error in Replication Monitor:
    Command attempted:
    {call sp_MSreleasemakegenerationapplock}
    Error messages:
    The merge process was unable to create a new generation at the 'Subscriber'. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200994)
    Get help: http://help/MSSQL_REPL-2147200994
    Internal Query Processor Error: The query processor encountered an unexpected error during execution. (Source: MSSQLServer, Error number: 8630)
    Get help: http://help/8630
    I executed below statement in both Publisher and Subscriber, but didn't help.
    update sysmergepublications set [generation_leveling_threshold] = 0
    Some suggests that I should use SP2 Update Package, Though that is installed and I am using SP4 now.

    Hi arahmancsd,
    Hi arahmancsd,
    According to your error message, when you sync data in merge replication, check if you use a SELECT INTO query statement. If you run the same INTO query twice and separately or you perform an operation that causes SQL Server to recompile the second SELECT
    INTO query, they all return the error 8630 message.
    For more information, see:
    http://support.microsoft.com/kb/323586/en-us
    Since you have changed the generation_leveling_threshold to 0 in sysmergepublications table in publisher and in subscriber. Please do not update the system tables directly. You can follow the steps mentioned in workaround section of
    http://support.microsoft.com/kb/953568.
    Hope it can help you.
    Regards,
    Sofiya Li
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Volume Settings Change on Reset

    Volume Settings Change on ResetZ Randomly when I reset, the volume settings all 'max out' and refuse to change in the Creative Audio Console, despite what I do to change them. It is not shown in any menus, but you can hear that it is this way.
    This then leads to weird noises as all the volume is too high for the features to work right. The only way I can get around this is to manually change the volume on everything when I use it (obviously not going to do this) after each reset/power-on, or I have to set it to default and change the settings again (gets annoying fast).
    Anyone know why it would be doing this? It seems software related to me, rather than hardware.
    OS: Vista 64Message Edited by Kogen on 05-26-2009 04:30 PM

    I "feel your pain", having had this issue on average every 3 months or so. Sometimes it will spontaneously fix itself. I tried deleting the Home/Library/Mail/Mailboxes Outbox.mbox folder followed by closing and reopening Mail which worked for a very brief time only, then became an issue once more. I have 2 accounts in gmail.com which are the current outgoing server issues. One of them works and the other doesn't. Now when I create a new note there are 2 text boxes in the from area of the note all of a sudden.
    This is a real problem because if I send mail using the other server, my business accounts will not recognize the incorrect server now being used by Mail to send all my outgoing as the address is not the one associated with my accounts.

  • Oracle database integration with SAP PI for high volume & Complex Structure

    Hi
    We have requirement for integrating oracle database to SAP PI 7.0 for sending data which is eventually transferred to multiple receivers. The involved data structure is hugely complex (around 18 child tables) with high volume processing requirement (100K+ objects need to be processed in 6-7 hours). We need to implement logic for prioritizing the object i.e. high priority objects must be processed first and then objects with normal priority.
    We could think of implementing this kind of logic in database procedures (at least it provides flexibility for implementing data selection logic as well as processed data can be marked as success in the same SP) but since PI sender adapter doesn't support calling Oracle stored procedures currently so this option is rules out. we can try implementing complex data selection using oracle table function but table function doesn't allow any SQL query which changes data (UPDATE, INSERT, DELETE etc) so it is impossible to mark selected objects in table function from PI communication channel "Update Query" option.
    Also, we need to make sure that we are not processing all the objects at once as message size for 20 objects can vary from 100 KB to 15 MB which could really lead to serious performance issues for bigger messages.
    Please share any implementation experience for handling issues:
    1 - Database Integration involving Oracle at sender side
    2 - Complex Data structures
    3 - High Volume Processing
    4 - Controlled data selection from database to contro the message size in PI
    Thanks,
    Panchdev

    Hi,
          We can call the stored procedure using receiver adapter using ccBPM, we can follow different approaches for reading the data in this case.
    a) In this  a ccBPM instance needs to be triggered using some dummy message, after receiving this message the ccBPM can make  a sync call to the Oracle database the store procedure(this can be done using the specific receiver data type strucure), on getting the response message the ccBPM  can then proceed with the further steps.The stored procedure needs to be optimized for improving the performance as the mapping complexity will largely get affected by the structure in which the stored procedure returns the message.Prioritization of the objects can be handled in the stored procedure.
    b) In this a ccBPM instance can first read data from the header level table, then it can make subsequent sync calls to Oracle tables for reading data from the child tables.This approach is less suitable for this interface as the number child tables is big.
    Pravesh.

  • Merge replication is not happening in one way

    Hi ALl,
    We have merge replications setup. it is not working in one direction. I enabled the logging to output fine but no use i could not find anything. The pings are fine no drops. Telnet is working. no load on server. i contacted network teams there is no issues.
    What could be the issue?
    The merge process could not retrieve column information for table 'dbo.MAINT'. Verify that you have sufficient privileges on the database and retry the operation.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.
    But the agent subsystem account and replication has sysadmin permission no possibility of password issue.
    Snapshot folder and file not be used here. 
    Select * from MSmerge_history
    order by time Desc
    Query result is
    Uploading data changes to the Publisher. 
    after that there is no status
    Please help Its very urgent issue

    Hi Ashwin,
    Thanks for the reply.
    PFB verbose output. there are no blocking on both publisher and suscriber.
    2015-01-27 13:07:23.493 Microsoft SQL Server Merge Agent 10.50.1600.1
    2015-01-27 13:07:23.502 Copyright (c) 2008 Microsoft Corporation
    2015-01-27 13:07:23.513 Microsoft SQL Server Replication Agent: replmerg
    2015-01-27 13:07:23.519 
    2015-01-27 13:07:23.524 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2015-01-27 13:07:23.529 User-specified agent parameter values:
    -Publisher Publisher
    -PublisherDB DODA_Prod
    -Publication DODA_PUB
    -Subscriber Subsciber
    -SubscriberDB DODA
    -Distributor Publisher
    -DistributorSecurityMode 1
    -HostName West Ariel
    -Continuous
    -output E:\VerboseData\WAL\Replout.txt
    -XJOBID 0x9BBE899CE4C3FF4DB358BEDD0F7E3970
    -XJOBNAME Publisher-DODA_Prod-DODA_PUB-Subsciber-92
    -XSTEPID 2
    -XSUBSYSTEM Merge
    -XSERVER Publisher
    -XCMDLINE 0
    -XCancelEventHandle 0000000000001A34
    -XParentProcessHandle 0000000000002708
    2015-01-27 13:07:23.619 Percent Complete: 0
    2015-01-27 13:07:23.623 Connecting to Distributor 'Publisher'
    2015-01-27 13:07:23.627 Connecting to OLE DB Distributor at datasource: 'Publisher', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:23.715 OLE DB Distributor: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: 
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:23.722 OLE DB Distributor 'Publisher': {call sp_MSgetversion }
    2015-01-27 13:07:23.738 OLE DB Distributor 'Publisher': {call sp_helpdistpublisher (N'Publisher') }
    2015-01-27 13:07:23.755 OLE DB Distributor 'Publisher': {call sp_MShelp_repl_agent (N'Publisher', N'DODA_Prod', N'DODA_PUB', N'Subsciber', N'DODA', 1)}
    2015-01-27 13:07:23.776 OLE DB Distributor 'Publisher': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'Publisher')
    2015-01-27 13:07:23.781 OLE DB Distributor 'Publisher': {call sp_MShelp_merge_agentid (0,N'DODA_Prod',N'DODA_PUB',null,N'DODA',90,N'Subsciber')}
    2015-01-27 13:07:23.788 OLE DB Distributor 'Publisher': {call sp_MShelp_profile (92, 4, N'')}
    2015-01-27 13:07:23.794 Percent Complete: 0
    2015-01-27 13:07:23.794 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:23.796 Initializing
    2015-01-27 13:07:23.806 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:23.812 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:23.817 Percent Complete: 0
    2015-01-27 13:07:23.818 OLE DB Publisher 'Publisher': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2015-01-27 13:07:23.822 Connecting to Publisher 'Publisher'
    2015-01-27 13:07:23.832 OLE DB Publisher 'Publisher': {call sp_MSgetversion }
    2015-01-27 13:07:23.835 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:23.846 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:23.860 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:23.870 OLE DB Distributor 'Publisher': {call sp_MShelp_repl_agent (N'Publisher', N'DODA_Prod', N'DODA_PUB', N'Subsciber', N'DODA', 1)}
    2015-01-27 13:07:23.878 Connecting to OLE DB Subscriber at datasource: 'Subsciber', location: '', catalog: 'DODA', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:07:29.240 OLE DB Subscriber: Subsciber
    DBMS: Microsoft SQL Server
    Version: 10.00.1600
    catalog name: DODA
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:07:32.330 OLE DB Subscriber 'Subsciber': {call sp_MSgetversion }
    2015-01-27 13:07:33.910 OLE DB Subscriber 'Subsciber': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
    N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
    as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
    2015-01-27 13:07:34.687 Percent Complete: 0
    2015-01-27 13:07:34.687 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:34.690 Connecting to Subscriber 'Subsciber'
    2015-01-27 13:07:34.697 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:35.730 Percent Complete: 0
    2015-01-27 13:07:35.730 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:35.736 Retrieving publication information
    2015-01-27 13:07:35.744 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:07:36.475 Percent Complete: 0
    2015-01-27 13:07:36.484 Retrieving subscription information.
    2015-01-27 13:07:36.490 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:08:03.441 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:08:04.265 Percent Complete: 0
    2015-01-27 13:08:04.269 Uploading data changes to the Publisher
    2015-01-27 13:08:04.278 OLE DB Distributor 'Publisher': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:08:11.122 Connecting to OLE DB Subscriber at datasource: 'Subsciber', location: '', catalog: 'DODA', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:15.591 OLE DB Subscriber: Subsciber
    DBMS: Microsoft SQL Server
    Version: 10.00.1600
    catalog name: DODA
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:08:18.670 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:18.690 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:08:18.697 Connecting to OLE DB Subscriber at datasource: 'Subsciber', location: '', catalog: 'DODA', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:23.111 OLE DB Subscriber: Subsciber
    DBMS: Microsoft SQL Server
    Version: 10.00.1600
    catalog name: DODA
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:08:26.124 Connecting to OLE DB Publisher at datasource: 'Publisher', location: '', catalog: 'DODA_Prod', providerstring: '' using provider 'SQLNCLI10'
    2015-01-27 13:08:26.141 OLE DB Publisher: Publisher
    DBMS: Microsoft SQL Server
    Version: 10.50.1600
    catalog name: DODA_Prod
    user name: dbo
    API conformance: 0
    SQL conformance: 0
    transaction capable: 1
    read only: F
    identifier quote char: "
    non_nullable_columns: 0
    owner usage: 15
    max table name len: 128
    max column name len: 128
    need long data len: 
    max columns in table: 1000
    max columns in index: 16
    max char literal len: 131072
    max statement len: 131072
    max row size: 131072
    2015-01-27 13:39:38.053 The merge process could not retrieve column information for table 'dbo.MAINT_STOCK_COSTS'. Verify that you have sufficient privileges on the database and retry the operation.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.
    2015-01-27 13:39:38.053 
    2015-01-27 13:39:38.078 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:39:39.119 Percent Complete: 0
    2015-01-27 13:39:39.133 No data needed to be merged.
    2015-01-27 13:39:39.138 The process was cancelled.
    2015-01-27 13:39:39.146 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:39:39.902 Percent Complete: 0
    2015-01-27 13:39:39.910 The process was successfully stopped.
    2015-01-27 13:39:39.915 The process was cancelled.
    2015-01-27 13:39:39.926 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. 
    2015-01-27 13:39:39.931 Percent Complete: 0
    2015-01-27 13:39:39.935 Category:NULL
    Source:  Merge Replication Provider
    Number:  -2147200999
    Message: The process was successfully stopped.
    2015-01-27 13:39:39.939 Percent Complete: 0
    2015-01-27 13:39:39.943 Category:NULL
    Source:  Merge Process
    Number:  -2147198718
    Message: The process was cancelled.
    2015-01-27 13:39:39.948 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. 
    2015-01-27 13:39:39.955 The merge process was unable to update last synchronization information at the Publisher.
    2015-01-27 13:39:39.962 OLE DB Subscriber 'Subsciber': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2015-01-27 13:39:40.738 [100%] Percent Complete: 100
    2015-01-27 13:39:40.744 The process was successfully stopped.
    2015-01-27 13:39:40.750 The process was cancelled.
    2015-01-27 13:39:40.756 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.762 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.768 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.773 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.778 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.783 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.787 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.791 Disconnecting from OLE DB Subscriber 'Subsciber'
    2015-01-27 13:39:40.795 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.799 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.805 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.810 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.814 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.819 Disconnecting from OLE DB Publisher 'Publisher'
    2015-01-27 13:39:40.823 Disconnecting from OLE DB Distributor 'Publisher'
    2015-01-27 13:39:40.829 Disconnecting from OLE DB Distributor 'Publisher'

  • Motorola 7232 audio popping during high volume scenes

    Ever since update (with audio alerts) I have noticed popping sound out of all DVRs during high volume scenes. Some channels are more excessive than others...it's almost as if the digital sound is over amped at the source.  Very strange.

    Are you using a surround sound system or is the sound coming out of the TV speakers? There are additional audio settings (dynamic range and audio format) I would suggest modifying as well to see if it can get rid of the popping.
    Anthony_VZ
    **If someones post has helped you, please acknowledge their assistance by clicking the red thumbs up button to give them Kudos. If you are the original poster and any response gave you your answer, please mark the post that had the answer as the solution**
    Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or plan

Maybe you are looking for