Skip snapshot delivery in transactional replication
When you get the msg "The initial snapshot for publication is not yet available......"
The distrib agent is expecting a snapshot to deliver but the snapshot is not available because it was intentionally cancelled.
Is there a way to reset this situation so that the distrib agent continues to deliver commands without applying the snapshot and without the need to reinint the sub?
Yaniv Etrogi
site |
blog | linked in |
mail
Please click the Mark as Answer button if a post solves your problem! or
Vote As Helpful
Hi Michelle,
Your test simulates the issue I am raising.
I run into a situation where the schema generated by the snapshot agent was for all articles and this is not what we needed (we needed a snap just for 2 new articles).
I therefore looked for a way to cause the distrib agent to skip that snapshot delivery while delivering the data (all the pending commands that were in the distribution).
So I did not want to reinit the sub (large database and was not a good option or something we planned for) and I did not want to loose the pending commands.
Finally, when no other solution found, we started removing articles one by one (selecting the smallest tables in size) and after a few articles the distribution agent
started to deliver data and did not look for a snapshot.
-Yaniv
Yaniv Etrogi
site |
blog | linked in |
mail
Please click the Mark as Answer button if a post solves your problem! or
Vote As Helpful
Similar Messages
-
Invalid rowid error while running the snapshot agent in transactional replication
Hi All,
I am getting an Invalid rowid error while replicating an large tables i.e around 30 millions rows from oracle(publisher) to sql server(Subscriber) while running the snapshot agent in transactional replication.
Its taking around 18 hours and its then its throwing this error.
Is there any faster way that i can replicate the initial snapshot this large table as 18 hours is very high on time.
Kindly suggest.i am always got quick and accurate response always..hope the same in this case also.
Thanks,Hi,
Could you please create a replication with some small tables for a test?
You can disable the firewall on both sides and rerun snapshot. Enable verbose logging to level 4 for snapshot agent and check the results if it fails.
http://support.microsoft.com/kb/312292
Here is a document says for the error: ORA-10632: Invalid rowid Cause: Segment Highwatermark was overwritten due to shrink and space reused Action: Reissue this command.
I also suggest you contact the Oracle support team for further help.
Thanks.
Tracy Cai
TechNet Community Support -
Taking snapshot of oracle tables to sql server using transactional replication is taking a long time
Hi All,
I am trying to replicate around 200 oracle tables onto sql server using transaction replication and it taking a long time i.e the initial snapshot is taking more than 24 hrs and it still going on.
Is there any way to replicate those these tables faster?
Kindly help me out..
ThanksHi,
According to the description, I know the replication is working fine. But it is very slow.
1. Check the CPU usage on Oracle publisher and SQL Server. This issue may due to slow client processing (Oracle performance) or Network performance issues.
2. Based on SQL Server 2008 Books Online ‘Performance Tuning for Oracle Publishers’ (http://msdn.microsoft.com/en-us/library/ms151179(SQL.100).aspx). You can enable the transaction
job set and follow the instructions based on
http://msdn.microsoft.com/en-us/library/ms147884(v=sql.100).aspx.
2. You can enable replication agent logging to check the replication behavior. You may follow these steps to collect them:
To enable Distribution Agent verbose logging. Please follow these steps:
a. Open SQL Server Agent on the distribution server.
b. Under Jobs folder, find out the Distribution Agent.
c. Right click the job and choose Properties.
d. Select Steps tap, it should be like this:
e. Click Run agent and click Edit button, add following scripts by the end of scripts in the command box:
-Output C:\Temp\OUTPUTFILE.txt -Outputverboselevel 2
f. Exit the dialogs
For more information about the steps, please refer to:
http://support.microsoft.com/kb/312292
Hope the information helps.
Tracy Cai
TechNet Community Support -
Transactional Replication and Database Snapshots
Hi,
I have a database that is a publisher in transactional replication.
I create a database snapshot on that database and then let transactions replicate to the subscriber(s).
I revert the database back to the snapshot.
What happens to replication?
Dan Jameson
Associate Director of IT/DBA
Children's Oncology Group
http://www.ChildrensOncologyGroup.orgYour Log Reader Agent could fail if the publication database LSN is less than the value of the transaction sequence number (max xact_seqno) at the distribution database. In which case you could execute
sp_replrestart to resynchronize the Publisher metadata with the Distributor metadata.
Afterwards it would wise to run a data validation to see how out of sync you are with the Subscriber and use
tablediff utility or SQL Data Compare to bring the Publisher and Subscriber back into convergence. Reinitialization is an option as well. It depends on exactly what you are trying to achieve.
Brandon Williams (blog |
linkedin) -
Does SAP use SQL server's snapshot and transactional replication?
Gurus:
Could you help with this?
Does SAP use SQL server's snapshot and transactional replication?
Thanks!Hi Christy,
no, SAP does not directly leverage these functions.
But none the less, it is up to you to use these on your system. I regulary use the snapshot functionality when applying Support Packages. In case somehing goes wrong a snapshot is the easiest way to roll back the import process (not exactly the best choice when talking about production and users keep on working while importing).
Have a look at this [document |http://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/SAP_SQL2005_Best Practices.doc]. It deals with Best Practices and also covers snapshot, replication and mirroring.
Sven -
Snapshot Error When Adding Article to Transactional Replication
I am trying to add an table articles to my transactional replication setup. When I do, the snapshot error fails with the following message:
Source: Microsoft.SqlServer.Smo
Target Site: Microsoft.SqlServer.Management.Smo.SqlSmoObject GetSmoObject(Microsoft.SqlServer.Management.Sdk.Sfc.Urn)
Message: Attempt to retrieve data for object failed for Server '<servername>'.
Stack: at Microsoft.SqlServer.Management.Smo.Server.GetSmoObject(Urn urn)
at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.BuildSmoObjectArrayAndUrnLookupTable(IDictionary& dictUrnKeyArticleScriptingBundles)
at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: Microsoft.SqlServer.Smo, Error number: 0)
Get help: http://help/0
Source: Microsoft.SqlServer.Smo
Target Site: Microsoft.SqlServer.Management.Smo.ObjectKeyBase CreateKeyFromUrn(Microsoft.SqlServer.Management.Sdk.Sfc.Urn)
Message: The input Urn must specify Name at level UserDefinedFunction.
Stack: at Microsoft.SqlServer.Management.Smo.SchemaCollectionBase.CreateKeyFromUrn(Urn urn)
at Microsoft.SqlServer.Management.Smo.Server.GetSmoObjectRec(Urn urn)
at Microsoft.SqlServer.Management.Smo.Server.GetSmoObject(Urn urn) (Source: Microsoft.SqlServer.Smo, Error number: 0)
Get help: http://help/0
Specifics:
Transactional replication: Both Immediate Sync and Allow Anonymous are set to 0.
Publisher and Distributer are same server: SQL Server Standard 2008 R2 (10.50.4000.0) on Windows 2008 R2 SP1
If I add even one table article (doesn't matter, I've tried different ones), I get the error above when I run the snapshot agent.
If I remove the table just added and rerun the snapshot agent, it succeeds with the message "A snapshot was not generated because no subscriptions needed initialization", so at least I don't have to reinitialize (thank goodness!).
Any ideas as to what might be causing this, and how I can add articles to my existing publication?
Thanks in advance for your help.Hi John V.Barone,
I’m writing to follow up with you on this post. Was the problem resolved after performing our action plan steps? If not, according to your error message, we need to verify if it is caused by replicating Meta Data corruption. You can check if there is a bad
row
in “sysarticles” (for a table) or “sysschemaarticles” (for a UDF) for which we do not have a corresponding “ObjectId” in sysobjects . If yes, delete
manually this row
from Published (sysarticles, sysschemaarticles, syssubscriptions) and Distribution DB (MSsubscriptions,sysschemaarticles,MSarticles).
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Sp_addscriptexec is not working with FTP Snapshot delivery
Hi,
We have a SQL Server Merge Replication topology. Both Publisher a Subscribers are using SQL Server 2012.
As I have seen in http://msdn.microsoft.com/en-us/library/ms174360(v=sql.120).aspx
"Using sp_addscriptexec to
post a script file for publications using FTP for snapshot delivery is only supported for Microsoft SQL Server Subscribers."
So we should be OK...
The problem is that the Merge Agent is looking for the Script in the local PC instead of download it form the
FTP Server.
Here is the Code at the publisher:
exec sp_addscriptexec 'IPoint_Pub','C:\IPoint_Files\ReplicationScripts\User\reIndex.sql'
This is how the subscription was created:
use IPoint
exec sp_addmergepullsubscription @publisher = @Central_Server_Name, @publication = N'IPoint_Pub', @publisher_db = @MGR_DB, @subscriber_type = N'Local', @subscription_priority = 0, @description = N'', @sync_type = N'Automatic'
exec sp_addmergepullsubscription_agent
@publisher = @Central_Server_Name,
@publisher_db = @MGR_DB,
@publication = N'IPoint_Pub',
@distributor = @Central_Server_Name,
@distributor_security_mode = 0, @distributor_login = 'XXX', @distributor_password = 'XXX',
@enabled_for_syncmgr = N'True',
@frequency_type = 4, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 1, @frequency_subday = 4, @frequency_subday_interval = 3, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 20100527, @active_end_date = 99991231,
@alt_snapshot_folder = N'', @working_directory = N'',
@use_ftp = N'True',
@job_login = null, @job_password = null,
@publisher_security_mode = 0, @publisher_login = 'XXX', @publisher_password = 'XXX',
@use_interactive_resolver = N'False', @dynamic_snapshot_location = null, @use_web_sync = 0,
@hostname =@SUCURSAL_ID
GO
And the log of the REPLMERG.EX
2014-03-29 13:01:49.009 Microsoft SQL Server Merge Agent 11.0.2100.60
2014-03-29 13:01:49.009 Copyright (c) 2008 Microsoft Corporation
2014-03-29 13:01:49.009
2014-03-29 13:01:49.009 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-03-29 13:01:49.009 User-specified agent parameter values:
-Publication Netul_Pub
-Publisher SRV01
-Subscriber NETUL-01\SQLEXPRESS
-Distributor SRV01
-PublisherDB IPoint_Netul
-SubscriberDB IPoint
-SubscriptionType 1
-ParallelUploadDownload 1
-DistributorLogin sucursal
-DistributorPassword **********
-DistributorSecurityMode 0
-PublisherLogin sucursal
-PublisherPassword **********
-PublisherSecurityMode 0
-SubscriberSecurityMode 1
-OutputVerboseLevel 1
-Validate 0
2014-03-29 13:01:49.019 Connecting to Subscriber 'NETUL-01\SQLEXPRESS'
2014-03-29 13:01:50.654 Connecting to Distributor 'SRV01'
2014-03-29 13:01:51.599 Initializing
2014-03-29 13:01:51.604 Validating publisher
2014-03-29 13:01:51.614 Connecting to Publisher 'SRV01'
2014-03-29 13:01:51.769 Retrieving publication information
2014-03-29 13:01:51.774 Retrieving subscription information.
2014-03-29 13:01:52.294 Connecting to Subscriber 'NETUL-01\SQLEXPRESS'
2014-03-29 13:01:52.304 Connecting to Distributor 'SRV01'
2014-03-29 13:01:52.414 Initializing
2014-03-29 13:01:52.429 Validating publisher
2014-03-29 13:01:52.439 Connecting to Publisher 'SRV01'
2014-03-29 13:01:52.604 Retrieving publication information
2014-03-29 13:01:52.619 Retrieving subscription information.
2014-03-29 13:01:53.274 [29%] [0 sec remaining] Snapshot files will be downloaded via ftp
2014-03-29 13:01:53.284 [29%] [0 sec remaining] Snapshot will be applied from a compressed cabinet file
2014-03-29 13:01:53.294 [29%] [0 sec remaining] Connecting to ftp site 'SRV01.real2b.com'
2014-03-29 13:01:55.019 [33%] [2 sec remaining] Extracting snapshot file 'Documento_Formc3f5d2f9_190.sch' from cabinet file
2014-03-29 13:01:55.064 [33%] [2 sec remaining] Extracted file 'Documento_Formc3f5d2f9_190.sch'
2014-03-29 13:01:57.299 [33%] [2 sec remaining] Applied script 'Documento_Formc3f5d2f9_190.sch'
2014-03-29 13:01:57.304 [33%] [2 sec remaining] Preparing table 'Documento_Formulario_Otros' for merge replication
2014-03-29 13:02:02.574 [51%] [8 sec remaining] Extracting snapshot file 'sysmergesubsetfilters_Documento_Formulario_Otros90.bcp' from cabinet file
2014-03-29 13:02:02.594 [51%] [8 sec remaining] Extracted file 'sysmergesubsetfilters_Documento_Formulario_Otros90.bcp'
2014-03-29 13:02:02.604 [55%] [7 sec remaining] Bulk copying data into table 'sysmergesubsetfilters'
2014-03-29 13:02:02.609 [55%] [7 sec remaining] Bulk copied data into table 'sysmergesubsetfilters' (0 rows)
2014-03-29 13:02:02.619 [55%] [7 sec remaining] Extracting snapshot file 'Documento_Formc3f5d2f9_190.dri' from cabinet file
2014-03-29 13:02:02.624 [55%] [7 sec remaining] Extracted file 'Documento_Formc3f5d2f9_190.dri'
2014-03-29 13:02:02.864 [55%] [7 sec remaining] Applied script 'Documento_Formc3f5d2f9_190.dri'
2014-03-29 13:02:02.874 [59%] [6 sec remaining] Extracting snapshot file 'Documento_Formc3f5d2f9_190.trg' from cabinet file
2014-03-29 13:02:02.884 [59%] [6 sec remaining] Extracted file 'Documento_Formc3f5d2f9_190.trg'
2014-03-29 13:02:02.889 [62%] [5 sec remaining] Applied script 'Documento_Formc3f5d2f9_190.trg'
2014-03-29 13:02:02.899 [62%] [5 sec remaining] Extracting snapshot file 'Documento_Formc3f5d2f9_190.prc' from cabinet file
2014-03-29 13:02:02.919 [62%] [5 sec remaining] Extracted file 'Documento_Formc3f5d2f9_190.prc'
2014-03-29 13:02:03.819 [62%] [5 sec remaining] Applied script 'Documento_Formc3f5d2f9_190.prc'
2014-03-29 13:02:09.334 [74%] [5 sec remaining] Launching sqlcmd to apply the script 'Create_Categorias_Tables.sql'
2014-03-29 13:02:09.974 [74%] [5 sec remaining] Applied script 'Create_Categorias_Tables.sql'
2014-03-29 13:02:09.979 [77%] [4 sec remaining] Launching sqlcmd to apply the script 'Create_Categorias_Tables.sql'
2014-03-29 13:02:10.144 [77%] [4 sec remaining] Applied script 'Create_Categorias_Tables.sql'
2014-03-29 13:02:10.174 [81%] [3 sec remaining] Launching sqlcmd to apply the script 'reIndex.sql'
2014-03-29 13:02:10.189 [81%] [3 sec remaining] Last 115 characters in 'sqlcmd' output buffer: Sqlcmd: 'C:\inetpub\ftproot\ReplData\ftp\SRV01_IPOINT_NETUL_NETUL_PUB\UserScripts\reIndex.sql': Invalid filename.
2014-03-29 13:02:10.194 [81%] [3 sec remaining] Failed to apply the script 'reIndex.sql' using the 'sqlcmd' utility.
2014-03-29 13:02:10.204 The schema script 'reIndex.sql' could not be propagated to the subscriber.
2014-03-29 13:02:10.254 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'reIndex.sql' could not be propagated to the subscriber.
2014-03-29 13:02:10.259 [100%] The process was successfully stopped.
2014-03-29 13:02:10.299 Category:NULL
Source: Merge Replication Provider
Number: -2147200963
Message: The process was successfully stopped.
As you can see, the FTP snapshot is working fine
"Extracted Documento_Formc3f5d2f9_190.trg"
But the it is looking for a file that only exists in the server.
'C:\inetpub\ftproot\ReplData\ftp\SRV01_IPOINT_NETUL_NETUL_PUB\UserScripts\reIndex.sql'
Do you have any idea?
Best Regards, Daniel.Hi again Brandon,
I understand what you are saying and I know it would solve the problem, but it's now our case.<o:p></o:p>
We have other installations with Merge Replication using a shared path (UNC) to download the initial snapshot and every user script is downloaded also from
de shared location fine.<o:p></o:p>
In this case,
we have no direct access to a shared folder in server. The full replication process is done by internet without VPN.<o:p></o:p>
I think the “Snapshot folder” it's well configured as the snapshot it’s being downloaded OK from the
FPT Server.<o:p></o:p>
My question is: Why the merge agent connects to the FPT server for download de Snapshot but it does not do the same to download the user script??<o:p></o:p>
May be it’s a bug in the Merge Agent or some parameter I am not passing?<o:p></o:p>
This is the merge agent invocation:<o:p></o:p>
REPLMERG.EXE -Publication %Publication% -Publisher %Publisher% -Subscriber %Subscriber% -Distributor %Publisher% -PublisherDB %PublicationDB% -SubscriberDB %SubscriptionDB% -SubscriptionType 1 -ParallelUploadDownload 1 -DistributorLogin %user% -DistributorPassword %password% -DistributorSecurityMode 0 -PublisherLogin %user% -PublisherPassword %password% -PublisherSecurityMode 0 -SubscriberLogin %user% -SubscriberPassword %password% -SubscriberSecurityMode 1 -OutputVerboseLevel 1 -Validate 0
Best Regards, Daniel. -
I've set up Replication (transactional replication) between two remote servers. On the one of server that I configure Distribution & publication .another server is subscription. The subscription is all set & snapshot agent is started .but the actual
replication doesn't take place.
When viewing the Synchronization Status of the subscription, i get an error, saying "The process could not connect to Subscriber ‘Server name'."
Clicking on start, this is the error message I get:
The agent could not be started.
Additional information:
An exception while executing a Transact-SQL statement or batch.
SQL Server Agent Error: Request to run job Server1-EDUSRV-Pubs-Server2-14 (from User Server1\Administrator) refused because the job is already running from a request by User sa.
Change database context to 'EDUSRV'.(Microsoft SQL Server Error:22022)
What can i do?
Please help me.ThanksThe error The process could not connect to Subscriber 'Server name' indicates that the Distribution Agent process account does not have enough permissions to connect to the Subscriber.
If this is a push subscription, verify the Distribution Agent process account is db_owner in the distribution and subscription databases, is a member of the PAL, and has read permissions on the snapshot share.
If this is a pull subscription, verify the Distribution Agent process account is db_owner in the subscription database, is a member of the PAL, and has read permissions on the snapshot share.
The permissions required are covered in
Replication Agent Security Model.
If you have anymore questions, please let me know. I hope this helps.
Brandon Williams (blog |
linkedin) -
Transactional replication from a failover cluster instance to a SQL Server Express DB
Hello,
I have been poking around on Google trying to understand if there are any gotchas in configuring transactional replication on a instance DB of a failover cluster, to a SQL Server Express DB. Also, this client would like to replicate a set of tables between
two instances DB's which both reside on nodes of the cluster.
Everything I've read suggests there is no problem using transactional replication on clustered instance as long as you use a shared snapshot folder. I still have some concerns:
1) Should the distributor need to live on a separate instance?
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber.
There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Thanks in advance.1) Should the distributor need to live on a separate instance?
Answer: It is recommended to configure the distributor on the different server, but it also be configured on Publisher/subscriber server. (Subscriber in our case is not possible as its a Express edition)
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber. There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Answer: If you configure both publisher and distributor on the same server and the SQL instance is failed over, the data synchronization/replication is suspended till the instance comes online.
Once the instance is up,all the replication jobs will start again and it will continue to synchronize the data to subscriber. No manual intervention is required. -
Transactional Replication Stalled.
Hi,
We are having a Transactional replication issue where the Data does not get replicated and the log Just keeps grawing.
Last week we had an accidental load 15 Million records, on one of the T replication enabled Db's .Then the replication stopped working i mean i look at the replication monitor it says NO transactions to replicate but we have a lot difference
with the DATA.I also see that the logfile file for the DB is growing.
1.I did a few things like stopping the log reader and restarting.
2.Reinitialize the Snapshot ,the snapshot is taken but is not being applied to the subscriber .No error msg that i can see.
So had to drop the replication entirely , shrink the log and recreate it adding few bunches of articles, creating a snapshot for them wait until they are applied and then add the other articles which worked fine for few days , and DB replication
stopped again and log started growing.This time it is also effecting other replications this time too.
I am running out of options can some one plz help!
THanks,
JackThat message means the log reader agent is going through the log reading commands from it. If your ETL operation does large batch operations replication many not be able to keep up. You might need to break these batches up into smaller batches - batchsize
works well here.
Another thing to consider is to do your ETL operation on both sides. This works well if the only source of changes occurs from the ETL process - then you would not publish these tables.
If not - think about use MaxCmdsInTran - you can set this to something like 10,000 which means that if you do a million row update - the log reader agent will start to read the commands out of the log for every 10,000 changes and replicate them to the subscriber
- before the transaction is committed on the publisher.
This is a command that you can put in your log reader agent profile so you can turn it off when the ETL process is done and replicated.
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 -
Transactional replication very slow with indexes on Subscriber table
I have setup Transactional Replication for one of our databases where one table with about 5mln records is replicated to a Subsriber database. With every replication about 500-600.000 changed records are send to the Subscriber.
Since one month I see very strange behaviour when I add about 10 indexes to the Subscriber table. As soon as I have added the indexes replication speed becomes extremely slow (almost 3 hours for 600k records). As soon as I remove the indexes the replication
is again very fast, about 3 minutes for the same amount of records.
I've searched a lot on the internet to solve this issue but can't find any explaination for this strange behaviour after adding the indexes. As far as I know it doesn't have to be a problem to add indexes to a Subscriber table, and it hasn't been before on
another replication configuration we use.
Some information from the Replication Log:
With indexes on the Subscriber table
Total Run Time (ms) : 9589938 Total Work Time : 9586782
Total Num Trans : 3 Num Trans/Sec : 0.00
Total Num Cmds : 616245 Num Cmds/Sec : 64.28
Total Idle Time : 0
Writer Thread Stats
Total Number of Retries : 0
Time Spent on Exec : 9580752
Time Spent on Commits (ms): 2687 Commits/Sec : 0.00
Time to Apply Cmds (ms) : 9586782 Cmds/Sec : 64.28
Time Cmd Queue Empty (ms) : 5499 Empty Q Waits > 10ms: 172
Total Time Request Blk(ms): 5499
P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
Reader Thread Stats
Calls to Retrieve Cmds : 2
Time to Retrieve Cmds (ms): 10378 Cmds/Sec : 59379.94
Time Cmd Queue Full (ms) : 9577919 Full Q Waits > 10ms : 6072
Without indexes on the Subscriber table
Total Run Time (ms) : 89282 Total Work Time : 88891
Total Num Trans : 3 Num Trans/Sec : 0.03
Total Num Cmds : 437324 Num Cmds/Sec : 4919.78
Total Idle Time : 0
Writer Thread Stats
Total Number of Retries : 0
Time Spent on Exec : 86298
Time Spent on Commits (ms): 282 Commits/Sec : 0.03
Time to Apply Cmds (ms) : 88891 Cmds/Sec : 4919.78
Time Cmd Queue Empty (ms) : 1827 Empty Q Waits > 10ms: 113
Total Time Request Blk(ms): 1827
P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
Reader Thread Stats
Calls to Retrieve Cmds : 2
Time to Retrieve Cmds (ms): 2812 Cmds/Sec : 155520.63
Time Cmd Queue Full (ms) : 86032 Full Q Waits > 10ms : 4026
Can someone please help me with this issue? Any ideas?
PimHi Megens:
Insert statement might be slow with not only indexes and few others things too
0) SQL DB Blocking during inserts
1) If any insert triggers are existed
2) Constraints - if any
3) Index fragmentation
4) Page splits / fill factor
Without indexes inserts will be fast because, each time when new row going to insert to the table, SQL Server will do
1) it will check for the room, if no room page splits will happen and record will placed at right place
2) Once the record updated all the index should be update
3) all these extra update work will cause can make insert statement bit slow
Its better to have index maintenance jobs frequently to avoid fragmentation.
If every thing is clear on SQL Server Side, you need look up on DISK IO, N/W Latency between the servers and so on
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :) -
Transactional replication issue
Hi,
i have configured transactional replication with separate distributor server, the data copied and snapshot delivered,last 2days it is running, publisher to distributor is good, but distributor to subscriber it show heavy latency and it is showing critical
status,when i see in the replication monitor, it shows undistributed commands 65000 records, when i see in snchronization status it showing 'deliverimg replication', when i compare to publisher and subscriber records difference is there, i checked the file
tranfer speed 100mbps and bandwidth speed is als good....how to fix itWas there any issue which caused replication to stop for some time or was there any huge updates that happened at publisher..
Take a look at this link..
http://blogs.msdn.com/b/chrissk/archive/2009/05/25/transactional-replication-conversations.aspx
It explains very clearly to troubleshoot this.. You might only have to look at the distribution agent latency part, as per your description...
Apart from this, check if there are any triggers in the subscriber end which is making the subscriber updates slow..
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com -
Please help me..
After configuring Transactional Replication with a publisher, distributor , subscriber and with one database and one table . and in subscriber the database in read write mode. so, we can perform changes . Here my question is....
we performed some changes in table (other than primary key column) in subscriber db.
Then both db's have different vales ( publisher db and subscriber db). how will face this scenario?Hi,
As Hilary said, if you make changes in the publisher database, the data which you changed on the same row in the subscriber database will be replaced.
Do you want to synchronize the changes between subscriber and publisher in both directions? If so, you need to Merge replication.
Merge replication, like transactional replication, typically starts with a snapshot of the publication database objects and data. Subsequent data changes and schema modifications made at the Publisher and Subscribers are tracked with triggers.
The Subscriber synchronizes with the Publisher when connected to the network and exchanges all rows that have changed between the Publisher and Subscriber since the last time synchronization occurred.
Thanks.
Tracy Cai
TechNet Community Support -
Transactional replication with 1 publisher 2 subscribers in SQL 2012 SE
I have a setup of transaction replication between one publisher and subscriber in the Same server.Now, I need to add a new subscriber to the existing publisher. So publisher database name is DB_A and Subscriber 1 name is DB_B. So the new subscriber will
be DB_C.
Is this kind of setup possible on one server?
If yes then at the time of reinitialization is it going to apply the snapshot on DB_B as well as DB_C?
Also let say if due to disk error DB_B gets corrupted then will data be still replicated between DB_A and DB_C? (Assuming publisher, subscriber 1 and 2 are sitting on individual disks)
Need your valuable thoughts experts.
Thanks a ton.For that you have to setup replication with backups. Assuming you had a failure and the only option now is to reinitialize, then instead you basically drop the subscription, change the publication property to
allow_initialize_from_backup to true. Now you can follow the article below to create the subscription. Instead of using the backup from publisher you can use the old backup of subscriber. In this case, you need to confirm that
all the data that is in the publisher (which needs to be replicated) is already there in subscriber.
http://msdn.microsoft.com/en-us/library/ms147834.aspx
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com -
Transactional replication issues
SQL 2012 for both servers.
Basically I would like to set up a (transactional I think) replication of few articles from serverA to serverB.
I created publication and I created subscription (push) related to serverB.
In the past, on a sql 2005 instance I used distrib.exe on publication server to deliver changes on subscriber and it worked well.
On sql 2012, running distrib.exe does not deliver anything .. and I don't understand why.
Please remember that my main goal is to deliver changes in articles from serverA to serverB "on demand".
Can you please help ?
Any help appreciated, best regards.I configured transactional replication because it seems the best choice in my scenario.
"C:\Program Files\Microsoft SQL Server\110\COM\DISTRIB.EXE" -Subscriber %Subscriber%
-SubscriberDB %SubscriptionDB% -SubscriberSecurityMode 1 -Publication %Publication%
-Publisher %Publisher% -PublisherDB %PublicationDB% -Distributor %Publisher%
-DistributorSecurityMode 1 -Continuous -SubscriptionType 0 -SubscriptionStreams 4 Isn't "-Continuos" the contrary of "on demand" ? Do I really need it ?However in my command line instructions I miss these 3 parameters: -Continuous -SubscriptionType 0 -SubscriptionStreams 4however it worked well in the past also without them.I deleted replication jobs (cleanup ... ) too because I would like to start from scratch but now they are not recreatec.Thanks for help.-
The distrib.exe works only with transactional and snapshot replication. I hope you are configured replication with Transactional replication topology.
It should work in the same way that it used to work with SQL 2005.
Reference:-
http://technet.microsoft.com/en-us/library/ms151169.aspx
Push subscriptions can be synchronized programmatically and on-demand by invoking the appropriate replication agent executable file from the command prompt. The replication agent executable file that is invoked will depend on the type of publication
to which the push subscription belongs.
To start the Distribution Agent to synchronize a push subscription to a transactional publication
From the command prompt or in a batch file at the Distributor, execute distrib.exe. Specify the following command-line arguments:
-Publisher
-PublisherDB
-Distributor
-Subscriber
-SubscriberDB
-SubscriptionType = 0
REM -- Declare the variables.
SET Publisher=%instancename%
SET Subscriber=%instancename%
SET PublicationDB=AdventureWorks2012
SET SubscriptionDB=AdventureWorks2012Replica
SET Publication=AdvWorksProductsTran
REM -- Start the Distribution Agent with four subscription streams.
REM -- The following command must be supplied without line breaks.
"C:\Program Files\Microsoft SQL Server\110\COM\DISTRIB.EXE" -Subscriber %Subscriber%
-SubscriberDB %SubscriptionDB% -SubscriberSecurityMode 1 -Publication %Publication%
-Publisher %Publisher% -PublisherDB %PublicationDB% -Distributor %Publisher%
-DistributorSecurityMode 1 -Continuous -SubscriptionType 0 -SubscriptionStreams 4
http://technet.microsoft.com/en-us/library/ms147886.aspx
-Prashanth
Maybe you are looking for
-
Dear Guys, Let me know implications on business when tax procudure changed from TAXINJ to TAXINN ans also how to do the configuration, send me some documents Regards: Tata Reddy
-
Payment program Customizing steps(for the program RFFOUS_T )
Hello all, we are planing to generate ACH file for the Remitanace advice, when we run the payment program( F111 - to pay payment orders) I dont know the required customizing that i need to do in FBZP, to get ACH file when we generate payments for a s
-
CF9 and Amazon S3 - Has anyone got this to work?
I've now sorted my other issues and thanks to everyone who helped me with them - I've now moved on to trying to create a set of services that will connect to the S3 cloud and post and retrieve pdf files in our buckets - We need to be able to supply v
-
I can't find how to make a contact sheet from Bridge 5. I did find something that creates a pdf but it's no where near as good and fast as the way to do it in Bridge 3. I used to be able to select 'make contact sheet' through the Tools menu - photosh
-
How to restore the FM Bands into iTunes?
How to restore the FM Bands into iTunes?