Hi all,
I have to 'copy' the production db to different db/instance on the same sql 2008 r2 server to allow users generating reports on that copied db.
How to do this the best way without having to pay attention/modify somthing if in the production db new tables are added/dropped ??
I tried to work with snapshot replication but did not found a way to handle new added tables?!

Thanks for your help
acki4711

I am trying to set up replication for a Dynamics GP 2010 database as part of disaster recovery procedures. I am also new to SQL Server. I have a test setup with SQL Server 2012 with 2 instances on a virtual machine. Replication is from one instance to the other.

I was able to set up transactional replication for the AdventureWorks sample database. The Dynamics database was a bit more difficult. It took 3.5 hours to create the snapshot for the publication and I made sure the snapshot completed successfully before proceeding any further.

I was unable to create the subscription however. After completing the subscription wizard all I had was a dialog showing 'in progress' and nothing else apparently happening. The monitor did not show any activity and there were no related errors in the logs. Twice I let it run for a couple of hours. Eventually both times I clicked on the Stop button, but the dialog just ignored it and kept on churning. All the while, on the server, CPU utilization was consistently up to 100% and no ups and downs.

At this point I really have no clue as to how to proceed. I am reading a lot of stuff but not fast enough to solve this problem.

Any clue would be greatly appreciated.

Thanks in advance

Philippe

Hi All,

I am running SQL Server 2008 R2 in a merge replication topology.  Publisher and distributor are on a single machine.  Server is WS2008 R2.  Connecting to server via SSMS on another machine.  When I am using SSMS to try and run the snapshot agent (right-clicking on Publication, choosing 'View Snapshot Agent Status' and clicking Run), the process hangs on 'Starting agent.'  When I try to click stop, I get:

SQLServerAgent Error: Request to stop job SERVER-DB-PubName-1 (from User sa) refused because the job is not currently running.

When I close this message box, the agent status stays at 'Starting agent.' and doesn't change.  Restarting the SQL engine doesn't help either as this message seems to be the last one logged in the agent history and therefore the one the agent status displays upon re-opening.

Here's the funny part.  If I take the parameters from the snapshot agent job, and use them to manually start the snapshot agent via Command Line, things seem to work fine.  Going back into the Snapshot Agent Status in SSMS I would see 'A snapshot of x articles was generated.'

I cannot find anything different on this server versus several others I have in production (using same configuration) and they are working fine.  However, I need to bring this particular one online and this error is causing me concern, to the point that I'm delaying (under pressure) the rollout until I can figure out what's going on.

Any ideas?  Any help would be greatly appreciated!

Thanks.

Hello Techies ...

What is the safest way to reboot the SQL Server under Transactional Replication , this is one way and not update able subscription.

Regards JakDBA Please Mark this as Answered if this solves your issue or satisfied with the response.

Hi ,

I have  primary key column which has clustered index created in it and now i want to change it to non clustered index this table is part of transitional replication how can i change it with out effecting replication.  

naveen

Greetings,

I configured a SQL Server Web Synchronization between two domains (without VPN, IIS 7.5, SQL Server 2008 R2, Merge replication with pull). The configuration was successful and  i set output log file and have seen the messages like

2013-05-07 04:58:42.347 Downloaded snapshot file 'ACTION_ITEM_ATTACHMENTS_3.sch'.
2013-05-07 04:58:42.862 OLE DB Subscriber 'SERVERNAME\SQL2008R2STD': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2013-05-07 04:58:42.862 Percent Complete: 0
-------------------------------------------------------------
-----------------------------------------------------------
----------------------------------------------------------

My database contains around 700 tables to replicate. After few hours when i checked the status of replication at subscriber side, i realized that it struck with the message like,

2013-05-07 05:27:50.050 Downloaded snapshot file 'UOM_MSTR_366.bcp'.
2013-05-07 05:27:50.752 OLE DB Subscriber 'SERVERNAME\SQL2008R2STD': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2013-05-07 05:27:50.752 Percent Complete: 0
2013-05-07 05:27:50.752 Downloaded snapshot file 'UPGRADE_LOG_367.bcp'.


I restarted the agent and it started from the beginning. After few hours i checked again it shows message as above (with different table name) .  When i checked internet connection between two domain, i have seen that there is a connection timeout in between (for milliseconds only).  

Then i increased internet_timeout property to 1800 at subscriber side. But still getting the issue. What is the cause of this ? How can i overcome this issue?



Regards

Dominic

If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful

Hi SQL Gurus,

Currently, I have AlwaysOn up and running in my production (live) with three node cluster PCI network(server1,2,3) with non-shared storage. Server1 and 2 are in primary DC with synchronous commit. Server3 is in DR DC with ansychronous commit.

Now, there is a new requirement to move some data from production to new server (server4) posibly with Merge replication so that we can filter out some sensitive data. Below are my questions.

1. I believe I would need another server to be remote distributor because I CAN'T add the distributor to the availablity group, is that correct?

2. If I was able to get new server for remote distributor, would server4 need to be added to same cluster with server1,2,3? Or can this server4 be on stane alone with separate from PCI network?

Thanks much,

KongDBA

I have simple transactional replication set up.  One of the publications had 3 articles.  1 of those became unnecessary, so I did:

EXEC sp_dropsubscription @publication =  'Pub_A', @article = 'Art3', @subscriber = 'Sub_Server'

EXEC sp_droparticle  @publication = 'Pub_A', @article = 'Art3' 

This seems to do exactly what I want, which is to keep the publication, but just remove Art3 from the subscription, and then remove Art3 from the Publication altogether.

I understand that the Art3 table will still exist on the subscriber db, and that I have to drop that.  However, at the subscription db, I run

select * from MSreplication_objects
where publication = 'Pub_A' 

This returns 3 replication procs for each of the 3 articles, including the Art3 which I had dropped.  Is this a problem?  Do I need to delete the Art3 rows myself?  I don't think this was ever fully documented, for such a simple process as dropping an article.

Thanks for your insights.

I am trying to setup a Transactional Replication between two SQL 2008 R2 Enterprise servers. The database has many tables that have a rowversion timestamp column and I'm getting errors when it hits one obviously.

Is there an easy way to eliminate them all at once? rather than going through each individual article to exclude them?

We have a table in Sql Server 2008 R2, which has been (Transactional Replication) replicated to two subscriber. We need to increase the size of primary key column from char(14) to char(28).This specific article is part of publication that includes other articles.

I fallowed the following steps and it wroked fine.

1- Remove that article from publication

2- Apply the changes on primary key on publisher and subscribers

3- Re-Add article to publication

When I checked the web,I noticed that many people were talking about fallowing steps:

1- drop the subscription

2- drop the article

3- modify the table

4- add the article
5- add the subscription

Do I need to drop the subscription?

A.G

I have a replication to copy data from Oracle to SQL Server.  The transactional replication would take longer and longer to complete each hour. Each time we restart the logreader, the system will work fine for a few hours but the performance would decline very soon. from hundreds  records to 1 or 2 records every minutes.
 
I generated the logreader log and find that it seems to be the Repldone take very long time. Did anyone experience that before. here is the digest of log. 
 

******************** STATISTICS SINCE AGENT STARTED ***************************
05-13-2013 22:13:45
Execution time (ms): 31284484
Work time (ms): 31282468
Distribute Repl Cmds Time(ms): 31104063
Fetch time(ms): 63673
Repldone time(ms): 26724148
Write time(ms): 84716
   Num Trans: 234  Num Trans/Sec: 0.007480
   Num Cmds: 351882  Num Cmds/Sec: 11.248537

LoadReplCmds time(ms): 4534932
Publisher status requests          (ms): 4340  Pct LoadReplCmds Total 0.1
Publisher synchronization requests (ms): 2789313  Pct LoadReplCmds Total 61.5
Publisher data queries             (ms): 275037  Pct LoadReplCmds Total 6.1
Distribution thread requests       (ms): 1780  Pct LoadReplCmds Total 0.0
Distributor queries                (ms): 26870  Pct LoadReplCmds Total 0.6
Log Reader processing              (ms): 1437592  Pct LoadReplCmds Total 31.7
SyncInit Total                     (ms): 0  Pct LoadReplCmds Total 0.0
SyncDone Total                     (ms): 0  Pct LoadReplCmds Total 0.0
InReconciliation Total             (ms): 0  Pct LoadReplCmds Total 0.0
RowCount Total                     (ms): 0  Pct LoadReplCmds Total 0.0
TracerToken Total                  (ms): 0  Pct LoadReplCmds Total 0.0
Change Total                       (ms): 1713941  Pct LoadReplCmds Total 37.8
SetupCache                         (ms): 468  Pct LoadReplCmds Total 0.0
Repldone time(ms): 26724148
Publisher synchronization requests (ms): 26724148  Pct ReplDone Total 100.0
SyncDone Total                     (ms): 0  Pct ReplDone Total 0.0
*******************************************************************************
2013-05-13 14:13:45.250 Status: 1，code: 22037，text: '共传递了 234个事务，使用了 351882个命令。'。
2013-05-13 14:13:45.250 共传递了 234个事务，使用了 351882个命令。
Disconnecting from OLE DB DISTOLE 'UISMSGQ\MSGQ'
2013-05-13 14:13:45.281 Disconnecting from OLE DB Publisher 'UISMSGQ\MSGQ'

power liang

I have a replication to copy data from Oracle to SQL Server.  The transactional replication would take longer and longer to complete each hour. Each time we restart the logreader, the system will work fine for a few hours but the performance would decline very soon. from hundreds  records to 1 or 2 records every minutes.
 
I generated the logreader log and find that it seems to be the Repldone take very long time. Did anyone experience that before. here is the digest of log. 
 

******************** STATISTICS SINCE AGENT STARTED ***************************
05-13-2013 22:13:45
Execution time (ms): 31284484
Work time (ms): 31282468
Distribute Repl Cmds Time(ms): 31104063
Fetch time(ms): 63673
Repldone time(ms): 26724148
Write time(ms): 84716
   Num Trans: 234  Num Trans/Sec: 0.007480
   Num Cmds: 351882  Num Cmds/Sec: 11.248537

LoadReplCmds time(ms): 4534932
Publisher status requests          (ms): 4340  Pct LoadReplCmds Total 0.1
Publisher synchronization requests (ms): 2789313  Pct LoadReplCmds Total 61.5
Publisher data queries             (ms): 275037  Pct LoadReplCmds Total 6.1
Distribution thread requests       (ms): 1780  Pct LoadReplCmds Total 0.0
Distributor queries                (ms): 26870  Pct LoadReplCmds Total 0.6
Log Reader processing              (ms): 1437592  Pct LoadReplCmds Total 31.7
SyncInit Total                     (ms): 0  Pct LoadReplCmds Total 0.0
SyncDone Total                     (ms): 0  Pct LoadReplCmds Total 0.0
InReconciliation Total             (ms): 0  Pct LoadReplCmds Total 0.0
RowCount Total                     (ms): 0  Pct LoadReplCmds Total 0.0
TracerToken Total                  (ms): 0  Pct LoadReplCmds Total 0.0
Change Total                       (ms): 1713941  Pct LoadReplCmds Total 37.8
SetupCache                         (ms): 468  Pct LoadReplCmds Total 0.0
Repldone time(ms): 26724148
Publisher synchronization requests (ms): 26724148  Pct ReplDone Total 100.0
SyncDone Total                     (ms): 0  Pct ReplDone Total 0.0
*******************************************************************************
2013-05-13 14:13:45.250 Status: 1，code: 22037，text: '共传递了 234个事务，使用了 351882个命令。'。
2013-05-13 14:13:45.250 共传递了 234个事务，使用了 351882个命令。
Disconnecting from OLE DB DISTOLE 'UISMSGQ\MSGQ'
2013-05-13 14:13:45.281 Disconnecting from OLE DB Publisher 'UISMSGQ\MSGQ'

power liang

I have a replication to copy data from Oracle to SQL Server.  The transactional replication would take longer and longer to complete each hour. Each time we restart the logreader, the system will work fine for a few hours but the performance would decline very soon. from hundreds  records to 1 or 2 records every minutes.
 
I generated the logreader log and find that it seems to be the Repldone take very long time. Did anyone experience that before. here is the digest of log. 
 

******************** STATISTICS SINCE AGENT STARTED ***************************
05-13-2013 22:13:45
Execution time (ms): 31284484
Work time (ms): 31282468
Distribute Repl Cmds Time(ms): 31104063
Fetch time(ms): 63673
Repldone time(ms): 26724148
Write time(ms): 84716
   Num Trans: 234  Num Trans/Sec: 0.007480
   Num Cmds: 351882  Num Cmds/Sec: 11.248537

LoadReplCmds time(ms): 4534932
Publisher status requests          (ms): 4340  Pct LoadReplCmds Total 0.1
Publisher synchronization requests (ms): 2789313  Pct LoadReplCmds Total 61.5
Publisher data queries             (ms): 275037  Pct LoadReplCmds Total 6.1
Distribution thread requests       (ms): 1780  Pct LoadReplCmds Total 0.0
Distributor queries                (ms): 26870  Pct LoadReplCmds Total 0.6
Log Reader processing              (ms): 1437592  Pct LoadReplCmds Total 31.7
SyncInit Total                     (ms): 0  Pct LoadReplCmds Total 0.0
SyncDone Total                     (ms): 0  Pct LoadReplCmds Total 0.0
InReconciliation Total             (ms): 0  Pct LoadReplCmds Total 0.0
RowCount Total                     (ms): 0  Pct LoadReplCmds Total 0.0
TracerToken Total                  (ms): 0  Pct LoadReplCmds Total 0.0
Change Total                       (ms): 1713941  Pct LoadReplCmds Total 37.8
SetupCache                         (ms): 468  Pct LoadReplCmds Total 0.0
Repldone time(ms): 26724148
Publisher synchronization requests (ms): 26724148  Pct ReplDone Total 100.0
SyncDone Total                     (ms): 0  Pct ReplDone Total 0.0
*******************************************************************************
2013-05-13 14:13:45.250 Status: 1，code: 22037，text: '共传递了 234个事务，使用了 351882个命令。'。
2013-05-13 14:13:45.250 共传递了 234个事务，使用了 351882个命令。
Disconnecting from OLE DB DISTOLE 'UISMSGQ\MSGQ'
2013-05-13 14:13:45.281 Disconnecting from OLE DB Publisher 'UISMSGQ\MSGQ'

power liang

Hello 

I have two window dedicated server with MS SQL 2008 R2.

Both SQL Server have same databases and I want that If ServerA database data change than it also update the ServerB database, If ServerB database data change than ServerA database also update.

I study MS SQL and I found Replication can do this.

Is it possible to both server have Publisher and subscriber?

I am very new to Replication so please guide me how can I achieve this, is there any other solution is available for this?

This is an oracle instance that I have been replicating to for over 5 years now. The machine was moved to another location and there is a VPN tunnel that this data is being sent over. There are 2 articles and it always fails on 1 of the articles when it is almost done.

Error Message:

David Ryan

I would like to know if we can check the records in publisher and subscriber for any article .

Currently in our environment, checking the row count for articles in publisher and subscriber and sending the alert if there is any mismatch of records.

But, I would like to know how can we check the records if they are same or not...technically it should be same .

I haven't done this before and don't have a test environment to do it. SQL server is moved from existing server to new hardware. Existing server will be turned off once the database is moved to new server which will retain the same name.

We have transactional replication on this server. Is it better to reconfigure the distribution on new server or to restore the backup of distribution database?  Restoring distribution database.. is it straightforward or should I have to do anything extra than the normal restore?

is there any microsoft article in restoring distribution database?

Thanks

kumar

Hello All,

I am using transactional replication on SQL 2008.

There are serveral publications created for more than 100 tables to replicate. I get this message on one of the log reader agent and I don't think the records are replicating.

Can someone please tell me what coudl be wrong?

Thanks,

Paul