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

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

'Initialize with backup' Option in transactional Replication

Posted By:      Posted Date: October 13, 2010    Points: 0   Category :Sql Server

We have set 'Initialize with backup'  while intialially restoring the backup over subscriber.My question is

When there is a failure on sunscriber or agent will I be able to reintialise the snapshot without changing any setting?

View Complete Post

More Related Resource Links

Transactional Replication: Schema Option

1.I need to Replicate a db without replicating its constraints, only the tables. What is the best way to achieve this? 2.Need the Subcription(replicated db) to have the collation of the server being replicated to. Please explain how the options need to be configured. Thanks  

Transactional Replication Log Backup Strategy


I have the log backup setup every 15 minutes on the production server by using the below command


The reason I use this command is we dont need point in time recovery and top of that we dont have storege for Log backups.

My question now is can I setup transactional replication with this setup in place or do I need to store the TLogs physically?




Why do you need Sync with Backup in Transactional Replication?


I am setting the transactional replication.My boss is worried about the point in time recovery on the subscriber if anything failson the subsciber .My question is I know we have log retention period of 2-3 days by default . Will that not take care of replaying the logs from publisher when there is a failure on the subsciption or distributor level?



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

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?

Replication Subscriptions by using Backup and Restore

I thought this would work, but obviously I've overlooked something. I have SQL Server 2008 on 2 servers. Have database on publisher server and want to merge replicate to subscriber, but didn't want to take days like it did last time. 1. I published the database and ran the snapshot agent. 2. I backed up the database to a .bak file. 3. I copied the .bak file to the subscriber computer. 4. I restored the database on the subscriber computer from the .bak file. 5. Back at the publishing server, I added the subscriber under subscriptions, but I unchecked the "Initialize" box since that was the point of doing the backup, copy and restore. And. Oops. The replication monitor says it has a syntax error at "AccountPK." That would be the primary key for the account table. That wasn't what I hoped for. Suggestions? You can't be successful at this unless you're at least 1/2 a bubble off level.

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!

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.

Row Filters using Transactional replication & joined criteria

Hi guys, I am after some advice as to my replication setup and what I can do with it.  I have only basic knowledge of replication but have had transactional replication setup for a while now which replicates a few of the main databases tables and it is working fine.  However we want to improve performance of our subscriber database, so I would like to use row filters for this. Imagine the setup of a database table for Questionnaires which has a Void bit field in it, and a table for Answers.  On the subscriber I want only non-void Questionnaires and their answers. So I set the row filter for the Questionnaire table to be "WHERE Void = 0", I think this works.  However, I don't think it works when I am working on the Answers table, my row filter would be "WHERE QuestionnaireID IN (SELECT QuestionnaireID FROM Questionnaires WHERE Void = 0). This works fine for the initial snapshot but not for following transactions. For example, if I made a Questionnaire not void then I'd expect that to make its way to the subscriber along with its answers. Or if I voided a Questionnaire I'd expect that Questionnaire and set of answers to be removed from the subscriber database. I have read that this type of filter that uses a subquery only works with merge replication, if my understanding is correct? So my question here is, can you validate my findings, is

Transactional Replication: Agent Profiles

Can someone explain the different Agent profiles and when is it appropriate to use one over the other?  Agent profile, continue on data consistency error...when can this be used?

Replication option SQL 2005 Standard Edition

Hi, We are using SQL 2005 Standard Edition.  We would like to use Replication for one of our database. I would like to know answers for the questions. 1. Can we use Replication features with SQL 2005 Standard Edition 2. Can we use DR site with replication for the reporting purpose?  Is there any risks associated with option? 3. Do we still need to take transaction log backup on the production server if we use replication.   Thanks.      

truncate_only' is not a recognized BACKUP option

Hello All,I am able to run the below command in sql 2005 but in 2008 getting error : truncate_only' is not a recognized BACKUP option.Back Up Log [DBName] with Truncate_Only  dbcc shrinkfile([logFileName]) Thanks in AdvanceAshwin

File Groups and Transactional Replication. PLEASE HELP


Im running transactional replication sql 2008 and have a couple table names with the same name but different schemas.  I want to make sure in the replication that the filegroups stay with the subscriber.  Is this possible?
Table AAA.Customer on file group A
Table BBB.Customer on file group B
Is there a way to keep these filegroups without rebuilding the index after it has been moved?  I noticed there was an option in the replicaiton options to keep file group but it doesn not seem to help.  Can you let me know how.  THANKS>

SQL 2005 Transactional Replication without Primary Key...


Hi All,

I am newbie to SQL 2005 and doing my first project  (I am an exchange/AD Consultant). I am trying to do a transactional replcation across a VPN link. I have humdreds and hundreds of tables to be replicated. I have around 100 tables which are without any primary key. I am using http://blogs.techrepublic.com.com/howdoi/?p=123 for configuration.

I am able to replicate the tables which are with Primary keys, can't replicate any tables which are without primary keys. I am sure there must be a work around or some solution for the tables without primary keys. 

Please help.




Need a solution for transactional replication


Dear friends,

I have a Database which contains about 15 tables that 10 of them should be replicated to another database which its schema is "EXACTLY" same with the publisher. The 5 tables that are not planed to publish, have no rows all over the time (indeed the subscriber DB is just a template DB that should be synchronized becuase of some reasons)...

At snapshot definition I just set each table to Truncate All rows at initialization level. But the problem was that it drop all indeces automatically and FK Constrains which causes the different schema in subscriber DB. So I dcided to set to Copy ALL of related objects (indeces,FKs,cluster indeces,triggers ,...) at initialization level. But the problem is with 5 tables that are not published when all their relations with the other 10 tables will be droped at initialization level....Beside of all these problems I get FK constraint error at initialization time...

Also I should mentioned that my DB version is 2000 SP4.

Did I miss or misunderstood something? or should I choos another solution? or some problem in SQL 2000 and should migrate to 2005 or 2008?

Thanks for your appreciation

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