.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Easy Web
Imran Ghani
Post New Web Links

Transactional Replication ISSUE - 487 tables need to be replicated

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :
 

Hi All!

I have configured transactional replication on 7 databases from an sql server 2005 to another sql server 2005.

One of them has 487 tables and when I check "Replication Monitor" it shows that everything ok, but database above , that shows the message "Performance Critical".

My question is : The tables have been replicated or not ? How can I check this ? It´s not possible check table per table. Anyone suggests any other way to check if tables and their data have been replicated.

Thanks in advance ,

RBretas.

 




View Complete Post


More Related Resource Links

merge replication system tables fragmentation issue

  
I have Merge replication going on in my environment. The problem is that system tables like MSmerge_content, MS merge _tombstone and MSmerge_genhistory are getting fragmented. We are rebuilding indexes time to time daily. But we want some good fix. Just send some good idea guys?

Transactional replication: Updates to one of my columns (sometimes) does not get replicated from the

  
hi, This is my scenario: I have a varchar(max) column on a table that is replicated to other servers. I have a stored procedure that does and update to this column and other columns on the table. This is done inside a transaction that also includes other updates. When I call the stored procedure, this one varchar(max) column's value is not replicated. When I just run the single update statement on its own, the value is replicated. Anyone know something about this? Thanks!    

transactional replication and sp_MSupd tables

  
Hi thre, My target server keeps running sp_MSupd sp for different values in profiler and synch status shows "delivering replication commands" I keep waiting but this never ends. and ultimately we run a snapshot and it can't be applied. So recreate the whole replication again. It runs fine for a while but again, the sp_MSupd sp starts running on the target server and the replication goes down again. I don't know how to fix this. any advices?   Regards

Issue with transactional replication on SQL 2005 SP3 using row filters with bit columns

  
We recently upgraded from SQL 2000 to SQL 2005 SP3 and I am noticing something that I think is a bug with replication from a publication that has an article in it with row filters.  It seems to be that if the row filter has columns that are bit datatype and that column is updated on the publisher to cause the row filter to exclude it, it is not removed from the subscriber.  If you update a column that is part of the row filter that is not a bit datatype it works as expected.  I can reproduce this in a test environment with a small base table.  In production this is resulting in an occasional 20598 error "The row was not found at the Subscriber when applying the replicated command". Is anyone aware of a hotfix that addresses this? I can think of a few work arounds but the table is rather large and I really would like to avoid having to pull replication, re-snap or changing datatypes on the base table etc. Any suggestions are greatly appreciated.  Thanks!

avoid accidental delete on Subscriber tables - transactional replication

  

Hello pundits..

I am looking to see if we have any way to set on the subcsriber to avoid accidental deletes on subscriber tables to avoid the 20598 error(where the publisher is trying to replicate a record not existing(rather deleted in accident) at the subscriber end). This is for transactional replication

regards


SQL Server 2005 Replication - Replicated Databse Performance Issue

  

Hello,

 

I am struggling to work out a very frustrating replication issue and wondered if anyone could help me.

Here is my situation.

 

I have a virtual machine with 16gb RAM and 4 quad core 3Ghz processors and 250gb disk. This has Windows Server 2008 64 bit installed.

The machine has a SQL Server 2005 64 bit instance installed with SP3.

I have setup a publication on this SQL Server called pub1 , this publication publishes all tables/sp's /views and UDF's . I have set the article properties for the published tables as below.

- Copy Check Constraints = True

- Copy Clustered Index = True

- Copy Non Clustered Index = True

- Copy Default Value Spec = True

- Copy Collation = True

- Copy Insert, Update and Delete = True

- Copy unique key contraints = True

- Copy XML Indexes = True

Every other setting is set to false.

I have created a subscription to pub1 within the same SQL Server instance. The database has replicated everything I require without an issue.

If I run a query against the databse that I have published, it returns the query in less than 10 secs. If I run the same query against the subscription DB then this query takes over 30 mins to return.

I thought this was an issue with the indexes not replicating. From what I have selecte

Transactional push replication in SS2008r2 Timeout issue

  
The problem: Set up transactional (push only) replication from SS2008r2 to remote SS2008r2

The issue: Replication manages to send the table structure before going into an unending cycle of trying to send the data and receiving Sql Native Client Semaphore timeouts - Try again later msgs. From what I've read, this indicates some sort of network issue.

Side observation - setting up and initializing a snapshot replication of a larger table to the remote server works like a charm.

Question: (1) Why does the straight snapshot work and not the initial snapshot for the transactional subscription. (2) Where, how to troubleshoot this issue ( i need some guidance here so point me in the right direction). I'm ready to enter into dialog. Thanks in advance for your help.

Koko

joekoko

Transactional push replication in SS2008r2 Timeout issue

  
The problem: Set up transactional (push only) replication from SS2008r2 to remote SS2008r2

The issue: Replication manages to send the table structure before going into an unending cycle of trying to send the data and receiving Sql Native Client Semaphore timeouts - Try again later msgs. From what I've read, this indicates some sort of network issue.

Side observation - setting up and initializing a snapshot replication of a larger table to the remote server works like a charm.

Question: (1) Why does the straight snapshot work and not the initial snapshot for the transactional subscription. (2) Where, how to troubleshoot this issue ( i need some guidance here so point me in the right direction). I'm ready to enter into dialog. Thanks in advance for your help.

Koko

joekoko

Transactional Replication issue Between SQL Server 28 R2 and Denali (SQL2011)

  

Hi All,

OS :Windows 7

SQL Server Instance : SQL Server 2008 R2 (Publisher)

Distributor : On SQL Server 2008R2

SQL Serer Instance : SQL Server 2011 Denali (Subscriber) Pull Subscriber.

Replication Topology :  Transactional Replication

I have Installed SQL Server 2008 R2 and SQL Server 2011 CTP on the same machine. Setup Replication between SQL Server 2008 R2 and SQL Server 2011 using Transactional Replication Topology.

I have added one table as artical with default settings , the table has one int and 4 varchar datatype columns having rows=26004606.

While distributor agent deploys the snapshot on the subscriber , it failed with the below error :

SQL Server encountered: '23(Data error (cyclic redundancy check).)' resulting from an attempt to read the following: sort run page (1:35472), in file 'D:\Program Files\Microsoft SQL Server\MSSQL11.DENALI_2011\MSSQL\DATA\tempdb.mdf', in database with ID 2.

Issue while adding article to existing subscription(Transactional Replication)

  

We are haing issues while adding article on existing subscription.

The replication is setup with Initialize from backup=true.

Below is the command I tired to use aftet transfering the rows thru export import wizard but the table on the subscriber isnt refreshing.

exec sp_addarticle @publication = N'marcus8rpl' , @article = N'appnames' , @source_owner = N'dbo' , @source_object = N'appnames' , @type = N'logbased' , @description = null , @creation_script = null , @pre_creation_cmd = N'NONE' , @identityrangemanagementoption = N'manual' , @destination_table = N'appnames' , @destination_owner = N'dbo' , @vertical_partition = N'false' , @ins_cmd = N'CALL sp_MSins_dboappnames' , @del_cmd = N'CALL sp_MSdel_dboappnames' , @upd_cmd = N'CALL sp_MSupd_dboappnames'


Issue while Adding article in existing publication Transactional Replication.

  

We are facing difficulties adding article to an existing publication.The replication was setup by restoring the backup on subscriber  from publisher and changed the setting Intilialize from Backup =True

Used the following steps but it almost bought down the system.

EXEC

sp_addarticle

 

@publication = N'marcus8rpl',


Locking published tables while generating the snapshot infinite (Transactional replication)

  

I set up a transactional replication, publisher 2005 SP2 to a subscriber SQL 2008r2. The database is about 90 GB. When I want to create a Snapshot, the snapshot agent is running to 96% and then give a error. I have set up some logging, here is the tail of it:

------------------------

2011-05-16 20:16:15.32 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLAutorisatieRegister' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.32 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLBericht' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLBerichttype' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$XBRLFault' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$Ziekmeldingsregistratie' during concurrent snapshot into the distribution database.
2011-05-16 20:16:15.33 [96%] Inserted stored proc to disable constraint/triggers article 'WGF B.V.$Ziekte Bijzonderheden' during concurrent snapshot into the distribution database

transactional replication falling behind. millions of transactions in sp_brosereplcmds

  
Hi, Hi All, we have transactional replication set up with all the agents running at source database. The synchronization status is stuck at "delivering replication transactions". The replication latency in replication monitor says excellent. when I check sp_browsereplcmds. it ever ends. It has over more than millions of rows of output. We were having trouble with this replciation recently because at the source db. they run a large batch. So we decided to schedule snapshot agent to run exactly after that batch but the snapshot doesn't seem to helping out with the latency. what should be done to resolve the issue. Please help. thanks.

getting an e-mail notification when a transactional replication stucks

  
Hi all, I've SQL Server 2005 and a transactional replication scenario with one puplisher and 11 subscribers. Sometimes one of the subscriptions fails and a manual operation is required. Is there a way to get an e-mail notification whenever the replica fails or stucks or simply degrade its performances?

Issue with sharepoint site replication?

  
Hi all, I have a requirement where in i need to replicate the business intelligence report to N no of subistes i am able to create reports to the site and also able to replicate to another site. But the problem here is the webparts that are getting created in the new site refers to the same old location and it is giving me exception that the filter is no more valid one. Is there any way i need to change the location of the newly created webpart location. Waiting for your reply.  

set reinitialization period on Transactional replication

  
How do you set the parameters on Standard Transactional Replication to Reinitialize after a certain period of time? Thank you.

Unable to publish two tables for replication. They have a key with a red x.

  
I am trying to figure out why I can't access the DB that I've replicated.  Two tables have a key with a red x that makes it so I can't publish them for replication.  In addition, how do I replicate all the user roles and permissions with the database that is being replicated?  I am using SQL Server 2000.   More info:  I can't access the replicated DB through the client software.  It is accessible through SQL Management Console.  I had to manually export all users and roles and then run the query to get them into the replicated database.  Is there a more thorough way to replicate a database?  How can I make an exact copy on a different server so all information is intact?
Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend