Articles on this Page
- 10/19/16--03:33: _Error ID: 26050
- 10/20/16--00:39: _Who delete the publ...
- 12/10/12--02:42: _Transactional Repli...
- 10/20/16--08:31: _Replicate non Prima...
- 10/20/16--13:26: _student
- 10/24/16--04:29: _Foreign key being d...
- 10/26/16--04:21: _Exploring Allways E...
- 10/26/16--16:57: _Replication issue
- 10/25/16--22:34: _SQL VSS writer is n...
- 01/24/12--16:57: _The process is runn...
- 10/27/16--03:53: _Transactional repli...
- 10/26/16--23:49: _Linked Server Estab...
- 10/26/16--04:36: _SQL Server Replicat...
- 10/27/16--13:01: _Tranactional replic...
- 10/27/16--10:41: _Replication over a ...
- 10/31/16--11:37: _Cannot shrink the l...
- 10/31/16--15:09: _Replication: Gettin...
- 11/01/16--04:38: _Replication between...
- 11/02/16--10:01: _T-log on subscriber...
- 11/02/16--17:12: _SQL Server Replicat...
- 10/19/16--03:33: Error ID: 26050
- 10/20/16--00:39: Who delete the publication?
- 12/10/12--02:42: Transactional Replication: Non-Clustered Indexes not copying.
- 10/20/16--08:31: Replicate non Primary key columns
- 10/20/16--13:26: student
- 10/24/16--04:29: Foreign key being deleted
- 10/26/16--04:21: Exploring Allways Encryption in 2016 Ent Edition
- 10/26/16--16:57: Replication issue
- 01/24/12--16:57: The process is running and waiting for a response from the server
- 10/27/16--03:53: Transactional replication - undistributed commands
- 10/26/16--23:49: Linked Server Establishment from sql 2012 to sql 2005
- 10/26/16--04:36: SQL Server Replication Issue
- 10/27/16--13:01: Tranactional replication
- 10/27/16--10:41: Replication over a one-way VPN
- 11/01/16--04:38: Replication between remote sites
- 11/02/16--10:01: T-log on subscriber database
Can you please help with this following issue.
Recently I had worked with replications but I did not found any error while working with replications. Is this error related to replications?
Today morning I received the following alert:
DESCRIPTION:Replication-Replication Distribution Subsystem: agent (null) failed. The publication 'XYZ_XYZ_XYZ' does not exist.
I've expanded the publication node where that publication should be, and yes it is not there.
how can I know when and who deleted that publication? is this information stored in Default Trace? if yes then I tried the following but with no luck... how can I found who?!
DECLARE @FileName NVARCHAR(260) SELECT @FileName = SUBSTRING(path, 0, LEN(path) - CHARINDEX('\', REVERSE(path)) + 1)+ '\Log.trc' FROM sys.traces WHERE is_default = 1 ; SELECT loginname , hostname , applicationname , databasename , objectName , starttime , e.name AS EventName , databaseid FROM sys.fn_trace_gettable(@FileName, DEFAULT) AS gt INNER JOIN sys.trace_events e ON gt.EventClass = e.trace_event_id where starttime >'2016-10-18'
I set up replication on our servers at work to streamline some procedures we run daily/weekly on them.
This copies around 15 articles from two databases on the "Master" server to another server used for execution purposes. For the most part it was a pretty straight forward task and it seemed to work nicely; but I realised after some investigation that the non-clustered indexes weren't copying over to the child server.
I set the non-clustered indexes property in the properties of the publishing articles to "True" and generated a new snapshot, this seemed to work, but I've come into work this morning to find the property has reset to "False" and I have no indexes on the table again. Why is this happening and is there any way I can resolve the matter so the indexes are copied over concurrently?
Thanks in advance for your advice.
Hi Experts, I need a small suggestion on how to replicate non PK columns, below is my scenario.
Server1, db1, 10 tables with PK used Transactional Replication To replicate Server2, db1--All good and happy
Server1, db1, 5 tables without PK Scheduled to run every 1 hour snapshot Replication To replicate Server2, db1, when i do this
all tables involved in Snapshot gets LOCKED to prevent any further Changes and that causing issues on Server1, db1 on 5 tables without PK , so had to drop that option
I thought of doing log shipping, Mirroring, not a good option for always on for 5 tables but none helping as i want Server2, db1 all tables for reporting purpose.
I am thinking of scheduling a JOB(ssis) on Server1 to truncate data of NON PK tables (5) on Server2 and then insert every 1 hour, but that also could block reporting users,
my question is how should i achieve this without blocking everyone , also can someone please provide a tip how to push data to server2, db1, any 5 tables if there is any change found in Server1,db1, in any 5 tables ?
Thanks for the help
can some one help this order is correct or not, if not please give me a correct order? - configure a replication between 2 servers sv1 and sv2. THANK YOU!
1. configure sv1 is distrubutor
2. configure sv1 is publisher
3. configure a publications of db1 on sv1
4. configure a subscription of db1 on sv2
I found a strange behavior in Transaction Replication. After the synchronization, one of my foreign keys is being deleted.
That situation happens with the follow sample:
CREATE TABLE [dbo].[Table1] ( [ColumnA] BIGINT NOT NULL, [ColumnB] BIGINT NOT NULL, [ColumnC] INT CONSTRAINT [DF_Table1_ColumnB] DEFAULT ((0)) NOT NULL, CONSTRAINT [PK_Table1] PRIMARY KEY CLUSTERED ([ColumnA] ASC) ); GO CREATE UNIQUE NONCLUSTERED INDEX [UQ_Table1_ColumnC_ColumnB] ON [dbo].[Table1]([ColumnC] ASC, [ColumnB] ASC) INCLUDE([ColumnA]); GO CREATE TABLE [dbo].[Table2] ( [ColumnX] INT IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL, --Subscriber: [ColumnX] INT NOT NULL, [ColumnY] BIGINT NOT NULL, [ColumnZ] INT NOT NULL, CONSTRAINT [PK_Table2] PRIMARY KEY CLUSTERED ([ColumnX] ASC), CONSTRAINT [FK_Table2_Table1] FOREIGN KEY ([ColumnZ], [ColumnY]) REFERENCES [dbo].[Table1] ([ColumnC], [ColumnB]) ); GO
The foreign key being deleted is FK_Table2_Table1.
Did anyone experience something similar? If yes, what's the reason?
I am exploring 2016 sql ent edition , Allways Encryption feature .
Case 1: how to adopt allways encryption feature on my existing DB , whose size is of 10 GB with 200 Tables and each tables varies from few min 1 MB to 900 MB.
Case 2: Create a new DB and adopt this technology
Can you please help me to understand how it works? and how to use test it/use it.
Can you please share me some simple WEblinks which explains me in detail
While I am setting up replication,my snapshot agent after it completes bulk copy its giving me below error
"Message: Conflicting locking hints are specified for table "dbo.employee". This may be caused by a conflicting hint specified for a view.
Command Text: SELECT TOP 1 0 FROM [dbo].[oemployeereplication] WITH (TABLOCK, HOLDLOCK)
Stack: at Microsoft.SqlServer.Replication.AgentCore.ReMapSqlException(SqlException e, SqlCommand command)
at Microsoft.SqlServer.Replication.AgentCore.AgentExecuteNonQuery(SqlCommand command, Int32 queryTimeout)
at Microsoft.SqlServer.Replication.AgentCore.ExecuteDiscardResults(CommandSetupDelegate commandSetupDelegate, Int32 queryTimeout)
I am doing replication from Indexed view as publisher and table as subscriber.
I have a problem need your advise please,
VSS SQL Writer does not appear on the following command :
vssadmin list writersas I know VSS SQL writer must be listed there, because I am getting a warning message during a replication job
any reply or help would be highly appreciated
I have tried to reinitialize a replication job a number of times and it keeps failing in the same place on the same table during the bulk upload (141919 rows). The Publication is coming from a SQL 2008 sever to two Subscribers a SQL 2005 and a SQL 2008. The SQL 2005 subscriber was able to synchronies however the SQL 2008 server was not.
The error I am getting is "The Process is Running and is waiting for a response form the server".
Based on some recommendations I saw I increased the Agent Profiles Query Timeout to 9000 and LoginTimeout to 90. Still no luck. I have restarted the SQL services on the Subscriber and reinitialized from a new snapshot, same problem.
Where do I go from here?
I checked MSrepl_Errors and there are no errors from the time I started until the time I had the issue
I have checked for deadlocks with the deadlock script and there seems to be none.
We have a problem in Transactional replication.
The problem is that I have mismatch number of rows between the publisher and the subscription.
We have Transactional replication in SQL2012 Enterprise edition SP3
Publication – Standalone server
Subscription – AlwaysOn server (Push)
Distribution – 3<sup>rd</sup> server Standalone
The Publisher/Subscriber combination have several publication that all work fine except 1.
The problematic publication has one table.
The table hasa column with XML Data type, size – 260GB, 5.5 Millions rows.
The data is notbeing replicated to the subscriber,
Undistributed commands show 919382 and counting
I think the problem probably in the distribution server.
The repl process try to exec sys.sp_MSget_repl_commands;1 and wait for PREEMPTIVE_OS_WAITFORSINGLEOBJEC. I found that by using sp_whoisactive.
We get error message in distribution job:
Raised events that occur when an agent’s reader thread waits longer than the agent's -messageinterval time. (By default, the time is 60 seconds.) If you notice State 2 events that are recorded for an agent, this indicates that the agent is taking a long time to write changes to the destination.
In addition thereare no database locks
Please advise how to solve the problem
Thanks & Regards
Can you please help me to establish the link server between sql server 2012 std edition to sql server 2005 please.
Expecting the steps to establish.
I tried , but end up with error.
The steps i tried is
log in to sql server 2012 ( source ) and in the SSMS, expand the server objects + Linked Server
2. right click on the linked server and select new link server, which will prompt us with new wizard, in which we need to enter the name
3. i have given the name of the link server, same as my destination instance name . and under that we have ser ver type of 2 radio buttons a. SQL server b. Other DataTypes, in whcih i have choosen SQL Server as my destiantion serv er is also SQL
4. choosen security tab on the left side of the wizard , i had given my log in id only in local login , remote user, remote password category
5. clicked the final OK button , but end up with error .
Please correct me if i am wrong.
A few days ago I came across the following error:
The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\100\COM' directory. System returned errorcode 5. (Source: MSSQL_REPL, Error number: MSSQL_REPL21100) Get help: http://help/MSSQL_REPL21100
I resolved the issue by granting the SQL Service and agent accounts full permissions on the above folder. My question is, what could have caused this to fail? It been running perfectly for months and then suddenly replication failed and I saw the above error. Could it be a case of someone removing the permissions from the folder? I've checked the replication job owner etc. and nothing has been changed. Any suggestions to what could have caused this?
Thanks in advance.
Can we Configure Tranactional replication without Primary Key Tables .
I have two SQL Server 2012 machines in two different domains. Server A can communicate with Server B over a VPN. This VPN is one way, that is port 1433 is open from server A to Server B but not the other way.
I have tried to set up Transactional Replication with Server A as the Distributor/Publisher. This seems to work but when I go to Server B to create the Subscriber, I get the following error message:
"The selected Subscriber does not satisfy the minimum version compatibility level of the selected publication."
Server A is a SQL 2008 Express updated to SQL 2012 Developer. Server B is SQL 2016 Developer. I use SSMS version 2014 on both servers. I have set the database Compatibility Level to 110 for both the source and target databases.
I thought this might be due to the one-way VPN. So I also tried Log Shipping. This does not seem to work either. Are my problems due to this one-way VPN? If so, I just want to get a copy of the database on Server A copied to server B. I don't want to do this manually so is there another way I should look at?
We have done the following. And we still cannot shrink the log and the log_reuse_wait_desc still reads REPLICATION. I told taking the database out of the AAG is not an option and changing the recovery mode to SIMPLE is also not an option. What else can we try?
Processed 19949278 pages for database 'ldm_carepoints', file 'ldm_Log' on file 1.
The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure the Log Reader Agent or capture job is running or use sp_repldone to mark transactions as distributed or captured.
BACKUP LOG successfully processed 19949278 pages in 984.803 seconds (158.258 MB/sec).
EXECsp_repldone@xactid=NULL, @xact_segno=NULL, @numtrans= 0,@time = 0, @reset = 1
Msg 18757, Level 16, State 1, Procedure sp_repldone, Line 1
Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
select name, log_reuse_wait_desc, is_cdc_enabledfromsys.databases
name log_reuse_wait_desc is_cdc_enabled
ldm_carepoints REPLICATION 0
I have set up replication between a SQL 2012 and a SQL 2016 server. On the 2016 Server in SSMS when I right click on the Local Subscription I get the error below. Does anyone know how to correct this? I am logged in with a domain account that is admin on the server and sysadmin in the database.
Cannot apply value 'null' to property ServerInstance: Value cannot be null
We have a Database and web application hosted in our office in Middle East, and we have 2 more sites in Philippines and USA.
Both offices in Philippines and USA are using the same hosted Web Application and SQL Server in Middle East but we face much latency between Philippines and Middle East due to Internet Speed.
We tried to run Merge Replication between Middle East and Philippines however it took very long time to copy the snapshot from Middle East to PHL.
Our Database Size is around 1.5 TB and we don't have any idea how we can resolve this situation we have now, putting into consideration that we need on the spot update between both Sites as users might be working on the same data at the same time
Any Clue ?
I am new to SQL Server management and have been tasked with maintaining transactional replication for disaster recovery. The publisher is on one server, with the distributor and subscriber on a separate server. The subscription is set up as pull. I have full backups of all databases, including distributor, master and msdb, scheduled daily and transaction log backups scheduled hourly. This is on both servers. All subscription databases have full recovery model. What I have noticed is the log file on the subscriber databases does not seem to be truncating with the regular transaction log backups. I have been reading about 'issyncwithbackup' but I cannot tell if that will help with this problem or not. While I expect we would simply roll over to the subscriber database in the event the publisher became unavailable, I am not certain we would not need point in time recovery. So I do not know that switching to simple recovery is an option, or even advisable. Any suggestions would be appreciated! Also, I am struggling to find a good resource for more complex replication questions, like this one. Any suggested sites or reading would also be appreciated!
We have 3 SQL servers running SQL Server 2008 R2. There is a primary server that has bi-directional synchronization with two child servers. Our alerting is set up to alert on A. replication connection issues and B. long running merges that last more than 5 minutes. The problem is that the long running merges are not generating Windows events and thus not alerting. When someone connects via SQL Management Studio, opens Replication Monitor, and expands the publication the events are generated and alerts begin firing.
Is this expected behavior and if not what settings can I check for issues?