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


Post New Web Links

Issue while adding article to existing subscription(Transactional Replication)

Posted By:      Posted Date: April 14, 2011    Points: 0   Category :
 

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'




View Complete Post


More Related Resource Links

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',


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!

Issue Adding a new Lookup Field to an existing List Instance

  
I have a code base that houses all of the column, content types, template, and list instance definitions. Am using the Update functionlaity a lot from version to version. Has been working well to this point. I just added two new columns (fields), one a Lookup and the other a Multi-Lookup. The fields are added fine on the update, columns look correct and the content type to which these were added also look fine. I can create a new List instance from the content type, and the new lookup columns are fine. The problem is this. Any existing list instances that were created from this same content type, now blow up when I try and access list items via the SP GUI. Something about a valid GUID, I dont't have the exect error anymore, but will repost it when I recreate the issue for the tenth time. I tried deleting the new lookup fields from this new list instance, thinking that I might be able to re-add them to fix the problem, but I get a new stack trace when I try and re-add them. Any hints on where I can start digging would be appreciated. I think I'll start with comparing the list instance schemas between an existing list and a newly created one.  

automatic adding new article to existing publication

  

Hi!

I have two servers with SQL Server 2005 Enterprise Edition. There are several databases on it. I implement snapshot replication (every hour) and everything works fine. But developers are creating new tables, views and etc every day. How i can automaticaly add it (tables, colums, views etc) in existing publication (i need to replicate all data in database). Or i need to use another solution like database mirroring?


Best regards

Transactional Replication - Creating Snapshot after adding a new table

  

Hello,

 

Sorry for my English..

 

Could you tell me if it is possible not to create entire snapshot after adding a new table? Our database is very big and it takes a lot of time to make snapshot.

 

Also could someone tell me exactly how works blocking of tables while creating snapshot?

I've read in BOL that if Snapshot Replication is used then all tables are blocked while creating snapshot for replication. And if Transactional Replication is used, snapshot is created in parallel mode and tables are not blocked and users can work with them. I understand that in second case each table is blocked while it is processing and after processing it is unblocked and next table is blocked. Is it so?

 

Also I am interested how actually tables are blocked? For SELECT/UPDATE/INSERT or how? Where can I read information about it?

 

Thanks,

V

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 with update-able subscription issues??

  

Hi, 

I am doing transactional replication with update-able subscriptions and I have come across few issues that have kept me stranded: Here  they are: 

1.can we not drop a table in Transactional replciation with updatebale subscriptions? I was assuming that with this mode, if you drop a table it will drop on subscribers as well?

2.if a new table is created at publisher, only the after running the snapshot agent(before adding the new table to the publisher) it would appear at the subscriber, can this not be automated somthing like if a new table is created, replicate it to the subscriber by itself when next snapshot agent runs, instead of manually adding it to the publisher(of course, it has to have pk's to qualify for replication)

3.In Transactional replciation with updatebale subscriptions, I can see the data changes made at both publisher and subscriber are being applied on both the nodes but when schema changes are made like adding new column, dropping column,  the changes made at subscriber are not being applied on to publisher but the ones made at publisher are being applied on to subscriber? I guess, i should be able to do this on publisher as well with this mode(I think queue reader is responsible for this, (queue reader is running al the time)).

4. what is

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.

Transactional Replication ISSUE - 487 tables need to be replicated

  

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.

 


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?

peer to peer replication, drop and add article of same name

  
We have peer-to-peer replication set up on our system (2005 EE). I would like to change the metadata of one of the tables (many of the tables actually, but right now I'm just trying to test out the process with just one table). As this is a high-availability system, I would like to stop the replication, make the changes on one node, verify that the changes are working, make the same changes on the other node, then re-enable replication. The ddl changes to the table are extensive enough that I have to clear them before executing. So I will handle re-populating the tables in a later step. Right now I'm just testing the process of stopping, doing ddl, then restarting. I am trying to implement this using scripts so as to minimize my clicking (and thus potential for mistakes) when doing it for real. I find that if I do the following process using the SSMS interface it goes smoothly with no errors (note that each step is conducted on both nodes unless specified): stop sync agents manually remove article: tblName1 with 'publications properties window' close 'publications properties window' make ddl changes to tblName1 (change column names, add columns etc. to a particular table) manually add article: tblName1 with 'publications properties window' re-enable agents But if I try the following, I get 'Peer-To-Peer topologies require identical articles in publications at all n

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
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