Articles on this Page
- 08/17/18--09:29: _Error trying to rem...
- 08/20/18--08:20: _Replication from mu...
- 08/21/18--02:34: _The proxy auto-conf...
- 08/21/18--09:53: _SQL Replication Bat...
- 11/22/17--19:18: _How to Configure Re...
- 08/23/18--00:58: _SQL 2014 Listener
- 08/24/18--12:19: _Replication and Bac...
- 06/09/16--00:03: _The process could n...
- 08/27/18--19:24: _Replication listene...
- 08/28/18--07:42: _Alerts don't trigge...
- 08/28/18--11:53: _MSSQL_REPL-2147199402
- 08/29/18--05:03: _SQL replication wit...
- 08/29/18--23:12: _Replication- SQL jo...
- 08/30/18--12:47: _SnapShot Replicatio...
- 09/03/18--04:15: _Source for Replicat...
- 08/13/18--11:42: _sp_addarticle error...
- 07/18/12--13:46: _Log Shipping not wo...
- 03/27/08--07:16: _correct way to paus...
- 01/08/17--09:04: _Can not drop an Art...
- 09/06/18--09:35: _Retrieving data fro...
- 08/20/18--08:20: Replication from multiple servers to a centralized server
- 08/21/18--09:53: SQL Replication Batch File Encryption
- 08/23/18--00:58: SQL 2014 Listener
- 08/24/18--12:19: Replication and Backups
- 06/09/16--00:03: The process could not execute 'sp_MSadd_replcmds'
- 08/27/18--19:24: Replication listener redirect error in AG
- 08/28/18--07:42: Alerts don't trigger unless Replication Monitor is running?
- 08/28/18--11:53: MSSQL_REPL-2147199402
- 08/29/18--05:03: SQL replication with Databse Mirroring
- 08/29/18--23:12: Replication- SQL jobs owner
- 08/30/18--12:47: SnapShot Replication betweem two different domains
- 09/03/18--04:15: Source for Replication and our Sql admin Microsoft
- 03/27/08--07:16: correct way to pause transactional replication
- 01/08/17--09:04: Can not drop an Article from Peer to Peer Transactional Replication
- 09/06/18--09:35: Retrieving data from Distributor
Hello, here is my set up. I have server1 as a distributor, server2 is a publisher, server3 is a subscriber to server2 and server3 is acting as a publisher and distributor for other subscribers. I am trying to add a second linked server to a to server2
for server3 using a different name and login/security context for applications that use the data as the linked server set up for replication is not appropriate. I have set up another linked server on server2 to server3 using the ipaddress\instancename since
replication has set up a linked server using the servername\instance name. It is all working, but I dont like using the ipaddress\instancename approach and would like to try and use a more generic name to make the data access simpilier. When I try to run sp_dropserver
for the ipaddress\instancename, I get the above error which makes it appear I have used ipaddress\instancename in replication but did not. This linked server I am trying to remove was set up after I created the replication. I have seen some other posts similar
and the resolution is to drop replication and start over....
Anyone know what is going on here? How can I remove that linked server without going through and dropping/recreating replication? Also how can I rename or set the name of the ipaddress\instancename to a more friendly name. Thanks
Currently, our systems are having their own individual MSSQL databases in multiple locations(1 DB per server). We need to create a single consolidated DB with the same structure in a centralized location. In this schema, there should be a server identifier column in every table to identify the source of data and to maintain uniqueness across the data.
If we create an initial snapshot and then add the columns and modify the primary keys for tables, will setting up a transactional replication work in this scenario?
I'm a newbie in SQL, any help would be greatly appreciated.
I'm having trouble configuring a SQL 2008 R2 subscriber on an AWS EC2 server.
I must setup merge replication and subscribers at least once a week for the past couple of years without any issues, or at least ones I can usually find an answer for.
No matter what I've tried, including the IE settings turned off for Connections -> LAN Settings ->Automatically Detect and Use configuration script the error "The proxy auto-configuration url was not found" persists.
Placing the URL in the IE address allows me to get to "SQL Server WebSync ISAPI"
I also have other subscribers working happily with the same publisher.
Is there anything special about AWS that could be causing this? I've never had a server I couldn't configure.
Thanks in advance
At the moment when creating a batch file, we have to enter in the publisher username and password, we also do this for subscriptions. Obviously with the introduction of GDPR and general security practices this causes an issue.
Is there a way to encrypt text in the batch files? I have found a way to do this using a plugin via Notepad ++, however, I wanted to know if there is an alternative method?
I would like to setting up Transactional replication on a database which is part of basic AlwaysOn Availability Group with No readable secondary
Server 1 : AlwaysOn Availability Group Primary replica and transactional replication publisher
Server 2 : AlwaysOn Availability Group Primary replica and transactional replication publisher
Server 3 : replication subscriber and distributor
I received the error message (as below) when I EXEC sys.sp_validate_replica_hosts_as_publishers at distribution database:
Msg 21899, Level 11, State 1, Procedure sp_hadr_verify_subscribers_at_publisher, Line 109 [Batch Start Line 2]
The query at the redirected publisher 'Server 1' to determine whether there were sysserver entries for the subscribers of the original publisher 'Server 1' failed with error '976', error message 'Error 976, Level 14, State 1, Message: The target database, 'xxx', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online.'.
One or more publisher validation errors were encountered for replica host 'Server 1'.
Due to SQL Server edition limitation, readable secondary is not able to set to read-only or intended read.
Is it possible to Configure Replication for Always On Availability Groups in this scenario and how to setup.
From reading, the purpose of listener is for client to access databases in primary or secondary replica of an AlwaysOn availability group.
and without a listener, it does not has any effect/impact the AlwaysOn Database replication itself, is this correct?
Just want to get some clarification. As there is no listener set up on our AlwaysOn Database (synchronous replication), and without a listener, it does not actually stop replication from occurring, is this correct?
Running SQL Server 2008 R2 SP2. Server handles distributor and publisher roles for merge replication topology (endpoint subscribers replicate directly with this server). All system and user databases are set to full recovery mode. The database backups (type D in backupset table) are conducted once daily at 9:00 PM.
Based on the current scenario I have a few questions:
a) Because these are full database backups does that mean we have no options to shrink the transaction log? It is growing considerably and (my understanding is) we cannot shrink it because we're not doing log backups.
b) If we were faced with a recovery scenario (keeping in my the database is replicated), would it be as simple as restoring the publication and distribution databases and having subscribers sync? Or are there specific items we need to take into consideration when restoring a replicated database?
c) Would there be any advantage (or disadvantage) to take a full database backup once a week (say Sunday night) with a log backup the other 6 days? Would we achieve anything different using this strategy other than what we're currently getting?
d) Would there be any arguments for changing the recovery model of our databases?
Any help is greatly appreciated!
I'm trying to troubleshoot a transactional pull replication with a subscriber initialized from backup.
Log reader agent is failing with the following error:
2016-06-08 16:23:06.671 The agent is running. Use Replication Monitor to view the details of this agent session.
2016-06-08 16:23:06.679 Status: 0, code: 1007, text: 'The process could not execute 'sp_MSadd_replcmds' on 'SQLVMCI2\ISQL2012CI2'.'.
2016-06-08 16:23:06.679 The process could not execute 'sp_MSadd_replcmds' on 'SERVER\INSTANCE2'.
2016-06-08 16:23:06.679 Status: 0, code: 1007, text: 'Only members of the sysadmin fixed server role can perform this operation.'.
The windows account used to run the log reader agent is already member of the sysadmin role on the server hosting the pubblished database.
Publisher is SQL Server 2008R2 SE
Subcriber and distributor on the same machine are SQL Server 2012 SE
I've launched profiler (and selected all "error" category) but I see no error messages.
Any help is appreciated
One day suddenly all log reader agent went to stop completed successfully state with the error.
Error validating publisher
arithmetic overflow error converting expression to data type nvarchar
error were logged when validating the redirected publisher
my environment is 2016, I have AG and replication setup, use sp_redirect_publisher to add the listener however i got the above error recently and check the system table MSredirected_publishers which has column datatype as Sysname..
So wonder why did i hit this error, unfortunately since the log reader agent completed it did not throw re-try mail.. please shed some light
CREATE TABLE [dbo].[MSredirected_publishers](
[original_publisher] [sysname] NOT NULL,
[publisher_db] [sysname] NOT NULL,
[redirected_publisher] [sysname] NOT NULL
) ON [PRIMARY]
I have 2 servers: 1 is a publisher, the other is a distributor/subscriber, using transactional replication.
We are having regular failures in various publications that are easy enough to repair (just start the synchronisation job), but despite having configured and enabled all the predefined Alerts - it seems like they are only triggered when Replication Monitor is running.
What am I missing?
We are running SQL Server 2008r2 Service pack2. We are doing merge replication. On occasion I receive the error:
"The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the Subscriber. You must reinitialize the subscription (without upload). (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199402) "
What service pack or what version of SQL server is this bug fixed. The KB article: 2733630 and patch: cumulative-update-package-3-for-sql-server-2008-r2-sp2 address a similar error: MSSQL_REPL-2147199401, but it does not mention the error that I have.
Can we use SQL mirroring to replicate databases from a Cluster SQL servers to a standalone SQL server in a secondary site?
in our replication setup ,
some jobs running under one windowsuser account " domain1\ABC "
we are going to remove this account, so we need to change this to some other admin user. how to perform this , bcoz below repl-distribution running continuously,
shall i change it to job's property - owner parameter ? in wizard.
Snapshot agent jobs are unable to connect to the subscriber using the original name which is in the different domain. When I try to set up subscriber with FQDN I will get a warning as "FQDN or IP or not supported to set up". Please suggest me if anything needs to be fixed?
Hi everyone, I need a quick need to get a Replication Database way. It might be a quick guide ......
In the meantime, if you have a source for you, Sql Admin you can provide me
I am upgrading a server from SQL 2000 to 2008 r2 which is being replicated. The original replication set up had sql 2000, sql 2008 and sql 2014 and had set up had table a on publisher 1 (sql 2000) replicated to table a subscriber 1 (sql 2008 r2 in
8.0 compat), then subscriber 1 would publish table a to subscriber 2 (sql 2014). This was done due to the version requirements of replication. Now, I am upgrading publisher 1 from sql 2000 to sql 2008 r2 and subscriber 2 will subscribe directly from publisher
1 eliminating subscriber 1.
I have generated the replication scripts to recreate this and run into the above error 21830 noted above when I run the sp_addarticle for one of the tables. The problem is with the identity columns and the schema options. When I look at the schema options for publisher 1 it is set to 0x00000000000080A3, and when I look at schema options for subscriber 2 where I created the scripts it is set to 0x000000000803509F causing the error. My testing is restricted due to the fact that subscriber 2 (sql 2014) is not on our domain and I have no access to it. Looks like I need @identityrangemanagementoption set to 'none' but that is what is causing the error.
Can anyone offer a sugguestion here? Thanks
I'm trying to learn how to setup Log Shipping within two sql servers. I've backed up and restored the database I'm working with to the secondary server using Restore with standby, I then Enabled the log shipping configuration but it does not work. I'm seeing the following error on the SQL Server Agents log history:
"Executed as user: Domain\Username. The step failed"
My initial thought was that there is a security issue. The account running the SQL Server Agent doesn't have access to something. I verified that the account is an admin and has rights to the folder the transaction files should be saved it. I also checked to make sure the account is also a sysadmin in SQL and is a db owner for the database I'm working with.
Also, you should know that I'm working with a SharePoint content database.
Can anyone give me any help on why I'm getting this error.
We have Transactional replication running from ONE DB on our sql server 2000 box to a SQL Server off our network. While DR testing is going on, the Tunnel to the subscriber server will be down (FOR A COUPLE OF DAYS)
What is the best way to pause replication so I don't have a problem with logs filling up etc...
I stopped the log reader on the publisher... but I don't know if that was the right thing to do?????
I'm working with SQL Server 2014 and configure P2P Transactional Replication between two instances; So both of them are active for Insert,Update and Delete actions.
Now I want to do a simple action that is "drop an Article" from publication, but I can't!!!
From Management Studio i get this error:TITLE: Microsoft SQL Server Management Studio
Object reference not set to an instance of an object. (CreatePubWizard)
And by T-SQL:
@publication = N'pub1',
@article = N't1',
@force_invalidate_snapshot = 1;
I get this error:
Msg 14046, Level 16, State 1, Procedure sp_MSrepl_droparticle, Line 286 [Batch Start Line 1]
Could not drop article. A subscription exists on it.
I've tried to drop it on Instance 2, and again give me same errors, obviously because of the structure of this kind of Replication(That a DB is Publication on each server and is also Subscription at same time.)
I don't want to drop subscription and reconfigure my replication.
So, is there any solution?
SQL 2017 Developer 14.0.3037.1. Management Studio 17.9/14.0.17285.0
Created merge replication. Everything in replication works with no errors.
If I connect with Replication Monitor from PC2 (Subscriber) to PC1 (Publisher and also Distributor) Monitor on PC2 works perfect.
If I connect locally with Replication Monitor it stucks with message "Retrieving data from Distributor". No errors in logs. No errors in Profiler
Reinstalled server, reinstalled studio, updated server, updated studio, executed repair from installer, recreated distributor, recreated replication. Nothing helped. Both PC1 and PC2 have same servers and versions of Studio and send same queries (caught with Profiler)
When I press on PC1 Action => Distributor settings => Connection it throws exception:
TITLE: SQL Monitor
SQL Monitor encountered unexpected error. Do you want to continue?
Object reference not set to an instance of an object. (ReplicationMonitor)
at Microsoft.SqlServer.Management.UI.PublisherSettings.ChangeConnection(Boolean changePublisher)
at Microsoft.SqlServer.Management.UI.PublisherSettings.ChangeDistributorConnection(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Any tips how to fix this?