Quantcast
Channel: SQL Server Replication forum
Viewing all 4054 articles
Browse latest View live

The merge process could not connect to the Publisher 'Server:Reports'. Check to ensure that the server is running

$
0
0

Sql version:Microsoft SQL Server 2008 R2 Replication type: Merge

Getting Below error in 'View Synchronization Status' window.

The merge process could not connect to the Publisher 'Server:Reports'. Check to ensure that the server is running.

Though Replication is working Fine as i can see records are replicating successfully from publisher to subscriber. User Permissions looks all good as i have provided db_owner roles. What else i can check?

Any assistance/thoughts would be most welcome


Does Golden Gate support SQL ALways ON

$
0
0
I am planning to setup replication b/w SQL to SQL by using Golden Gate. Does Golden Gate support SQL Always ON? My source server has SQL Always on

tx replication issues

$
0
0

Hello,

I am using SQL Server 2012 SE and implemented tx replication with one publisher and 2 subscribers(server A to Server B and Server A to Server C). It had been running fine for the past 6 months but this morning I noticed that data from publisher is not being pushed to distributors.

The errors in replication monitor (Publisher to Distributor history tab)  show:

Agent 'ServerA-databasename-2' is retrying after an error. 100 retries attempted.

The process couldnot execute sp_replcmds on 'Server A'

The process is running and is waiting for a response from the server

The log Reader Agent shows:

The replication agent encountered an error and is set to restart within the job step retry interval. 

2016-07-17 12:45:31.532 Status: 4096, code: 20024, text: 'Initializing'.
2016-07-17 12:45:31.532 The agent is running. Use Replication Monitor to view the details of this agent session.
2016-07-17 13:15:31.581 Status: 2, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'Server A'.'.
2016-07-17 13:15:31.581 The process could not execute 'sp_replcmds' on 'SERVER A'.
2016-07-17 13:15:31.581 Status: 2, code: 0, text: 'Query timeout expired'.
2016-07-17 13:15:31.581 Status: 2, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'SERVER A'.'.
2016-07-17 13:15:31.643 The agent failed with a 'Retry' status. Try to run the agent at a later time.

Also this filled out the trnasaction log of the database and it is sitting at 150GB compared to 15GB everyday.

Any ideas whats causing the timeout?

Thanks a ton

Error 3931 when running sp_addpullsubscription_agent where Distributor security account is a domain account

$
0
0

Hi all,

Upon removing and re-adding replication from a production system at the weekend, we encountered the following error when executing sp_addpullsubscription_agent:

Msg 3930, Level 16, State 1, Procedure sp_grant_login_to_proxy, Line 70
The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
Msg 3931, Level 16, State 1, Procedure sp_MSrepladdproxyaccount, Line 129
The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.

The specifics of our configuration are:

- SQL Server 2012, SP3
- Transactional replication
- Pull subscription
- Dedicated Distribution SQL Server
- Log Reader Agent and Distribution Agent to run as a dedicated domain user account which is a local Admin on the Distribution server and Subscriber server (which is where DISTRIB.EXE is running)

The only way we could get around this error was to create the pull subscription specifying that it runs under the SQL Server Agent account.

However, this is not our standard or preferred configuration.  It is not how we run in other domains where everything is the same as this one where we've just experienced this new problem.  And we successfully did the equivalent replication removal and re-creation work in those other domains the previous week.  
We have installed SP3 of sql server 2012 since the last replication removal and re-creation in the affected domain.  However, the same is true of the other domains where the error isn't prevalent.

Has anybody else experienced this please?  Is it perhaps a bug manifested in very specific circumstances but something that can be worked around by changing the properties of the Distribution Agent job step in place?  

Many thanks.

J

metadata cleanup has deleted metadata... With 2008 R2 all updates

$
0
0

I have the issue of this link with Web Sync:

https://support.microsoft.com/en-us/kb/2733630

But my versions are later than cu:

Publisher: 
Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)   Aug 19 2014 12:21:34   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Subscriber: 
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4042.0 (X64)   Mar 26 2015 21:18:04   Copyright (c) Microsoft Corporation  Express Edition with Advanced Services (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)  

So I can´t install CU3  for SQL Server 2008 R2 Sp 2 in Subscriber, getting this message (is in Spanish but easy to understand):

"Ya se ha instalado una actualización de SQL Server de una versión superior en la instancia de SQL Server SQLEXPRESS, por lo que la actualización actual de SQL Server no se puede aplicar. La versión de la actualización de SQL Server que ya está instalada es GDR 10.52.4042.0(10.52.4339.0) con KBKB3045313, y la actualización actual de SQL Server es 10.52.4266.0 con KBKB2754552."

I have checked metadata tables and the problem is that randomly the last send generation of changes stops to update. Then the sync start to send the same old changes one time and another and when the expiration time pass I get the error. I reinitialize the subscriber and everything goes ok until the last send generation of changes stops to update again.

I have a publication with 13 subscriber and all of them have got the error one time at least.

So I don´t know what to do.

Thanks,

Luis.




sp_droppullsubscription

$
0
0

I am having an issue dropping a pull subscription on a subscriber. I tried using the UI without connecting to the publisher as well as running thesp_droppullsubscription command. The error I am getting is:

Msg 3930, Level 16, State 1, Procedure sp_droppullsubscription, Line 375

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.

It's a snapshot subscription. The publisher is SQL 2008 R1 SP1 and the scriber is SQL 2008 R1 SP2. I was able to delete the subscription from the publisher. I can not upgrade the publisher at this point.

 

XML parsing: line 1, character 38, unable to switch the encoding

How to continue restoring transactional logs without restore recent .bak file

$
0
0

Hi Team,

Hope doing well.

I have primary server, from that I am taking database backup and transactional logs. At the very first time restored database backup file into the secondary database. Later continuing restoring transactional log files continuously from primary server to the secondary server, going very good.

in mid we have taken database back(.Bak) from primary server ( we don't want restore recent database backup file into the secondary).But we should continue restore logging to the secondary. I am not able to restore the transactional files into the secondary server without restoring recent Bak file.

Requesting please help me on this.

Thanks in advance.

Regards,

Muni



ident_current issue

$
0
0

HI All,

I am using replication for sql server 2008. I noticed that ident_current and ID of latest inserted entry of replicated tables are different. for example: Suppose i have a table Employee so output of the below queries are different:

select top 1 * from Employee order by Employee_id desc  gives me 4004049

and select ident_current('Employee') gives 15503398

whereas both queries should return either the same value or ident_current value should be greater than last identity id of Employee table.

I am getting "Identity insert issue" due to above scenario . I got it why it's coming because 15503398 is lesser than 4004049 and already exists into db .

We can manually  reseed it using DBCC CHECKIDENT('Employee', RESEED, 4004049 ) but that's not the proper solution.

Please advise if we can stop occurring this or we can do some settings into replication so that value of ident_current would be same or greater than last identity id of Employee table.

Thanks in advance. Any help would be appreciated


Troubles with replcation for special characters to Oracle

$
0
0

Hello,

We are replicating some tables to our websitedatabase. Al our internally DB are SQL Server, our webapp is build on a oracle.

Wgen replication tables that contain varchar's with special charaters such as é ö it goes 100% correct with the initial snapshot (and then bulk insert i supose), but when we update a record (even on a other field) the varchar contains wrong characters ....

Any ideas on how to work arround this ?

Disk Space Loss and Publication Snapshot Job Questions

$
0
0

I have a server running SQL Server 2012 with a transaction replication a large database (500gb). I have noticed over time that my disk space have been slowly shrinking. I have increased disk space but I am not sure what to do about how to slow down the disk space loss. Does anyone have any suggestions or recommendation for this?

I have noticed that the publication snapshot regenerates every hour. I thought that in transactional replication, it generated a snapshot once and relied on the logs. What effect will reducing the amount of times a day the publication snapshot regenerates?  How about stopping the snapshot job from regenerating?  Thanks.

Question on Subscribing only few columns

$
0
0

I have Transactional replication in SQL Server 2014 which is running fine , no issues found as of now.

Replication Topology:

Publisher 1 with 10 tables -----> Subscriber ABC

Publisher 1 with 10 tables -----> Subscriber XYZ

now, out of 10 tables which involved in replication, i have a table with CC number column(NOT ENCRYPTED)  and i am ok to replicate CC data to Subscriber ABC

but i do not want to replicate CC data column to XYZ.

how can do this? 

I am aware of taking out entire table  in Publication but never did the scenario above..

can someone help me providing some info?

Thanks

could not find stored procedure 'sp_MSupd_dbotbl***'. (source mssqlserver error number 2812)

$
0
0

Hi

Recently, I Created replication 2012(alresdy have 2000) and sometimes recived brlow error:

could not find stored procedure 'sp_MSupd_dbotbl***'. (source mssqlserver error number 2812) and I have to created manually.

I searched and saw about below SP but should i run this where? in publisher db or subscriber

sp_scriptpublicationcustomprocs [ @publication = ] 'publication_name' 

How to create the batch file for the Snapshot replication on the publication and subscription side .

$
0
0

Hi there,

I found the batch script for merge replication as below to create the initial snapshot script and also the batch file to activate subscription. But however i didn't get any for Snapshot replication.

Could you please help?

Following is what I got for merge replication.

The following command-line arguments start the Snapshot Agent to generate the snapshot for a merge publication.

REM -- Declare variables
SET Publisher=%InstanceName%
SET PublicationDB=AdventureWorks2012
SET Publication=AdvWorksSalesOrdersMerge

REM --Start the Snapshot Agent to generate the snapshot for AdvWorksSalesOrdersMerge.
"C:\Program Files\Microsoft SQL Server\120\COM\SNAPSHOT.EXE" -Publication %Publication%
-Publisher %Publisher% -Distributor %Publisher% -PublisherDB %PublicationDB%
-ReplicationType 2 -OutputVerboseLevel 1 -DistributorSecurityMode 1  

Scenario: Publication Database is on MSSQL 2012 Standard 

Subscription Databse is on SQL EXpress 2012

Replication between remote sites

$
0
0

Greetings

We are planning to create replication/mirroring between two database servers for an existing database.

We did a scenario but it seems it never works

- Took a backup of the existing database from the Publisher

- Restored the backup on the subscriber side

- Started the merge replication between both servers

what we expected is a comparison will occur between the restored backup and the snapshot however the publisher started to push the whole records without verifying if it's exists on the subscriber side or not

Is there anything missing ?  


need help with sync_type = 'replication support only'

$
0
0

Hi,

On certain tables in a PUB, we do not replicate the deletes so there is more data on the SUB. On these tables we use sync_type  = ‘replication support only’ but, doesn’t that mean that any changes made at the PUB will remain there? How do they get over to the SUB?


TheWheel


MSSQL Server : TCP Provider: The specified network name is no longer available

$
0
0

When i Run a store Procedure (which pulls data from another server) returns this Error:

OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "Unspecified error".
OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "Communication link failure".
OLE DB provider "SQLNCLI10" for linked server "(null)" returned message "Communication link failure".
Msg 64, Level 16, State 1, Line 0
TCP Provider: The specified network name is no longer available.

Can anyone Help me... ?

SQLSERVER 2008 R2 (BOTH)


Is this possible to add distribution database into always on availability group ?

$
0
0
as per my understanding/reading  distribution DB is not a part of Availability group, just to confirm i want to ask can we do this?

Replication - requiring logging in to the server with the Server Name instead of IP Address

$
0
0

I am in the Office, SSMS is in the office - I mean office subnet.

The production machine(s) are in the data center, accessible only via VPN.  Currently, I do not have O/S Server level (via RDS) access to the remote database server.  No access to SQL Server Configuration

Unfortunately, I can only login to the remote SQL servers via VPN - IP only. 

Publication is done from the Principal server.  But I cannot do the subscriptions via GUI and/or cannot Script Out subscriptions from another set of servers ... just because I cannot login with the name to the Repl Subs server or to another Repl Subs server which has identical repl scenario, but cannot script out the Subscriptions.

Help!!!  Is there a workaround from within SQL Server even with the sa privlidges.

Duplicate Primary Key When Merge Database

$
0
0

I very new in SQL Server. Now, I am stuck with a problem.

i need to merge 2 DB with identical structure, but i still stuck in duplicate primary key,, in my mind is i wanna change primary key one DB with increment id start from 5000 we can say DB 1 and let DB 2 no change (DB 2 increment id from 1 until 1000) Or set PK DB 1 as odd (1,3,5,7) and set PK as even (2,4,6,8), and then merge them with generate script

I need to change the primary key on a table with lots of data, about 10000 rows. Some other tables have relationship with this table (FK), but some tables stand alone.

I have browsing in google but still no luck.

Can someone in here give me solution.

Thanks..

Viewing all 4054 articles
Browse latest View live




Latest Images