Articles on this Page
- 12/31/13--11:57: _Transactional repli...
- 01/09/14--10:40: _SQL Server collatio...
- 06/15/11--09:25: _How to add a new Ar...
- 01/09/14--18:40: _Merge Agent failed ...
- 01/10/14--16:03: _Merge replication u...
- 01/10/14--20:06: _Replication driving...
- 01/13/14--07:55: _SQL Server could no...
- 01/13/14--03:48: _Replication to one ...
- 01/13/14--15:55: _Migrate from Existi...
- 01/14/14--00:37: _One way data replic...
- 01/14/14--08:28: _Merge replication e...
- 01/14/14--00:46: _One way data replic...
- 01/14/14--08:11: _Restore transaction...
- 01/14/14--16:34: _Enabling Replicatio...
- 01/15/14--07:21: _Deadlock on replica...
- 01/15/14--06:39: _Unable to add repli...
- 01/15/14--10:54: _msrepl_transactions...
- 01/15/14--17:49: _Extremely poor perf...
- 01/16/14--01:03: _How to delete a pee...
- 01/16/14--06:28: _Is Transactional Re...
- 12/31/13--11:57: Transactional replication server upgrade
- 01/09/14--10:40: SQL Server collation on for Data Warehouse
- 01/09/14--18:40: Merge Agent failed to locate the partitioned snapshot
- 01/10/14--16:03: Merge replication use of snapshot
- 01/10/14--20:06: Replication driving me nuts!!!!!
- 01/13/14--03:48: Replication to one subscriber from two publishers is possible?
- 01/14/14--00:37: One way data replication from MS SQL Server 2008 to MS SQL 2000
- 01/14/14--08:28: Merge replication error
- The schema script 'VW_ST_RESULT_R56b7b40_241.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001) Get help: http://help/MSSQL_REPL-2147201001
- Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL20164) Get help: http://help/MSSQL_REPL20164
- Invalid object name 'VW_ST_RESULT_WITH_SAMPLE'. (Source: MSSQLServer, Error number: 208) Get help: http://help/208
- 01/14/14--00:46: One way data replication from Oracle 11g to SQL Server 2008
- 01/14/14--16:34: Enabling Replication functionality between two similar databases
- 01/15/14--07:21: Deadlock on replicated trnasaction at subscriber
- 01/15/14--06:39: Unable to add replication feature in sql server 2012 web edition
- 01/15/14--10:54: msrepl_transactions and msrepl_commands
- 01/15/14--17:49: Extremely poor performace
- 01/16/14--01:03: How to delete a peer to peer replication
We have to upgrade our SQL 2008 publication to SQL 2012. Our Subscribers are still on SQL 2005 which also needs to be on SQL 2012. It’s heavily used OLTP system. Source databases all together are 1 TB.
The production server ServerA replicates to Server B and Server B replicates to Server C. Distributors are on publishers due to the higher or same SQL version on source.
Three different publishers Server A1, Server A2 and Server A3 replicate data to ServerB.
One database publishes from A1, A2 and A3 to Server B. So on Server B the data merges by unique keys. (Complex thing is the tables which doesn't make unique record we modified the insert/update/delete
replication procedures on source
servers to add hardcoded key value). Also, not the entire database is replicated. There are filters and few articles are replicating. Sometimes this adds problems. Troubleshoot takes time as re-initialization is not an option.
Q1: Is this the good design?
For rest of the databases, it's straight forward database to database replication. So on Server B there are three copies of databases replicating from A1, A2 and A3.
The Servers B and C are used heavily for reports and some reports require very close to live data.
Q2: How do I proceed with the SQL server upgrade to 2012? I have an option to go for log shipping or other types of replications. Any recommendation? I don't want to make it very complex.
Q3: Is it good idea to keep distributor for source servers (A1, A2 and A3) on different servers? Would it help in performance or replicate the transactions smoothly (without delay or queued)?
Q4: To All SQL replication guru - please help me and give me inputs and suggestions. I would appreciate all your help.
Let me know if you have any questions.
We have our database in SQL SERVER 2008 R2 which has collation SQL_Latin1_General_CP1_CI_AS which is an case insensitive collation.So i facing issue while inserting data which varies in upper and lower case.which collation can i use so as to make our Database case sensitive in SQL Server.
Thanks in advance.
I have a publication and subscription in place and want to add a new article into it. the problem is when I fo it, I need to reinitialize the entire subscription to see the effect.
is there any way to reinitialize the subscription and publication for only the new article added ?
Thanks in advance,
We have merge replication setup, there is one server that will not finish the initialization. Almost all the tables in the publication are filtered. The Data connection is via native SQL and FTP is used to deliver the snapshot. During initialization the subscribers partition is successfully created, all the schema object and data is moved across the FTP, the database is built and populated, and then just before finalization of the subscription it throws the follow error:
The Merge Agent failed to locate the partitioned snapshot for this subscription in the expected location. If the publication does not support Subscriber-requested snapshot generation, ensure that the partitioned snapshot for this subscription has been generated. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199429)
Get help: http://help/MSSQL_REPL-2147199429
If we try to re-inititalize the subscription it will create the same exact folder repeat the entire process and then fail.
we have turned on verbose logging and all the logs look good:
Examples from the publisher log files:
2014-01-08 20:31:49.98 -DynamicFilterHostName GZQRS0011
2014-01-08 20:31:49.98 -DynamicSnapshotLocation \\SEKUSQL\ReplData\ftp\SEKUSQL_SEKUTNT_805_NSV1_PUB_SEKUTNT_805_NSV1\GZQRS0011_2\
2014-01-08 20:32:15.00 [86%] Bulk copied 100000 rows from [dbo].[CodeHistoryLocation] (1200000 total rows copied)
2014-01-08 20:32:15.08 [86%] Bulk copied snapshot data for article 'CodeHistoryLocation' (1250000 rows).
2014-01-08 20:32:15.88 *************************** Performance Statistics ****************************
2014-01-08 20:32:15.88 Overall snapshot generation time (seconds): 25.83
Then from the subscriber side the log is full of:2014-01-10 17:40:38.588 Ftp get file from SEKUSQL_SEKUTNT_805_NSV1_PUB_SEKUTNT_805_NSV1\GZQRS0011_2\Sys_AppSettingType_19.sch to C:\Windows\TEMP\f652230cf66e4b7b9b5a518845ef7f3d\Sys_AppSettingType_19.sch.
During the initialization it will completely build the database and load all the data then just error out saying failed to locate the partitioned snapshot for this subscription in the expected location.
I am lost and need any ideas of what and where to look.
I have a very large database using merge replication and I am wondering if I can remove the snapshot as a step in the snapshot agent job (pre step so it would remove the existing snapshot before creating the new one) so I don't have to increase my disk capacity. Any known issues or concerns with doing this? How long is a snapshot normally retained? I thought this was based on the publication retention setting.
Company has about 20 users updating a database, however these database are at very remote sites and very rarely have access to internet and when they do it's very sketchy! Trying to set up replication on an application so that these users can sync up to the database when they have internet.
Right now, it's working on some computers, and not working on some, so I keep thinking I'm moving forward but then I'm back at a stand still.
The error I'm getting on one of the machines is that the machine cannot access the listener. However when I navigate to the listener via IE, I am able to access it after entering server credentials.... But yet with other computers it works fine.
Anyone have any idea what could be causing this?
We have configured replication and wanted to remove it hence without any checklist we have deleteddistribution database and wanted configure newly but couldn't find "configure distribution". Later we tried to disable publishing and distribution finally we received the below error. Please share your views on this and suggest on how to configure replication at this scenario. Thank You
SQL Server could not disable publishing and distribution on 'WIN-KPDO'.
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Database 'distribution' does not exist. Make sure that the name is entered correctly.
Changed database context to 'master'. (Microsoft SQL Server, Error: 911)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.3368&EvtSrc=MSSQLServer&EvtID=911&LinkId=20476
----Learners Curiosity Never Ends----
Is it possible to configure replication to one subscriber from two publishers?
Subscriber 1 = (Server = C & Database = db03 )
Publisher 1 = (Server = A & Database = db01 )
Publisher 2 = (Server = B & Database = db02 )
Note: Domain for these three servers is same.
Please share your views on this. Thank You.
----Learners Curiosity Never Ends----
I have an existing cluster sitting in Rackspace. We have a new co-location with its own SAN that we want to migrate everything over to. Now, if we were keeping the SAN active in Rackspace, this wouldn't be an issue and I'd just add two new nodes to the cluster and take down the two old nodes, but I need the data shipped to the new SAN so everything in Rackspace can be turned off. VPN is configured between sites (500mbps pipe), so bandwidth isn't a problem.
Should I be adding new shared storage to the existing cluster, replicate to that, turn off the old shared storage, then add new nodes and eventually disable old nodes? I'm trying to do this with the least downtime.
The picture can best be described as this (very simplified)
RACKSPACE CLUSTER - on its own SAN
Node 1: SQLSERVER1-RACK
Node 2: SQLSERVER2-RACK
SQL Server Name: SQLSERVER
NEW CLUSTER - on its own SAN
Node 1: SQLSERVER1-NEW
Node 2: SQLSERVER2-NEW
Do anyone got idea about one way data replication from MS SQL Server 2008 to MS SQL 2000, can this case use sync framework? or other easy way?
I am getting these messages when checking sync status.
In creating my publication I was careful to allocate the correct processing_order to each article, so that dependent articles were processed after the articles they depended on.
I cut down the publication to just those articles related to the ones in the error, and it worked fine.
What is it that these error messages are telling me exactly?
Oh, merge replication, SQL 2008 R2, every view, table, function and stored procedure, no filtering.
Do anyone got idea on one way data replication from Oracle 11g to MS SQL 2008 Server. I am focusing on build-in tool or freeware.
Our publishers, distributor and subscribers are on three separate servers and SQL Servers respectively.
Our subscriber and system databases are unavailable due to a SAN failure.
Is it possible to restore backups of the subscriber and system databases to a brand new instance without losing the pull subscription to the existing publications?
I would like to restore all subscriber and system databases to a new SQL Server instance on a different server without losing access to the transactions building up on the remote distributor.
I have one feed inserting/updating data into 2 different databases (But views & storedprocedures are different on each).
Now we are planning to stop feed into one of the database (let us say Database2) and continue into other (Database1).
And then have a sql server replication, to publish data from Database1 to Database2.
Now my issue is, how to intialize the subscription (as my tables are huge)?
I know when I initialize by default, it will drop my subscription objects and then do the sync. But I dont want do this, as those are big tables and also thoese tables will be having triggers that will not be in the subscriber. Also if I select"Keep existing object unchanged", then I will get the duplicate records inserted into subscriber.
Is there any better way to this ?
Thanks in advance..
I get this warning often now. Can someone please tell me why anf how to resolve it? Transaction (Process ID 52) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. (Source: MSSQLServer, Error number: 0) Thanks,
I get this warning often now. Can someone please tell me why anf how to resolve it?
Transaction (Process ID 52) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. (Source: MSSQLServer, Error number: 0)
We are using SQL Server 2012, Web edition and when it was installed replication is not an added feature so I tried to add this feature but getting below error.
Error: There are no SQL Server instances or shared features that can be updated on this computer.
Description: The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update. The installed SQL Server product version is 11.1.3000.0, and the expected SQL Server version is 11.0.2100.60
And also please let me know how to identify the default file location of the setup file 'setup.exe' for SQL Server 2012 (Webedition, 64bit) Grateful to your time and support.
I'm using "C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2777772\QFE\setup.exe" to add replication feature, please correct me if I'm wrong.
----Learners Curiosity Never Ends----
When I execute select * from msrepl_transactions and msrepl_commands, I see one row in the msrepl_transactions result.
If the msrepl_commands table has all the repl commands groups by a transaction then why can't I see anything returned in msrepl_commands?
I queried sp_browsereplcmds but don't see the actual command there as well.
Shouldn't these two tables be kept in sync always?
We have a client who has a database server (MS SQL 2008) and a couple of the databases are being replicated to a couple of different servers. One server is local to the database server (i.e., same physical network) and the other server is remote (at
another datacenter, connection is via VPN). The sychronisation performance is *extremely* poor (based on the "Delivery Rate): one of them is currently at about 0.44 rows per second and the other is about 1.14 rows per second. It does not matter
of I stop the synchronisations and start them again; they start off pretty good for about 5-10 minutes (12+ rows per second) but then steadily decline until they are around their current rates. The replications are configured as "Merge Replications",
and as far as I can tell are using the defaults from the replication setup wizard.
I have tested connectivity between the servers in question by transferring a 3GB ISO file. From the SQL server to the subscriber server that is local, the file transfers at about 35-40MB/s, and from the SQL server to the remote server at the other datacenter, it is about 10-15MB/s.
I am not even close to having DBA skills (I can create and manage simple databases, but have never had an environment with replications, etc.)
I have no idea where to start looking or at what to figure out why the performance is so poor. I have searched on this issue, and many articles go into the database coding, etc. and that's something not currently under our direct control.
Any suggestions and/or pointers to pretty straight-forward guides (i.e., for non-DBA) to look at and use to troubleshoot (if any exist) would be appreciated.
actually I want to drop and recreate the peer to peer replication. How can I do it?
Is it possible to configure Transactional replication with updatable subscriptions in sql server 2012 or it is deprecated?
----Learners Curiosity Never Ends----