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

Unable to delete Peer-peer Node from topology of Server crashed

April 30, 2019, 6:09 am
$
0
0

HI Experts,

Need you suggestions , We had one SQL server crashed due to Storage and we had Peer-Peer with 4 nodes set,

As server is crashed we have to setup Server and create replication again, However now we have to remove the Crashed Node from Peer-Peer topology but we are unable to remove as Distribution & Publication doesnt exist and SSMS is being closed .

Need your inputs on how to delete the Peer-peer node or publication that doesnt exists in new server from Other Servers Peer-Peer topology.

Do we have any backup scripts to remove orphaned replication settings without impacting existing replication setup on other PRD Peer-peer nodes.

Thanks for time .

Thanks, Dev SQL DBA


↧
Search

Can't synchronize my subscription

April 30, 2019, 12:01 pm
$
0
0

Ok so I was able to establish the new subscription and set database permissions at the subscriber. However, when I went to view the subscription status I got a message:

TITLE: View Synchronization Status
------------------------------

The agent could not be started.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.0.2000.8&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=CantStartAgent&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

SQLServerAgent Error: Request to run job BCC-CH-DS01P-Ignition-HandAddsProductTrans-WIN-T6S43L3VKK9-3 (from User sa) refused because the job is already running from a request by Start Sequence 0.
Changed database context to 'Ignition'. (Microsoft SQL Server, Error: 22022)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.00.5000&EvtSrc=MSSQLServer&EvtID=22022&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

I received a similar message before and then I went into the publisher and enabled named pipes which was disabled there and enabled at the subscriber. After restarting the server I started synchronization and it seemed to have worked because a green loading icon was processing and then next time I checked synchronization status it said synchronization complete but however the same error persists. I've verfied the tcp/ip being enabled, both servers are running, browser is running for both, remote connection is verified for both, I can ping one to the other and vice versa. However, I don't understand how to troubleshoot via the powershell or what settings I should be looking for in firewall? I have not done anything in log file viewer it might be a possibility. I've also checked job history in the publlisher but don't know where to look everything just says job succeeded. Any Suggestions?

↧
↧

old snapshots not being deleted

May 1, 2019, 10:25 am
$
0
0

I have default retention period of >0 and <72hrs. The Agent account has full rights over the folder tree that the snapshots are stored in. 

SQL Server 2017
Server 2012 R2

↧

Removing node in Peer to Peer replication

May 1, 2019, 4:58 pm
$
0
0

We have 4 node peer to peer replication. DB1,DB2,DB3 and DB4.

Recently DB4 got crashed due to storage issues and not able recover the server.

Have to build the server DB4 from scratch. we are have installed new server with master, model and user database backup.

But we don't have backup of distribution database. 

When i try to remove the DB4 node from peers, it searching for distribution database on DB4 for dropping publication on DB4, In-fact we don't have distribution database SSMS is getting struck and SSMS is getting restart without removing DB4 node from Peer to Peer topology. 

Kindly suggest how can i remove this DB4 peer node without affecting other 3 peers nodes.

   

↧

Unable to create replication subscription in a different domain.

August 26, 2011, 7:49 am
$
0
0

Hi All,

I'm attempting to set up replication between two servers (both are SQL Server 2008 R2 EE) in two different domains, both of which are trusted, but am unable to do so as I receive the following error:

"Cannot connect to xxxxxx.

SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'xxxxxx'. (Replication.Utilities)"

If I put just the server name into the field and connect I receive the error stating that the server is not accessible since it's in another domain.

I'm able to connect to this server through SSMS on the publisher and am also able to browse the DBs on the server when specifying the server name and domain, yet am unable to proceed with setting up the subscription.

In searching for a solution I came across the following post, however when attempting to implement the proposed solution I still receive the same messages above:

http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/9a8cf6b1-a449-4748-b3c2-1c13e2bfcc5b/

Looks like I've hit a wall for the moment, any ideas?

↧
↧

Configure Cloud Witness

May 3, 2019, 1:00 pm
$
0
0

Hi,

I'm trying to configure a cloud witness for a SQL Server 2014 cluster. THe issue I'm having is that the "Configure a cloud witness" option is disabled in the Configure Cluster Quorum Witness wizard. How can I do this? Is there a way to enable that option?

Thanks! 

↧

Query - frequency

May 6, 2019, 12:33 pm
$
0
0
Could you please provide query to check transnational replication data frequency from publisher to subscriber.
↧

Change transactional replication from every 20 mins to continuous

May 6, 2019, 10:57 pm
$
0
0

Could you please help on below requirement.

how to change frequency of transactional replication from every 20 mins to continuous.

↧
Search

Add article

May 7, 2019, 1:07 pm
$
0
0
Can we add an article to the existing publication without generating a snapshot with all articles?
↧
↧

schedule frequency

May 7, 2019, 1:13 pm
$
0
0
how to know the schedule frequency of Transactional replication.
↧

SQL server 2016 peer to peer transactional replication error: The replication agent has not logged a progress message in 10 minutes

May 8, 2019, 8:00 am
$
0
0

Hi all,

I am running into this error on the SQL server 2016 developer edition. 

Set up: 4 nodes in a rectangular peer to peer replication topology, each node acting as a publisher as well as a distributor.

Error: on one of the nodes it is reporting:The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.

I followed the link below trying to resolve this issue but I believe I can rule out the possibility of "The agent cannot log in to one of the computers in the topology". However, according to the link another possible cause is that the agent is busy, in this case the agent is distribution agent since it is the one that is not responding. I have tried to restart the distribution agent and also added verbose logging. What I am seeing in the log is that distribution agent started initializing but never seems to finish as it is stuck at "agent waiting for Peer-to-Peer commands to apply". 

Since the node has two subscribers and only one is encountering this issue, I also added the logging on the healthy subscription and log leading up to the agent initializing are identical but the problematic one is just stuck at "agent waiting for peer-to-peer commands to apply". On the replication monitor I do see undistributed commands staying constant which means commands are not being applied. Then what is the distribution agent busy doing then? Any idea on how I can debug this further as I am completely lost and this peer to peer topology technology just seems way too unreliable. 

https://docs.microsoft.com/en-us/sql/relational-databases/replication/mssql-eng020554?view=sql-server-2016

Thank you for your help.

↧

SQL Server 2005 Replication: Job missing: Distribution clean up: distribution job

August 6, 2012, 12:42 am
$
0
0

I am reading on how to stop my distribution db from growing wildly, in doing this I find that there is a job I am supposed to have called:  Distribution clean up: distribution job

Is there any reason why I wouldn't have this in SQL SRVR 2005 STD?

How do I go about adding it in?

↧

Merge Replcation between SQL versions 10.5 and 14.0

May 9, 2019, 6:13 pm
$
0
0

Having successfully configured merge replication between a number of SQL version 12.0 SQL Express databases and a SQL 14.0 server, hosting the respective distributor databases, I have run into a problem with the final database (which is SQL Version 10.5). The first thing that I noticed was that when the SQL Express backup was restored to the SQL version 14.0 server, an upgrade process occurred, which I did not see when restoring restoring 12.0 databases.

The were no problems creating the merge publication but there was an error when attempting to create the subscription for the SQL version 10.0 database. When the Subscription Wizard attempted to connect to the subscriber database, the following error occurred.

Invalid object name 'sys.availability_group_listeners'. (Microsoft SQL Server, Error: 208)

The SSMS has no problem connecting to the SQL 10.5 database from the SQL 14.0 server, so I assume that this is not a basic connection error, but more related to something that the Subscription Wizard attempts to immediately after connecting.

I think that I probably need to upgrade the the SQL 10.5 SQLEXPRESS to at least SQL 12.0, but before I do that, I would like to see whether this is actually necessary.

R Campbell

↧
↧

distribution..MSreplservers table after SQL Server 2016 SP2 CU3 update

May 12, 2019, 9:36 pm
$
0
0

Hi Guys

We recently faced an issue with some of our customers where they were unable to install SQL Server replication properly through our software. We have a .NET based component which is used by our software to install SQL replication. Internally this component uses SQL queries / stored procedure calls to install the replication. The problem we noted with these customers is that out software was unable to detect the publication on these customer systems. To detect the publication, we use a SQL like the one below.

IF exists (select *from sys.databases where name ='distribution') 
select top 1 publication from distribution..MSpublications p, distribution..MSsubscriptions s, sys.servers 
where p.publication_id=s.publication_id and p.publisher_id=s.publisher_id 
and (server_id = s.publisher_id or server_id=s.subscriber_id) and name = '<<server name>>' and s.publisher_db like '<<database>>' 
ELSE Select 'NotExist'

This SQL is supposed to return the publication name for the database specified in <<database>> that has the <<server name>> as the publisher. This SQL does not work for these customers and does not return the publication name. After investigation we found that these customers are using SQL Server 2016 SP2 CU3 or higher. What breaks our SQL is the fact that the publisher_id column of distribution..MSpublications table no more matches with the expected server_id value of sys.servers. In earlier versions of SQL Server, the publisher_id used to match the server_id value that corresponds to the  sys.servers record for <<server name>> (i.e. the publisher SQL server). Instead, the the publisher_id now matches the server_id value that corresponds to the sys.servers record for repl_distributor.

With further investigation we can now see that the publisher_id column of distribution..MSpublications table now points to srvid of distribution..MSreplservers table. The srvid of distribution..MSreplservers table corresponds to the record for <<server name>> (i.e. the publisher SQL server). I can see some blog posts that suggest this is related to a distribution database in an Availability Group. However, we do not have any Availability Groups configured. I have tested this myself on a fresh SQL Server 2016 SP2 CU3 setup where no Availability Groups have been configured explicitly.

If we have an existing replication on SQL Server 2016 version earlier than SP2 CU3, and then we upgrade to SP2 CU3 (or higher), the distribution..MSreplservers table is still created during the upgrade. However, in this case the table has a srvid that matches the pre-upgrade publisher_id value. So our SQL continues to work in this case because the srvid has a value that matches our expected record in sys.servers.

The distribution..MSreplservers table does not exist in earlier versions of SQL Server 2016. I cannot find any Microsoft documentation that discusses the distribution..MSreplservers table. I also do not see any explanation as to why Microsoft decided to do such a change that could break existing implementations. I wonder if anyone here has any clues?

Thanks



↧

SQL Replication Error 17750

May 13, 2019, 3:28 am
$
0
0

Hi, I have been trying to create replication in SQL Server 2016 Standard, but getting below error 17750. Please let me know if any suggestions.

Error Message:
* Could not load the DLL xprepl.dll, or one of the DLLs it references. Reason: 2(The system cannot find the file specified). (Source: MSSQLServer, Error number : 17750) Get help: http://help/17750

*The merge process was unable to deliver to the Subscriber. if using Web Synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and Get help

Thankss,

Chandra

↧
Search

Merge replication table changes for on table

May 13, 2019, 11:50 pm
$
0
0

We using merge replication in our organasiation , we have 13 subscriber

I want to update lots of record for one table , but after update this replication have lots of record to upload and download .

we can use any other way , like snap shot for one table or anything , which not affect my replication ?

↧

MsMerge_genhistory has alot of rows with pubid = null

September 26, 2017, 7:44 am
$
0
0

I have a merge replication and I am worried that the cleanup of metadata might not be enough. I have a retention period of 60 days and I can see thet the metadatacleanup-job do remove rows i msmege_genhistory that are older but only for rows that has the right guid in pubid. most of the rows, about 1,6 million, has the value NULL in pubid and I cannot figure out why. does anybody know why there is so many null-values?

This is causing the stored procedure sp_msenumgenerations90 to be very slow and sometimes the whole system is locking.

↧
↧

Recreate Replication: easiest way?

May 16, 2019, 5:45 pm
$
0
0

I have two nodes, Node 1 is publisher/distributor, Node 2 is a subscriber.

They authenticate using an AD domain account between one another

Recently a catastrophic failure caused us to recover an Active Directory controller from prior to the date that the AD account used for this authentication existed.

Now, certain stored procedures on Node 1 which pull data from Node 2 fail with:

Msg 18456, Level 14, State 1, Line 10
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Attempting to sp_dropserver results in:

Msg 20584, Level 16, State 1, Procedure sp_MSrepl_check_server, Line 67 [Batch Start Line 137]
Cannot drop server 'Node2' because it is used as a Subscriber to remote Publisher 'Node1' in replication.

I have recreated the Login on Node2 using the new domain account. How can I update the "linked server" login account without breaking replication? Or if I do need to break replication, and rebuild it again, what's the easiest way to go about it without losing data on either node?

Very much appreciate any insight.

UPDATE: I discovered that replication is working and querying across servers works if I run the script while logged in using sql authentication. I tried recreating my own domain account login for SQL Server, tested that I can log in with that account on both servers. However, querying across servers still doesn't work.

Not sure why.

↧

SQL Server - Heterogeneous Replication

May 17, 2019, 5:20 am
$
0
0

Hi,

We currently have the below replication setup in SQL Server & it is working fine.

SQL Server 2008 R2 is both “Publisher” and “Distributor” too.

Oracle database 11g release 1 is “Subscriber”.

Now, when we try to make Oracle database 18c as “Subscriber”, SQL Server throws the below error message:

ORA-00932: inconsistent datatypes: expected FILE got BINARY (Source: <publisher name>, Error number: 932)

Get help: http://help/932

I assume we are getting this error because, SQL Server doesn’t have the datatype between Oracle18c & SQL Server.

I executed the below command... andI only see Oracle database mapping till 11g.

execsp_helpdatatypemap

@source_dbms=N'MSSQLSERVER',

@destination_dbms=N'ORACLE'

Can someone help me how to add Oracle database 18c mappings in SQL Server 2008 R2?


Many thanks in advance!


↧

What are the steps to follow to restore a previous replication when restoring to a previous release of my company's product

May 17, 2019, 6:42 am
$
0
0

    The company I work for has introduced the use of replication, I am in charge of executing multi-server databases on a distributed system. So far going forward with new releases, I have been able to set up replication with a publisher and subscriber on different servers. When the release is completed I backup the executable, along with the databases which includes distribution, master and msdb according to the docs I read from Microsoft about replication. 

     The problem occurs when I have to roll back to an older release. I perform restoration of databases on both db servers and restore the executable where needed. The databases for replication include the distribution (publisher server), master(as a single usr) and msdb. Master and MSDB are on both db servers. When I refresh replication I do see the publisher and subscriber names.  The question here is where do I go from here. I have not had much success after this point. Do I have to execute a snapshot? What are the steps from this point to restore the replication?

Thank you Pete

↧
Viewing all 4054 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>