Articles on this Page
- 03/14/13--18:34: _Merge Replication -...
- 03/14/13--20:26: _SQl 2005 Bidirectio...
- 03/15/13--01:48: _SQl 2005 Bidirectio...
- 03/15/13--03:30: _Replication
- 03/15/13--04:52: _Why are updatable S...
- 03/15/13--01:16: _subscribed table info
- 03/15/13--05:13: _subscrition of the ...
- 03/16/13--19:41: _Replication clarifi...
- 03/18/13--12:44: _Replicate from MS S...
- 03/18/13--08:58: _Configure Distribut...
- 03/18/13--05:16: _Facing issues with ...
- 03/19/13--09:19: _SQL 2008 R2 Standar...
- 03/19/13--15:26: _Replication and con...
- 03/19/13--09:48: _Which type of repli...
- 03/19/13--08:21: _Replication network...
- 03/19/13--10:38: _LogRead.exe removin...
- 02/10/13--23:42: _SQl 2005 Bidirectio...
- 03/19/13--22:32: _Replication
- 03/20/13--02:48: _Subset filters and ...
- 03/20/13--04:08: _Replication
- 03/15/13--03:30: Replication
- 03/15/13--04:52: Why are updatable Subscriptions deprecated?
- 03/15/13--01:16: subscribed table info
- 03/16/13--19:41: Replication clarification
- 03/18/13--12:44: Replicate from MS SQL Server to PostgreSQL???
- 03/18/13--08:58: Configure Distributor for Replication in 2008
- 03/19/13--09:19: SQL 2008 R2 Standard- Replication (Do Not Replicate Missing?
- 03/19/13--15:26: Replication and concurrency check failed.
- 03/19/13--09:48: Which type of replication or possibly mirroring do I need?
- 03/19/13--08:21: Replication network traffic
- 03/19/13--10:38: LogRead.exe removing logging from event manager
- 03/19/13--22:32: Replication
- 03/20/13--02:48: Subset filters and HOST_NAME()
- 03/20/13--04:08: Replication
In my case there is a merge replication setup between two sql server 2005 DB's.
one act as subscriber and another as publisher.
Now on publisher, apart from merge replication related triggers (MSMERGE_INS_<GUID>) for each table (article) in DB . For each table in DB, I also have my own insert,update and delete trigger.
so now when merge replication is started my triggers also flow to subscriber end. How to avoid this. Please advice.
I am looking at the Update Stats in replication Monitor for Subscriber Changes Uploaded to Publisher and I was hoping that
I could audit those to see at a record level which ones have been uploaded to the Publisher.
Any advice appreciated.
In reference to http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/d3b2987e-7391-4c35-9b65-a04068f2209c
i have a clear audit trail of a Published Table and also on the Subscriber. My investigation is showing that
for an Update being pushed from the Publisher to the Subscriber it looks like *sometimes these updates also
get logged to be Pushed Back from the Subscriber to the Publisher.
This is very confusing.
Is there some best practice guidelines to follow to bypass this behavior?
Any advice greatly appreciated and have yourselves a great weekend:).
i am just started learning the ms sql server DBA.
please tell me.
Generally what kinds of issues happening in the REPLICATION..?
just out of curiosity. Are there any informations why updatable subscriptions are deprecated? I can't find any and would like to know if anything is wrong with those.
From Subscriber server, I need to know from which table(Originator) a particular table is subscribed. I can easily check from Publisher but seems not enough way to find the same from subscriber. It is in SQL 2008 R2 transactional replication.
Kindly mark the reply as answer if they help
Is it possible in the configuration of the subscription to ensure that data older then 30 days get deleted?
We have a subscrition of the last 30 days but the problem is that the DB doesnt delete the older records automaticly.
Using MSSQL 2005.
I am new to Replication. Would like to know or clarify below.
Is 2 way transactional replication is peer-to-peer replication?
What is the difference between peer-to-peer and Merge Replication?
Thanks in advance.
Hi I would like to ask if i can Replicate from MS SQL Server 2008 to PostgreSQL 9.x and how ??????
OR Vs XOR
I am trying to configure a distributor for replication in SQL Server 2008. For some reason when I right-click on Replication there isn't a "configure distribution" choice? Does it need to be enabled first?
Facing issues with service a/c while uploading file where user can upload file to site without any issues.
We are facing file upload issues into site which has been integrated with middle layer authentication setup. As site is hosted on with service a/c.
We note that when we use middle layer of security authentication then file upload is happening with login a/c which has the Kerberos delegation property enabled. when we remove this middle layer authentication and directly hit the site the we can upload the file easily.
Please suggest any issues.
I'm setting up a publication where all I want to do is replicate Insert and Updates only. In the Article properties the "Statement Delivery" is not available, therefore I don't see where I can select in the Delete Delivery (Do Not Replicate Delete Statements)
Is this because this is R2??
I have several sql 2000 servers at outside location and sql 2008 at the corp office.
I have a few tables that I set up with transactional replication with updateable subscriber. Pull.
This was set up at 3 locations. Things were looking good for a few days it appeared. I tested changes at both ends good, I check data integrity good. I was to the point of linking them into the corp FE.
Then.......all three location came up with an error while preforming the same procedure. updating one of these tables from another of these tables. (seem like at the same time?)(could be just timing)
[Microsoft][odbc sql server driver][sql server]Optimistic concurrency check failed. the row was modified outside of this cursor.
I tried tested: shutting down the services "queue, log, snapshot"
stopping all agent jobs (replication)
disabling all agent jobs (replication)
ensuring none were running at publisher or subscriber
this worked for a short time but the error returned and eventually had to delete the publications.
the database at the outside locations was written by a 3rd party that is not accessable.
Any help that I can get would be so much appreciated.
One of our clients is using our software with merge replication of a database on a MSSQL 2008 R2 server. There are two production environments in separate geographical locations only one of which is live at any one time, so basically one and live one on standby. Only the live database is updated by teh applications. Every couple of months they failover between the datacentres and the standby environment become the live centre. There is an instance of SQL2008 in each datacentre and merge replication is used to keep them in synch. This was all working ok until the beginning of the year when we started getting replication errors with some lTID fields in various tables that have the Identity property set.
The errors were like this one:
The insert failed. It conflicted with an identity range check constraint in database 'GateMain', replicated table 'dbo.tGateCalcsLog', column 'lTID'. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.
Then after the last failover we noticed we had an issue with the lTID values in one specific table. Our application relies on the lTID value always having incremented in order such that the highest lTID value is always the newest entry in the table. We've found that due to how the identity ranges are being managed by replication that when the system is failed over that the lTID range of the now live database server may have a range of values that are lower than those already present in the table. Is there a way to manage this in merge replication so we can guarantee that the next identity value allocated to the lTID field in greater than any lTID currently in the table? Or do we need to use a different type of replication or possibly mirroring?
We are getting a ton of activitiy from our distributor server and Main SQL Server (Publication).
We currently have 3 MSSQL 2008 Servers. Publication, Distributor, and Subscriber.
The Publication and Distributor is logging a ton of traffic and I need to reduce the logging traffic.
Can I reduce the time it takes to sync or replicate?
Is it possible to remove logread.exe from security Audit Sucess from my Event Manager?
I'm getting a ton of these every min.
The Windows Filtering Platform has permitted a connection.
Process ID: 5004
Application Name: \device\harddiskvolume2\program files\microsoft sql server\100\com\logread.exe
Source Address: 192.168.20.14
Source Port: 49236
Destination Address: 192.168.20.12
Destination Port: 1433
Filter Run-Time ID: 69200
Layer Name: Connect
Layer Run-Time ID: 48
Firstly SQL 2005 Bidirectional Merge Replication is setup and working between the Publisher and the subscriber.
I am monitoring the stats for Downloaded and Uploaded statements and for the most
part things are looking great.
I am doing data compares (Excluding the timestamp datatype) to confirm things are A ok and
I found that for a few records (Current count is 5) on a certain datetime column is different on the
Publisher from the Subscriber and I was hoping to track down as to the reason.
1. There are no Triggers on the Subscriber at all.
2. There are some AFTER triggers on the Table in question on the Publisher but none of them
affect the field in question.
Unsure if this helps but I have also tried to run the below to force the row in question through from the Publisher to the Subscriber but this also does not force things through for the field in question.
declare @int as int
exec @int = sp_mergedummyupdate 'customer','0DDA6892-5E59-E211-8F91-001A64DB8758'
Any advise would be greatly appreciated.
when i configure replication in snapshot folder some files are created like BCP,IDX,SCH AND one more
file is created that is the PRE.
WHAT IS THE ".PRE" FILE IN SNAPSHOT FOLDER..?
I have many tables need to be dynamically filtered based on HOST_NAME() parameter.
First approach is to Subset filtering the join table and join the other tables to it, but this looks to have performance and timeout issues when updating correspondent datapartation.
Second approach is to Subset filtering all the tables and remove the join filters, in order to do this my filter needs to be like : SELECT TitleId FROM Title WHERE DocumentId in ( SELECT DocumentId FROM Document WHERE UnquieId = HOST_NAME())
My question is the second approach possibles, i read that putting the HOST_NAME() in a subquery has too many problems and might not work, Can any one help ?