.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

Change in transaction replication articles without enabling the enable Schema Replication to true

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

We have a transactional replication database where in we have set the schema change property to false. Now we have added a new column and to the table and wanted this column also to be replicated. But before enabling the allow schema replication parameter, we have altered the article added a column.

Now we reliazed that we have not enabled the sehema replication option. The database is very large and reinitializing the subscription remains our last option.

Could anyone suggest us the right way forward.

Thanks in advance.


View Complete Post

More Related Resource Links

enabling replication

Hi,   I was trying to use SSExpress as a subscriber for replication, but when I try to add a subscriber to the database it says: ====================================================== TITLE: New Subscription Wizard ------------------------------ Microsoft SQL Server Management Studio is unable to access replication components because replication is not installed on this instance of SQL Server. For information about installing replication, see the topic Installing Replication in SQL Server Books Online. For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=ReplicationNotInstalled&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Replication components are not installed on this server. Run SQL Server Setup again and select the option to install replication. (Microsoft SQL Server, Error: 21028) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=21028&LinkId=20476 ====================================================== Where can I find this option?  neither link seems to work...  

Reinitialize transaction replication clear the subcriber data and replicating again

Hi all, I add new table in to mu publisher database and reinitialize the subscriber.And i select the option to create new snapshot and marked as reinitialize.When it starts the reinitializing it clear all data from subscriber and coping again.Am i missing any thing here to add new table into existing replication ? Regards, Theesh

SQL 2008 Transaction Log too big from Replication

How do I clear transactions from log due to a failed attempt to setup replication?

Select all articles that have participated in a merge replication in the last n days/weeks

I have a merge replication set up in MS Server 2000. Some of the published articles are not used. I am trying to write a query that will select these articles as well as the time when they have been last used in the replication. I was know that in the distribution database there is a table [MSmerge_history] however I cannot figure out how to join it to MSarticles. Any help will be much appreciated! Regards, Pencho

which is best Snapshot Replication or Transaction Replication for my requirement?

Hi,    We have a main transaction database where all the live data is there.Now, to run a reporting application,we need a  different database, but the data is as EXACTLY as the live database.So,probaly every noght aroung 1 0'clock,we want to sync these two databases.   In this scenario,which is better, Snapshot replication or Transaction Replication? what are the pros and cons of using them? As I am new to this things,ur answers would be very much helpful..

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  

Serve to server Transaction Replication error


I have windows 2003 sp2 servers each hosts SQL Server 2008 SP1 standard edition. I am trying to replicate both servers, using the tutorial available in the online documentation <Tutorial: Replicating Data Between Continuously Connected Servers> which can be found at: ms-help://MS.SQLCC.v10/MS.SQLSVR.v10.en/s10rp_1devconc/html/9c55aa3c-4664-41fc-943f-e817c31aad5e.htm

I have created the users (repl_logreader, repl_distibution, repl_snapshot, and repl_merge and setting their security. Then I have created the distibutor, setting database security as mentioned in the document, and last creating the publication with a snapshot to be run immediately, distributor and publisher are on the same server and the publication will be pushed to the subscriber. Once the publication is created succesfully, I am checking the agents to see the errors. I am always stuck with the following two error messages:

1- snapshot agent error:

Error messages:

Message: Failed to create AppDomain "mssqlsystemresource.dbo[runtime].1090".
The domain manager specified by the host could not be instantiated.
Failed to create AppDomain "mssqlsystemresource.dbo[runtime].1091".
The domain manager sp

Bi-Directional Transaction Replication?


hi all

i want to know how to reslove conflicts when using Bi-directional transactional replication ,,conflicts like

1-If you insert a record that has a key into a table on one of the servers and another record that has the same key already exists on the other servers that participate in the replication, the replication does not propagate the changes to the other servers.

2-When you update a column in a record that is updated at the same time on another server, the data may be different on the two servers.

3-When you update different columns in a record, simultaneous updates of different columns of a record may sometimes lead to conflicts.

4-When you delete a row that is being deleted at the same time on another server that is participating in the replication, the replication fails because the DELETE statement does not affect any rows on some of the subscribers.

..i need help to know what to do to handle this conflicts and if there is any implementation or any ideas about this issue




SQL Server 2008 merge replication snapshot hangs on filtered articles


I have a publication on SQL Server 2008 Standard Edition using merge replication.  When I attempt to generate the initial snapshot, the snapshot agent appears to hang on the step "Setting up the publication for filtered articles."  I get a long (over 4 hour) series of messages: "The process is running and is waiting for a response from the server."  I know something is happening server-side, as SQL Server and the snapshot agent use a lot of memory and max out one core's processing capacity.

This has me confused as the publication is not doing any filtering.

Even more confusing:  I backed up the database and restored it onto my development-test system.  I created the snapshot there, and it took under 10 minutes every time.

Any suggestions for investigating and resolving this?

Tracking of schema changes replication has stopped working in some of our publications


Environment Summary

Our environment is SQL Server 2008 R2 running Merge Replication with Web Synchronization using the SQL Server Compact Edition 3.5 SP2 Server Tools, and SQL Server Compact Edition 3.5 SP2 for the client DBs on full Windows XP or later OS’s.  We have about 120 articles, each of which range from 10 published columns to close to the 255 limit. Regarding join filtering, we have a root article filtered on the hostname, which then has 2 levels of filtering cascading off that.  We are using the default Row Level change tracking.


The Problem

Tracking of schema changes replication has stopped working in some of our publications

The manifestation is that subscriptions schemas are left behind at some point in time, and the only temporary recovery has been to delete the client DB and get it to recreate from a snapshot which then contains the latest schema.  However, subsequent schema changes don’t propagate.

The longer term workaround that we have applied has been to manually update the sysmergesubscriptions table on the publication DB and set the schemaversion column values (ALL of which are inexplicably high in this

Sanpshot Replication of all objects and Table Schema but no Data


Can this be done? I just want all database objects to be pushed out to a subscriber once a week via snapshot replication. Procs, tables, triggers, functions etc but I dont want any of the table data

Thanks in advance

Transaction Replication


Hi Team,


i have one dought


publisher is 2008 subscriber is 2000 data will be published or not

because we are going to configure this t-replication. suggest me.





Transaction LOG shipping of a Std. Transactional Replication


I have a primary database replicated to another server where I have added legacy data to the subscription. 

1.Can i perform Tx Log shipping of this subscription  to another server?

2. Republishing of the subscriber was very hard to maintain and throws errors when ever the servers involved are restarted. Can Log shipping help in this respect? 


3. Question: Can we add static data to the subscriber when using LOG shipping? Thanks

table schema changes not being propagated - merge replication


I have attemped to change column types (i.e. from int to varchar(8)) on read-only published tables. I used ALTER TABLE ALTER COLUMN to make the change, and according to BOL this should make sure the changes are seen at the subscribers. Unfortunately, after I make the change to table and run sp_enumeratependingschemachanges, I do not see the table changes listed. However I can make changes to SPs and UDFs, and they do show up in sp_enumeratependingschemachanges and on the subscriber. Any ideas would be appreciated.
The publication is marked for replicating schema changes, the publisher is SQL 2005 and the subscribers is SQL 2005 Express btw.


Darrell Young

SQL Server 2005 Schema Replication in Merge Replication


Dear Sir,

I am using SQL Server 2005 Developer Edition for Creating & Testing Database.

I had created Merge Publication WITHOUT FILTERING ROWS and Created Push or Pull Subscription. Now if I Add or Drop column using ALTER TABLE (T-SQL) in Table OR modify stored procedure using ALTER PROCEDURE in Published Database then while Synchronizing It replicate same in Subscriber Database and works very fine.

But when I had created Merge Publication WITH FILTERING ROWS (Parameterize or Static) and Created Push / Pull Subscription and I try to Add or Drop column using ALTER TABLE (T-SQL) in Table  OR modify stored procedure using ALTER PROCEDURE in  Published Database then while Synchronizing It DOESN'T REPLICATE in Table of Subscriber Database but tries Replicate in Stored Procedure and display error.

After Adding Column in Table of Published Database, If I Checked Article in property of Publication then it Adds column but it doesn't selects it. I also checked using sp_enumeratependingschemechenges it displays pending schema changes of stored procedure but

error occurred while I tried to setup transaction replication with updateable subscription

   when I tried to setup transactional replication with updatable subscriptions between two nodes, an error occurred.

The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "REPL1 " was unable to begin a distributed transaction. Changed database context to 'database1'.

OLE DB provider "SQLNCLI" for linked server "REPL1" returned message "No transaction is active.". (.Net SqlClient Data Provider)
 May I know whether in order to setup transactional replication, do I need to run replication agents under domain users or local users?

thank you

How to get transaction replication latency value from code behind?



I'm using transactional replication only for reporting purpose (DB1 (publisher) ->DB2 (Subscriber).For Some function really on the latency time to select data from DB2.That mean When user click one button it will update in DB1 first then by the changes it will read from DB2.So now I have hard code the wait time to read from DB2 after update in DB1.What is the correct way to solve the problem. Is any way to get the latency time from Distributor from code behind?

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