Articles on this Page
- 07/17/14--11:51: _Replicated db & SSRS
- 07/16/14--22:22: _Restore merge filte...
- 07/18/14--07:04: _The merge process c...
- 07/18/14--10:23: _SQL Replication Met...
- 07/19/14--01:46: _unable to drop publ...
- 07/19/14--06:32: _Transactional Repli...
- 07/21/14--02:17: _Hyper-V Replica - S...
- 07/22/14--02:26: _Transactional repli...
- 07/21/14--06:44: _Replication between...
- 07/22/14--06:02: _merge table indexes...
- 07/21/14--00:04: _Very slow SQL Serve...
- 07/22/14--02:37: _Index Taking Longer...
- 07/24/14--08:22: _Issues synchronizin...
- 07/24/14--07:22: _Noncovergence in tr...
- 11/29/06--09:52: _Merge Replication C...
- 07/27/14--17:05: _Replication with Al...
- 07/28/14--22:17: _SQL Replication in ...
- 07/30/14--19:39: _Replicate encrypted...
- 07/31/14--10:01: _Migrate SQL Server ...
- 08/01/14--08:53: _Configure overwrite
- 07/17/14--11:51: Replicated db & SSRS
- 07/16/14--22:22: Restore merge filtered replication without initialize
- 07/18/14--07:04: The merge process could not allocate memory for an operation;
- 07/18/14--10:23: SQL Replication Metadata for when subscription became inactive
- 07/21/14--02:17: Hyper-V Replica - SQL 2000 & 16-bit application
- 07/22/14--02:26: Transactional replication issue
- 07/21/14--06:44: Replication between two different domains
- 07/22/14--06:02: merge table indexes fill factor
- 07/22/14--02:37: Index Taking Longer time to create
- 07/24/14--08:22: Issues synchronizing DB
- 11/29/06--09:52: Merge Replication Conflict Problem
- 07/28/14--22:17: SQL Replication in SAN replicated environment
- 07/30/14--19:39: Replicate encrypted data to subscribers in unencrypted form
- 07/31/14--10:01: Migrate SQL Server 2005 distributor to 2012 for 2005 publisher
- 08/01/14--08:53: Configure overwrite
My company has a SQL Server 2005 db that was acting as a shadow database to a SQL Server 2008 production database both on different servers. A contractor just recently moved the physical location of the server containing the shadow database and reinstalled to a different location with a different IP address. Now these linked servers are not talking to each other. There may have been a quick way to fix this but a coworker ended up replicating the shadow db to get the data current. So far, so good as all of the data is now matching up.
However, now the SSRS reports which use the replicated database as their datasource do not want to populate the reports with this new shadow database. When one clicks on the report it just hangs. No data ever comes forth.
I do not think that this is a SSRS issue as the SSRS files came up just fine prior to the replication. I am thinking that I need to configure the new database somehow. Anyone have thoughts on this type of issue?
I have filtered merge replication on the publisher with many subscribers. One of the publication become broken and i removed publication and subscription. it was a few days ago and now the subscriber has a new records that does not replicated to the publisher. How to create the replication, so that new data will synchronize from subscriber to publisher?
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
I use sql server 2012 Enterprise edition, and I face this problem after I configure Merge Replication using web synchronization and the error shown below displayed after 3 day in work.
and the following error shown on the client side
We had a replication subscription go inactive due to security issues which we have fixed and are in process of resnapping. I need to determine when the subscription went into the state of having to be reinitialized. I am having no luck looking
at the distribution history tables to determine this information. Does anyone have a query that I could use to determine this?
we are getting one issue when the time of dropping publication database on publisher server in transactional replication in sql server 2008 r2.
TITLE: Microsoft SQL Server Management Studio
Could not delete publication 'dbname_Pubs'.
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1&EvtSrc=Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Replication.ReplicationMenuItem&EvtID=CantDeletePublication&LinkId=20476
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Could not find stored procedure ''. (Microsoft SQL Server, Error: 2812)
We are experiencing an issue where our log reader is reading the commands and placing them into our distribution database, but when the distribution agent runs it skips certain commands (it is the same commands every time for one of our processes).
I have tried to troubleshoot the issue by running the commands manually on the subscriber, but the commands work just fine. Also, if I pull the skipped commands out and run them separate from the set on the published database, they do end up getting replicated.
We did add a column to the replicated table that is involved just prior to this happening. However, we did remove the table from the articles and then place it back into the articles to reinitialize the subscription.
Hi all, I have just migrate a legacy VM server from VMware to Hyper-V WIndows 2012.
I was reading up on Hyper-V Replication which needs SQL 2008 for minimal support and I realize that I have enable Replication on this server. This server is using Solomon IV which is a 16-bit software and dependency on SQL 2000. Would it mean Hyper-V Replication should not be enabled ?
Another question is that I have another VM server running SQL 2008 R2 and according to the requirement the below must be set to 1. How can I check the current value of the below ?
Set-VMReplication -VMName <vm-name> -EnableWriteOrderPreservationAcrossDisks 1
i have configured transactional replication with separate distributor server, the data copied and snapshot delivered,last 2days it is running, publisher to distributor is good, but distributor to subscriber it show heavy latency and it is showing critical status,when i see in the replication monitor, it shows undistributed commands 65000 records, when i see in snchronization status it showing 'deliverimg replication', when i compare to publisher and subscriber records difference is there, i checked the file tranfer speed 100mbps and bandwidth speed is als good....how to fix it
Can someone please provide step by step setup for SQL replication between different Domains?
Shouldn't indexes such as MSmerge_current_partition_mappings.ncMSmerge_current_partition_mappings have a fill factor other than 0? I am getting many page splits on this and other merge table indexes. My server has many of the indexes set to 0.
Using merge replication with 120 subscribers SQL Server 2008 R2 on distribution server.
we have started to replicate our live database to a remote test server. Both servers are running "Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)"
Our software uses two databases - first one holds the client data and the other one is for history data changes. The history data are written by triggers. We only want to replicate the first one with the client data.
I setup a new publication on the first server where our live database runs. After that I setup my publication as a “Merge publication”, for Subscriber type “SQL Server 2008” and so on…
My setup for a new subscription for the remote test server is “Run each agent at its Subscriber (pull subscriptions)”. The agent schedule is “Run continuously”, subscription type is set to “Client”.
Everything works fine - if I do some data changes on the publication database then the SQL Server replicates the data to the subscriber – that’s ok, but it’s too slow.
We recognized on the subscriber that the history trigger fires for each column one time – that means for our Part-Table which has 177 columns, it fires 177 times for each changed row.
E. g. when I changed 111 rows on the publication database in table Part, I got 19647 history rows on the subscriber database [DB_History].
All in all there are 177 (=columns in table Part) calls for each changed row. We think that’s the bottleneck. Why isn’t each row updated by one call of [MSmerge_upd_sp_xxx]?
The property "Multicolumn UPDATE" is set to "True" when I setup the replication. After that this option is shown as "False" and it can’t be changed because it’s disabled.
Have someone any idea how to change this behavior?
On the subscriber, there are many calls like these:
First call by the Replication Merge Agent is:
[dbo].[MSmerge_upd_sp_57E80269F8FF49205518DC22294346CB]'90F8EE6E-C0AE-E311-9403-005056842B7E',0x0E2C1000A0280000FEFFEF0F4B0B087E820D020EC10400000000000000000000,3,0x00,25,0x29435518DC2203000000FF,0x00,NULL,NULL,NULL,48,'1987-09-28 00:00:00',N'SI','2003-03-26 09:46:27',default,default,NULL,NULL,default,NULL,default,1.00000000,default,…,90
--2nd call by the Replication Merge Agent is:
---3rd call is:
---…and so on…
---177th call is:
Hi All I have a table which is 150 GB in size and I want to create a new Index on it but when I am creating index on it taking more than 3 hours and lots of blocking also happening. So I have kill that create index process. Can anyone give better way to do it less than 3 hours?
I have been having an issue synchronizing my DB to another server. I have 2 servers with a prod and dev DB on both. I have the prod DB on the primary server, and the dev on the secondary. I have replication set with the prod DB to the 2nd server working no problem. I just did a refresh of the DB for the dev server and I am trying to set up replication the the 1st server. We originally had this setup, but the refresh seemed to have broken it.
Anyways, I have the publisher and subscriber setup and a snapshot taken on the 2nd server. When I try to synchronize, I get a constant error of "Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber." After about a minute, it then starts back up and will say, "Skipping file 'file name' because it has already been delivered for a previous article or by a previously interrupted snapshot."
I have spent hours on Google trying to find a solution to this and I have no answers. One thing I wasn't sure is if I had to delete the DB of the subscriber server and if the replication put it back? Could that be my issue?
Any help would be great!
I have a Transactional replication with updatable subscription setup having 1 publisher and 3 subscribers. All the servers are SQL 2008 and have conflict resolution policy set as subscriber wins. Of late, I have been observing data mismatch for few tables. Some tables have records but their column values doesn't match. Some records are there on one subscriber but missing on publisher and other subscribers. However replication is running fine without any issue. I am trying to understand what could have caused this issue and how it could be avoided in future.
Do you guys have any idea what might be causing this and how to fix this?
Let me know if you need any further details.
FYI: There is no filter defined for any articles in replication.
at Microsoft.SqlServer.Management.UI.ConflictViewer.ViewerForm.GetWinnerSQL(DataRow loserRow, Boolean blockFetch)
at Microsoft.SqlServer.Management.UI.ConflictViewer.ViewerForm.summaryInfoGrid_SelectionChanged(Object sender, SelectionChangedEventArgs args)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.OnSelectionChanged(BlockOfCellsCollection selectedCells)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.SelectedCellsInternal(BlockOfCellsCollection col, Boolean bSet)
at Microsoft.SqlServer.Management.UI.Grid.GridControl.set_SelectedCells(BlockOfCellsCollection value)
at System.Data.DataRow.get_Item(String columnName)
at Microsoft.SqlServer.Management.UI.ConflictViewer.ViewerForm.SetLogInfo(DataRow logRow, String sql)
at Microsoft.SqlServer.Management.UI.ConflictViewer.ViewerForm.btnClearUpper_Click(Object sender, EventArgs eg)
Hi, I have successfully setup replication with Allow Initialization From Backup Files option enable.
By normal replication setup, if I need add new article into replication. I can just adding through management studio and run snapshot agent.
But since it is setup without snapshot agent how can I do if I need add new articles?
We are using SAN replication as part of our DR strategy. Also we do have SQL Server Replication in our environment for data flow to various instances/application. Below are my questions with respect to SAN & SQL replication
1. How to configure SQL Replication in DR instance. The DR instance will be made up only during DR Drill period or disaster occurence.
2. In case of Disaster, whether we need to manually configure replication ? Is there any possibility to resume the replication by validating the data available in both publisher and subscriber.
Please provide your suggestions on the same.
I have a question that I have not found anyone asking.
I have some encrypted fields at the publisher and want them to end up at the subscriber in an unencrypted form. The replication can be working on SQL2005 +
I have started researching altering the schema on the subscriber from the snapshot. Is there a way to call the decryptbyKey when the data is being replicated? Any insight would be appreciated.
I have 2 SQL Server 2005 SP2 servers (on Windows 2003). One is a publisher and the other is both distributor and subscriber. I am attempting to migrate the distributor/subscriber to SQL Server 2012 SP1 on Windows server 2012.
I am getting connection errors when trying to run sp_adddistributor on the original publisher.
"OLE DB provider "SQLNCLI" for linked server "repl_distributor" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "repl_distributor" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".
Msg 5, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server . "
I have verified that the distributor allows remote connections. I've tried connecting via sqlcmd, too and get the same error. Is this a limitation of the client connectivity components on eth SQL 2005 server, or am I missing something else?
Hello all. I am trying to setup replication for 10 databases between 2 servers. For simplicity, I will call them Server 1 and Server 2. I am able to get replication working, but I am wanting to use a UNC path for the data storage. the snapshot data will use an average of 18GB per day for total snapshot usage. Ideally, I do not want this data to reside on Server 1 itself, but on one of my mass storage devices before it is pulled to Server 2. I am wanting to know best practice for using UNC paths. I would like to know specifically, how to overwrite the replicated data from the previous day. I am fine with their being a static or floating ~20Gb on Server 2, but I would like to know how the data would flow. If I use a UNC path to storage on Server 2, when the schedule hits the specified time ( by the way I have 2 schedules setup. 1 to take the snapshot, then another later on for the replication) to replicate the data to Server 2 does the data have to flow back to Server 1 before it applies the SQL data to Server 2 or is it smart enough to know that if the data is already sitting there, and to just apply it?
Thanks in Advance!