Articles on this Page
- 04/28/16--03:02: _The process could n...
- 04/27/16--14:11: _2014 Merger Replica...
- 04/21/13--17:15: _How do you drop a p...
- 05/01/16--06:19: _Database full and d...
- 05/03/16--02:02: _Merge Replication -...
- 05/05/16--03:27: _Reinitialize Subscr...
- 05/05/16--09:29: _Peer-Peer and Merg...
- 05/05/16--18:34: _Monitor SQL Server ...
- 05/06/16--14:09: _how to configure tr...
- 05/09/16--08:12: _Replication issue (...
- 05/10/16--08:03: _Merge replication -...
- 05/11/16--10:36: _does restore of dat...
- 04/20/12--05:35: _Goldend Gate Replic...
- 10/21/11--09:12: _sysmergesubscriptio...
- 05/12/16--08:34: _Invalid Descriptor ...
- 03/15/12--00:24: _Not able to add new...
- 05/13/16--08:21: _Orphan records in M...
- 05/16/16--10:41: _SQL server 2012 rep...
- 01/19/12--04:16: _SQL Server 2008 - R...
- 08/26/13--01:53: _SQL Server 2012 Mer...
- 04/27/16--14:11: 2014 Merger Replication not logging all conflicts
- 05/01/16--06:19: Database full and differential backups are same size ?
- 05/03/16--02:02: Merge Replication - Recover Data from tracked changes?
- 05/05/16--03:27: Reinitialize Subscription message
- Open the publication Properties (using SSMS 2008 R2)
- Expand the columns on <table>
- Tick the <column> box
- 05/05/16--09:29: Peer-Peer and Merge Replication
- 05/06/16--14:09: how to configure transactional replication latency warning?
- 05/09/16--08:12: Replication issue (Error converting data type nvarchar to numeric)
- 04/20/12--05:35: Goldend Gate Replication Issue
- 10/21/11--09:12: sysmergesubscription status values
- 05/12/16--08:34: Invalid Descriptor Index
- 05/13/16--08:21: Orphan records in MSarticles - How to remove them
- 05/16/16--10:41: SQL server 2012 replication -- transactional
I am having some problems configuring a replication. After the installation, once I tested via replication monitor, I got this errors:
The process could not connect to Subscriber 'CDBSRV01'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084)
Get help: http://help/MSSQL_REPL20084
Login failed for user 'CCV\EBSRV01$'. (Source: MSSQLServer, Error number: 18456)
Get help: http://help/18456
I am using a domain login to connect to the windows server and sql server.
Servers CDBSRV01 and EBSRV01 are connected to different networks, they are connected trough Cisco routers.
Also, there are two domain controllers on the domain each server belongs to one site.
Hi, I am looking for any assistance or ideas.
We have a merge replication set up between 2 offices. Pub-Sub client subscription, row level conflict checking with default resolver on all articles.
When Table A is updated in both databases and merge run it reports a conflict and publisher wins.
When Table B is updated in both databases and merge is run, the publisher wins but there is no conflict information logged in any merge conflict tables.
I've read all the articles I can find, I've checked all of the conflict table I know about, etc. There are no errors in the sql logs.
Any suggestions would be greatly appreciated.
I had two test databases on one server that I had been experimenting with for transactional replication. I wanted to delete the publication from one database and the subscription from the other and finally delete both databases. I deleted the publication, the subscription , the jobs related to them and finally the databases. I must confess that i wasn't as careful as I would be if I hadn't planned on just deleting everything. So what I have now is nothing appearing in SSMS under local publications or local subscriptions for these two test databases (but pubs and subs for other useful things) but in replication monitor the publication shows up with a red x.
I cannot use sp_droppublication @publication='my pub name' because the publication database is gone. Can I do anything to remove this publication from replication monitor? This isn't a production server yet it has some users who would be severely inconvenienced if I have to drop all replication and rebuild. Is there any other way?
Please find the below my backup strategy of 700 GB database
Every Sunday 9:30 PM full backup and from Monday to Saturday 11:00 PM differential backup . we observed the full and diff backup files are same size.(ldf file size only 10GB )
could you please suggest me , how to troubleshoot this issue
I'm looking for some advice about recovering data from a subscription database. I have a situation where we are using merge replication for several subscribers, and it appears as though for one of the subscribers the replication agent had not been running for a few months and therefore the changes at the subscriber were not being uploaded to the publisher. The subscription has then expired and been cleared off from the publication database and a new snapshot has been applied against the lapsed subscription.
Is it possible to recover the data which would have been updated at the subscriber prior to the new snapshot being applied? I was thinking this might be possible by looking at the msmerge_contents table and some of the other tables involved in tracking the changes, but could not see a way to do it; based on the number of records in this table on the subscriber it does not appear as though this has been overwritten. Unfortunately, there is not a backup of the subscription database available prior to the new snapshot being applied.
Any advice would be appreciated!
I have a replicated table (Transactional) where only a hand full of fields are replicated, I need to add another column and below is how I am adding the column, once I’ve ticked the box and clicked OK, I get the below message, please can someone explain what this means.
Steps to add column
You have changed one or more properties that require all subscriptions to be reinitialized.
Saving these changes marks each subscription that supports automatic reinitialization to be reinitialized
from the snapshot the next time its distribution agent runs. You must run the snapshot agent to generate the snapshot.
For subscriptions that were initialized manually when they were created: drop the subscription, reinitialialize the
subscription database manually, and create the subscription again.
Is it possible to Reinitialize Subscription in Peer-Peer and Merge Replication?
I get below request in my environment , please help me to create a replication latency job on server
- Create a table in TestDB database with name “test”
- Create a sql agent job that insert to this table from sp_helptracertokenhistory every 15 mins
- Create an alert that sends out email to when latency is higher than 15 secs. This can be part of the above job step.
Hi all ,
please help me to configure transnational replication latency warning step by step.
Getting below error message in synchronization history during synchronizing of subscription
Error converting data type nvarchar to numeric. (Source: MSSQLServer, Error number: 8114)
Get help: http://help/8114
for finding the exact issue, we have checked windows sql server event log and found something below:
[ Name] MSSQL$VERB1
- EventID 14151
[ Qualifiers] 49152
[ SystemTime] 2016-05-06T06:14:28.000000000Z
[ UserID] S-1-5-21-2320706869-2720452709-2089460225-500
Replication Merge Subsystem
Error converting data type nvarchar to numeric.
0000: 00003747 00000012 00000010 004F004C
0010: 002D004E 00420044 0030002D 005C0031
0020: 0045004E 00560052 00000038 0000000D
0030: 00690064 00740073 00690072 00750062
0040: 00690074 006E006F 0000
0000: 47 37 00 00 12 00 00 00 G7......
0008: 10 00 00 00 4C 00 4F 00 ....X.X.
0010: 4E 00 2D 00 44 00 42 00 X.-.D.B.
0018: 2D 00 30 00 31 00 5C 00 -.0.1.\.
0020: 4E 00 45 00 52 00 56 00 V.E.R.B.
0028: 38 00 00 00 0D 00 00 00 1.......
0030: 64 00 69 00 73 00 74 00 d.i.s.t.
0038: 72 00 69 00 62 00 75 00 r.i.b.u.
0040: 74 00 69 00 6F 00 6E 00 t.i.o.n.
0048: 00 00 ..
also we increased output verbose level higher (-OutputVerboseLevel 2) but we did not get anything in log
now unable to understand this sql server event log so please help me out if you have any suggestion
Thanks & Regards,
I need to reinitialize an replication without the option "Upload pending changes", and I have pending changes in the subscriber side which I don't want to lose.
Is there a way to detect this changes to generate the corresponding insert, delete and update scripts to be executed after the re-initialization process?
we run a job that copies a database backup file from server A and restores it to server B. Both servers are SQL 2014. this job runs twice daily.
we have configured replication on server B to do transactional replication of this database to an Azure SQL database.
here is my question: will the twice daily job to restore the database require any modification to the replication process, perhaps a snapshot regeneration or a subscription reinitialization? we are not touching the replication databases themselves,
just the database with info we wish to push to Azure SQL database.
I need your help in getting some information aboutGolden Gate SQL Server replication. Could you guys please help me in finding an answers on how a highly transactional sql server does with clustering and replication ? How long does it take to get replica online to users ? Is there any good reading material about Golden gate sql replication? Please help
What are statuses 5 and 7 in sysmergesubscriptions table (status field). We have several subscriptions with those values as their status but cannot find any mention of those values in BOL.
SQLState = S1002, NativeError = 0 Error = [Microsoft][SQL Server Native Client 10.0]Invalid Descriptor Index
I have searched around and all things point to my fmt file being out of sync with the data file and destination table but I cannot see that as the case thus far. I am posting the fmt file and table definition, and if anyone has any recommendations on troubleshooting this it would be greatly appreciated.
Things I have tried (rebuilding the fmt file each time) Removing the RowNumber Removing the first two bit fields (which do have defaults defined) Dropping and recreating the table
When I tried to insert the new field into the Microsoft Ax dynamics custtable(table name) it is not synchronizing while that particular table is configured for the transactional replication----- throwing the error as---> cannot execute the data definition language command on (). The sql database has issued an error.
And problems during the sql data dictionary synchronization.
In the event viewer the error description is as bellow.....
Object Server 02: The database reported (session 3 (Admin)): [Microsoft][SQL Native Client][SQL Server]Only members of the sysadmin fixed server role or
Db_owner fixed database role can perform this operation. Contact an administrator with sufficient
Permissions to perform this operation... The SQL statement was: "ALTER TABLE CUSTTABLE ADD FIELD1 NVARCHAR (10) NOT NULL DEFAULT ‘‘“
But the user, whose is logged in AX and trying to add a new field is having the full rights to SQL Server.
He is having sysadmin & db_ownerrights.
What could be the problem? How to resolve it?
When I run the following query:
SELECT msa.* FROM [distribution].dbo.MSarticles AS MSA LEFT OUTER JOIN [distribution].dbo.MSpublications AS MSP ON msp.publication_id = msa.publication_id WHERE msp.publication_id IS NULL
I have articles referencing publication which do not exist. How do I remove them?
Before anyone responds "use sp_droparticle", this requires a PublicationName which does not exist.
Before anyone responds "use sp_removedbreplication", tried that and did not remove these items.
I also dropped the published database, and the objects remain.
Any other ideas?
I created a new replication between SQL server 2012 standard edition and web edition, the publisher and distributor are on the SQL server 2012 standard edition, and I have to use SQL login to do push subscription to web edition SQL server and after re-initialization, the replication was successful for a few days and all the new transactions were successfully replicated to web edition SQL server. However, then all of sudden, I got following replication error from the publisher SQL server:
Date 2016-05-12 10:00:22 PM
Log Windows NT (Application)
User NT SERVICE\SQLSERVERAGENT
Replication-Replication Distribution Subsystem: agent W2012-DB-01-Paragon-Paragon_to_iWeb-CL-T054-473CN-42 failed. The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.
my questions are:
1. Which SQL server machine failed to create the temp folder?
2. Since I only be able to use SQL login to setup subscription on web edition, there is nothing really on web edition end; we checked the access permission on publisher / distributor end and the access permission has been setup properly.
3. On the other hand, all other replications setup have been working properly.
Thank you very much in advance.
Adding new articles (new tables) to replicate.
This is the process I followed which worked the last time I used it.
•Publisher (REPL_ISIS_APPS) --> Properties
•Click off ‘Show only checked articles in the list’
•Click on extra tables to add
•Click on OK
•Publisher (REPL_ISIS_APPS) --> View Snapshot Agent Status
•On View Snapshot Agent Status page click on Start
On the last step an error message is displayed.
Error message reads :-
The Agent could not be started
An exception occurred while executing a transaction-SQL statement or batch.
Could not find regular snapshot job for specified publication 'REPL_ISIS_APPS'.
Supply either @job_id or @job_name to identify the job.
Changed database context to 'ISIS'. (Microsoft SQL Server, Error 20678)
Q1) Does anyone know what caused this error?
Q2) Is there anyway to fix this error?
Q3) Would the option 'Reinitialize All Subscriptions' (with Use a new snapshot and generate the new snapshot now) correct this issue or make the issue worse?
At present all tables replicate (except the new ones I want to replicate) fine. What I don't want is to be in a situation where things stop replicating all together.
I have tried searching the internet for resolutions to this but I cannot seem to find this exact scenario.
Can you help?
In reference to http://dba.stackexchange.com/questions/29141/why-do-replication-deletes-require-sysadmin-access
I have the same issue as reported in the above link. The immediate issue has been bypassed in that I have granted ALTER TRACE permission to the main Applications account that does DELETE operations on the tables in question but in all honesty I don't want to grant that access just to bypass the error.
Msg 8189, Level 14, State 10,Procedure sp_repl_generateevent, Line 1 You do not have permission to run 'SP_TRACE_GENERATEEVENT'.
Has anyone else ran into this and come up with a better solution other than biting the bullet and giving all accounts that run DELETE operations on the merge Tables ALTER TRACE permission?
I could try some impersonation within the Replication Triggers to overcome this but of course if the replication is recreated then i would need to manually administrate the trigger code to manage the impersonation so that doesn't seem that practical to me.
Does this mean that its now a requirement for all accounts that run delete operations on Merge replication Tables to have Alter Trace Permission? o.O
Some advice would be greatly appreciated.