Articles on this Page
- 08/22/16--08:38: _Side by side upgrad...
- 08/22/16--09:06: _Good Way To Failbac...
- 08/23/16--03:27: _SQL Server Replicat...
- 08/23/16--13:16: _2012 standard editi...
- 08/24/16--00:59: _Moving 1.2TB SQL Se...
- 08/24/16--01:20: _Replication stopped...
- 08/24/16--08:50: _Replication automat...
- 08/07/16--22:59: _How do you calculat...
- 08/25/16--05:38: _Issues with Log Rea...
- 08/26/16--09:54: _A dynamic snapshot ...
- 04/08/11--11:38: _The merge process c...
- 05/05/11--07:39: _maxversion_at_cleanup
- 12/22/11--22:53: _Rplication :The mer...
- 08/27/16--22:57: _Cannot exec sp beca...
- 08/29/16--13:59: _SQL Server 2008 R2 ...
- 08/30/16--06:01: _SQL Server Replicat...
- 08/31/16--15:19: _Replication subscri...
- 05/27/13--17:06: _Peer to Peer replic...
- 09/01/16--12:15: _Difference between ...
- 09/02/16--11:06: _Clustering Suggesti...
- 08/22/16--08:38: Side by side upgrade replication from SQL server 2005 to 2008 R2
- 08/22/16--09:06: Good Way To Failback Using Replication During SQL Upgrades
- 08/23/16--03:27: SQL Server Replication Problem
- 08/23/16--13:16: 2012 standard edition clustering
- 08/24/16--00:59: Moving 1.2TB SQL Server 2008R2 database to new storage
- 08/24/16--01:20: Replication stopped working after data refresh
- 08/24/16--08:50: Replication automatically re-initializes by itself
- 08/07/16--22:59: How do you calculate the space required for snapshot ?
- 08/25/16--05:38: Issues with Log Reader Agent status in Replication Monitor
- 05/05/11--07:39: maxversion_at_cleanup
- 08/27/16--22:57: Cannot exec sp because of replication
- 08/31/16--15:19: Replication subscription with manual backup restore without snapshot
- 05/27/13--17:06: Peer to Peer replication primary key conflict (Emergency)
- 09/02/16--11:06: Clustering Suggestion Required
Is there a faster ways rather than to recreate replication from scratch. I am wanting to upgrade server 2005 SP4 replicated Dynamics SQL Server to 2008R2.
I was searching for something that can do to Just restore the system databases from 2005 to 2008R2 and then detach attach the databases from 2005 to 2008R2.
Another way was to <g class="gr_ gr_15 gr-alert gr_spell gr_run_anim ContextualSpelling" data-gr-id="15" id="15">setup</g> log shipping between 2005 and 2008R2 and then on the cutover day, go the usual route or bring database to recovery / backup database and restore on <g class="gr_ gr_21 gr-alert gr_gramm gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="21" id="21">second</g> server (subscriber) / and reestablish replication. But this is a long way of doing a thing. remember the database is 400 GB.
Currently I am looking at upgrading a 2008 instance to 2014 and would like to have an option to roll back to the 2008 instance up to 24 hours after the upgrade with all the data in tact. My plan was to either init replication from backup to 2014 or to mirror up.
Please let me know if you know of a better approach or lesser known caveats to this approach. I'm not sure if Updatable Subscribers is a good option in this case but it seems like it has room for issues and there are text columns in the db which would have to be accounted for.
Either way to roll back I was going to setup transactional replication with a 2014 being the distributor and have 2008 be the publisher. In order the plan is to:
-Failover to 2014 via replication backup init or mirroring, upgrade compatibility level, etc. etc.
-run scripts to start snapshots on the databases, already pre timed them, takes a few minutes. Conduct live QA.
-while snapshots are running, run scripts to deattach current dbs and move mdfs to a new subfolder
-recreate the dbs from scripts with all the same options as prior
-trans replicate back to those databases
I have one stage server database in which consists of 20 tables. These to be transferred from this server to another server, say to production server. Previously, our dba’s are replicated those and they have scheduled hourly and daily snapshots replication, so every hour and daily a folder is created with unique name. Is it possible to replicate with same name?
The problem we have right now is a 10 min delay in the data retrieval (means data is showing blank) on our application. This is happening daily in one particular point of time. As per our analysis we came to a conclusion that while replicating from stage to production, the data is deleting and adding a new one in the production server. During this session, the application might be delaying to display the records.
If this will be the actual case, is there any alternative to overcome this issue, so that data should not affect the application? If not, what will be the reason and solution for this?
we are using sql server 2012 standard edition. I have one question regarding sql server standard edition. I know that in standard edition we cannot have more than 2 nodes in a cluster. but the question is can one cluster (with two nodes) replicate data from the database(lets sat Database1) to another cluster( with two nodes) database(let say Database1)?
Recently we got new faster storage, we are planning to move the database data(mdf, ldf) files to faster storage. One of the database size was 1.2TB and that database was configured for replication. Approved downtime was only max. of 4hours.
Any thoughts/suggestions much appreciated. Thanks in advance!
We have two databases in prod DB1 and reportdb1
There is transnational replication set from DB1 to Reportdb1
The same we have in Development environment as well.
DBDev1 and ReportDBDev
This time we did a data refresh from DB1 to DBDev1 , after that replication stopped working.
Can you please suggest what went wrong here, do we need to do anyother steps to prevent the replication from breaking.
we have 500millions of records of huge table which is replicating from A to B (both sql 2012) Servers. After all the data got synched up and the indexes were added on to replication automatically re-intializes byitself
I do see something weird in transnational replication snapshot - Can you plz help me in finding the root cause ?
When I created the initial snapshot for one big table with 350GB data and 250GB index size (shouldn't be but...) on SQL Server 2012 (SP1), snapshot folder size was 900 GB. For some reasons, I had to scrap everything and re set up the replication. At this moment Snapshot folder size has crossed 1.7 TB and not even 50% of the records has been processed, I am running out of clue for this. There has not been significant changes in number of records and table size since last snapshot.
Appreciate your insight !
While checking replication status for using Replication Monitor, replication seems to be raising some error. Checked under agents tab and found log reader agent was not running but when i check in job activity monitor log reader agent is running from last 2 hours without any issues. Inserted tracer token and I could see commands flowing from publisher to subscriber. Excuted below TSQL and found commands were indeed getting distributed.
select agent_id,sum(UndelivCmdsInDistDB) as UndeliveredCommands,
sum(DelivCmdsInDistDB) as DeliveredCommands
from MSdistribution_status --WHERE agent_id=5
View details section in Subscription watchlist tab shows below error.
The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated. (Source: MSSQLServer, Error number: 21074)
Get help: http://help/21074
Executed below commands and didn't find any inactive subscription.
SELECT * FROM [dbo].[MSsubscriptions] WHERE status !=2
ENV : SQL Server 2012 (SP1)
Distribution agent is also running without any issue. To me it looks like replication monitor is showing incorrect info - Not sure if I am missing something important.
Appreciate your insight. Thank you.
I'm getting the following error after adding a dynamic filter on my replication scheme.
"A dynamic snapshot is required because the publication '123' contains both dynamic filters and logical record relationships"
So far I have not been able to find out what the problem is. I have not found any useful information regarding this error, I have tried recreating the dynamic snapshots with no success. I'm using SQL Server 2012
Any suggestions are appreciated.
Hi, we have a merge pull replication in SQL Server 2008 R2 (publisher) and SQL Express 2008 (subscribers)
The publication contains almost 200 articles.
We are having trouble in only one article.
When we update / insert a row in that table, all the subscribers fail to sync with the following error:
The merge process could not retrieve column information for table 'dbo.Tipo_Movimiento_Caja'. Verify that you have sufficient privileges on the database and retry the operation. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201016)
Cannot synchronize the subscription because the schemas of the article at the Publisher and the Subscriber do not match. It is likely that pending schema changes have not yet been propagated to the Subscriber. Run the Merge Agent again to propagate the changes and synchronize the data. (Source: MSSQLServer, Error number: 25007)
The script of that article is really simple, and it has no join filters:
exec sp_addmergearticle @publication = N'IPoint_Pub', @article = N'Tipo_Movimiento_Caja', @source_owner = N'dbo', @source_object = N'Tipo_Movimiento_Caja', @type = N'table', @description = N'', @creation_script = N'', @pre_creation_cmd = N'drop', @schema_option = 0x000000010C034FD1, @identityrangemanagementoption = N'manual', @destination_owner = N'dbo', @force_reinit_subscription = 1, @column_tracking = N'false', @subset_filterclause = N'', @vertical_partition = N'false', @verify_resolver_signature = 1, @allow_interactive_resolver = N'false', @fast_multicol_updateproc = N'true', @check_permissions = 0, @subscriber_upload_options = 1, @delete_tracking = N'true', @compensate_for_errors = N'false', @stream_blob_columns = N'true', @partition_options = 0
I've compared the schemas of the publisher and each subscriber and I didn't notice any difference.
Indeed, yesterday we dropped all subscribers Data Bases and recreated the subscription, so there's no chance the schemas are different.....
That's only happening in one table...
Thanks a lot in advance!
Best Regards, Daniel.
for several articles maxversion_at_cleanup column
in the sysmergearticles table contains a very
large value, 788438623, 2031311968, for example, while for most other
articles this column is less than 10000.
I want to know what this column is used for in merge replication and is it
normal with such large values?
Would this cause our "uplineage" delay problem? Can we manually reduce the
large values as a test?
we are having issues and see that the "maxversion_at_cleanup" value is used on the replication
update trigger for the "lineage" column on the msmerge_contents table, and
the sp_msuplineageversion stored procedure will use this lineage in a
"while..." loop. So it seems that if the Lineage is very large, it will
take a long time for the sp_msuplineageversion
i have 2 subscirbers in publisher side for merge replication.
I added filters for one table at Publisher side in middle of merge replication working,after some time i removed the filter.
then iam getting this error 'The merge process could not retrieve column information for table 'dbo.ATTRIBUTE_DASHBOARD'. Verify that you have sufficient privileges on the database and retry the operation.' at subscriber side when running view sysn status.
Kindly help me to find out the exact rootcause.
Thanks in advance....
Rajesh Kumar Tuta
In my environmet many years ago , befor me was merg replication on server 2000 now all server are 2012 and delete merg replication but when i want to exec a sp that want exec insert rowset return error :
while this table is not in replication :
Msg 3609, Level 16, State 1, Line 1
The transaction ended in the trigger. The batch has been aborted.
Msg 20092, Level 16, State 1, Procedure MSmerge_disabledml_CBBF36366F884B97977FFE082ACD1981, Line 8
Table '[dbo].[Tb*****User]' into which you are trying to insert, update, or delete data is currently being upgraded or initialized for merge replication. On the publisher data modifications are disallowed until the upgrade completes and snapshot has successfully run. On subscriber data modifications are disallowed until the upgrade completes or the initial snapshot has been successfully applied and it has synchronized with the publisher.
I have a SQL Server instance called NLSQL06 and I'm replicating to another instance called NLSQL05. I'm only replicating 20 tables, most small, the biggest 3 tables have 6, 5 and 2 million rows, but not many records should be changing.
The distributor is also on NLSQL06 and the Subscriber on NLSQL05 is pulling.
Replication ran fine for a week or so, but now, after returning from the weekend I notice that replication is now critical and the Log Reader agent is not running. The Publisher-Distributor is working fine. The problem appears to be between the Distributor and the Subscriber.I can't figure out what is going on. Nothing is reporting any errors.
Any help appreciated. Thanks.
is it necessary to set the recovery model of the subscription-database (in a transactional replication) to Full for technical purposes?
Actually all my subscriptions running in "FULL" and i would like to change that as i think it will be also a performance increase...or am i wrong? Any ideas why i should left it on FULL?
I am using SQL 2008 r2.
I have production server on Location X which is transitionally replicated to a subscriber in locations Y.
The link between X and Y is not good to create snapshot or to transfer the backup of publisher.
I am tasked to create a backup infrastructure using one backup server in X and Y each. I need to write a script to restore the latest backup on of publisher in X to the backup server in X and latest backup of subscriber in Y to the backup subscriber in Y.
After that I need to configure the replication between the backup servers of x and y. Doing this, will give us an independent backup infrastructure (with few hours old data). Some discrepancy in the data is avoidable.
We take full-backup every weekend and differential-backup every evening. And we need to restore both.
When I looked at sp_addsubscription(), I found that it asks to restore the backup of Publisher to the subscriber which is not possible due to bad link between X and Y.
What will happen of I restore the backup of subscriber in Y to the backup server in Y? Can it create and problem with the running replication?
How would I restore both Full and Differential backup using sp_addsubscription() command?
Is there any way to manually restore the backups and then start replication without snapshot? As I mentioned earlier, minor discrepancy in data is avoidable.
And help or alternate idea will really help!!
(On SQL server 2012) I have to set up peer to peer replication on A/A cluster node(production to development and development to production ). Now the question is if data is coming from application server and inserting/updating a row on production. it will
mirror automatically on development too. but at that same time while doing this if both table is same on both server and which has a primary key then it will be conflict insert-insert or update-update or insert-update conflict. So, i want some automatic solution
for this. can please someone guide to solve this conflict?
Can someone please tell me the difference between Transactional Replication and AlwaysOn Replication? In layman terms...hopefully supporting Non-Microsoft Web sites...maybe the pros and cons of each... the benefits and liabilities of each...maybe a supporting YouTube that explains the differences...
Thanks in advance for your review and am hopeful for a reply.
we have a transaction database(A) and we want to load data from A into an ODS(B) environment this will be straight replica of A.
The purpose of ODS is for reporting(no Dataware house) and since we do not want to touch A due to transaction load we choose to have ODS as replica(same as A).
We thought of SSIS to get the delta data from the database A using CDC and it works fine. But I heard about Clustering(Always high availability) and I am still exploring the pros and cons so would appreciate if we get some suggestions or help.
We are using sql server 2016 and Azure. I am not able to find much details on 2016 version so though to take help with MSDN.
Suggestions/help is appreciated.
Thanks in advance