add article in merger replication

April 16, 2014, 12:16 am

≫ Next: Data Loss in merge replication

≪ Previous: Merge Replication Hardware requirment

$

0

0

hello everyone,

is there any way to add article in already configured publication in merge replication with out snapshot of entire database.

as per my query it take snapshot of only newly added article not for entire db.

for example:

the distance between publisher and subscriber is 1200 km.

db size=50 gb(it's already configured in merge replication) after that as per our requirement I added one new article(size 1 gb) for that database, if I run snapshot agent it take whole db snapshot it's time consuming.

when I add one article in transaction replication it take snapshot of newly added article only. like that any way in merge replication.

---

Data Loss in merge replication

April 16, 2014, 6:48 am

≫ Next: Mr

≪ Previous: add article in merger replication

$

0

0

Hi,

I have a server with SQL 2008 as publisher and several Laptops with SQL 2008 R2 as subscribers (push).

Our customer is complaining about sporadic data loss on the subscriber side. The inserted record has disapeared on the subscriber side and I think was never uploaded to the Publisher (?). Is there a way to check out what records have been uploaded to the publisher?

Does someone have a SQL-Script based f.ex. on msmerge_Contents to get some "readable" data out?

BTW. no filtering is active.

Thanks,

Patrick

Mr

April 17, 2014, 4:20 am

≫ Next: Resynchronizing subscription will cause data loss.

≪ Previous: Data Loss in merge replication

$

0

0

Dear Support,

Can you elaborate this one

What's the difference between SQL Replication and SQL Database Mirroring

and how to configure both....

Thanks

Naushad

---

Naushad Alam

Resynchronizing subscription will cause data loss.

April 17, 2014, 9:20 am

≫ Next: replication alert is never fired.

≪ Previous: Mr

$

0

0

Background:

Pertinent Information:

System and user databases from live production machines were restored to virtual machines with identical Computer Names to those in the field (Format of {2-Letter state code}{2-Letter partner/pharmacy code}-{2 or 3-digit partner/pharmacy identifier}-{2-digit machine identifier} ).

These restoration appear to have been done with the  KEEP REPLICATION option.

MSTDC session logs for these machines show sporadic attempts to contact and begin transactions with their distributors. It is not constant. Some of these virtual machines have Computer Names that do not match the local Server Name of MSSQLSERVER instance which they are ‘mimicking’. Some still do. The only log data that I could locate for these MSDTC sessions did not provide the contents of the transaction – successful or failed – so I do not know for certain whether any ‘mock’ data made its way to production, a cursory review of the SQL Server Queue Reader Agent logs from these time periods would indicate that it did not. “Spot” tests of attempting to locate test data in live production servers was also unsuccessful – but the test instances which seem to be the initial source of this problem are already overwritten. So, potentially apples and oranges. In the process of restoring a database from a computer swap, the log reader appears to have attempted to reinitialize all 103 articles for the subscription.

Investigation revealed that each publication now has five subscriptions – and the current facilities databases appear to be assigned the “most recent” of these subscriptions (the highest range of article_ids). Every article in the Publisher’s distribution database was marked as “queued for reinitialization”, this has been (ostensibly) corrected. However, for the most recent facility, the snapshot that the publisher wants to “push down” consists of only the data from the “most recent” set of articles – that is, they want to take all the data that’s there right now and replace it with data from April 16, 2014 10 AM to April 16, 2014 1 PM.

Checking the replication subsystems the repldata from the previous snapshot appears to be valid and in place already but I am having difficulty finding a way to tell it “You already have the data you need, just use that”.

Any thoughts on how we can recover from this situation? 

replication alert is never fired.

April 17, 2014, 9:32 am

≫ Next: The initial snapshot for publication 'xxxxxxx' is not yet available.

≪ Previous: Resynchronizing subscription will cause data loss.

$

0

0

I tried to set up email alert in SQL 2005 when replication is successfully completed. I set up the dbmail and it works fine. I enabled dbmamil profile in SQL server agent; I also enabled the "Replication: agent success" in the alerts and checked the email in the response and set a right operator to notify. However when a replication was completed successfully, no email was received. Is there anything or any step I missed? By the way, I check the msdb..sysreplicationalerts but it is empty.

Thanks

The initial snapshot for publication 'xxxxxxx' is not yet available.

April 17, 2014, 11:28 pm

≫ Next: Data is not replicating in subscriber

≪ Previous: replication alert is never fired.

$

0

0

Hi,

Data is not replicated in subscriber even log reader agent continuously delivering the transactions. Showing not running status in Replication Monitor. 

Data is not replicating in subscriber

April 17, 2014, 11:44 pm

≫ Next: Merge Replication schema definition of the destination table does not match source table

≪ Previous: The initial snapshot for publication 'xxxxxxx' is not yet available.

$

0

0

hi 

Log reader agent continuously delivering the transactions but those are not replicated in subscriber. In replication monitor showing not running status. Please guide me on this issue.

Merge Replication schema definition of the destination table does not match source table

June 26, 2013, 5:52 pm

≫ Next: replication

≪ Previous: Data is not replicating in subscriber

$

0

0

I added a column to a merge replication article. The DDL change propagated to the subscribers but now I'm getting this error message.

The schema definition of the destination table 'dbo'.'tdat_store' in the subscription database does not match the schema definition of the source table in the publication database. Reinitialize the subscription without a snapshot after ensuring that the schema definition of the destination table is the same as the source table. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199478)

The schemas are the same but for some reason, the merge agent doesn't recognize this. Is there any way to fix this without reinitializing my subscriptions?

---

replication

June 16, 2013, 5:17 pm

≫ Next: Queue reader aborting

≪ Previous: Merge Replication schema definition of the destination table does not match source table

$

0

0

I'm looking to automate, replication set up. I have one pushliser and 2 subscribers.Distributor stays on the same instance of publisher.

This steps I follow.

Run the login script against the database.
Right click on replication folder and generate the script.,replace the null with the user password for logins.
break the replication by below query.

restore the database.
run the replication script that is taken in the step 2.
Expand the replication folder->expand  the local publications -> there will 2 publications.
Right click on each->view snapshot agent status->check the generate snapshot option ->click ok.
do the same for another publication.

Once snapshot is done, and if the it's fails while bulk copying then re-initiatation all subscriptions.

I like to know how to automate or generate query for  below steps

run the replication script that is taken in the step 2.
Expand the replication folder->expand  the local publications -> there will 2 publications.
Right click on each->view snapshot agent status->check the generate snapshot now option ->click ok.

Once snapshot is done, and if the it's fails while bulk copying then re-initiatation all subscriptions.

any help is greatly appreciated.

---

vivekanandhan periasamy

Queue reader aborting

April 11, 2013, 9:59 pm

≫ Next: SQL 2012 Transactional Replication Publisher is also AG Primary, AG fine, but Replication status continuously 'waiting for next Log backup'

≪ Previous: replication

$

0

0

Hi all, This is my detailed error. The Queue Reader Agent has encountered the error  "Row handle is invalid". when connecting to "DB1" on "DB2". Ensure that the publication and subscription are defined properly and that both servers are running. From last week I suffer from this error. It happen 2 or 3 times per day. I want to know whats the reason and how to resolve this problem. pls help me this is a critical issue. Thanks.

SQL 2012 Transactional Replication Publisher is also AG Primary, AG fine, but Replication status continuously 'waiting for next Log backup'

April 19, 2014, 5:14 pm

≫ Next: Issue in change tracking table on subscriber after reinitialization the subscriber

≪ Previous: Queue reader aborting

$

0

0

Hi,

I have a SQL 2012 instance that hosts 3 databases that are publishers in (push) transactional replication to subscribers in other domains and are also primary in an Availability Group to other instances in the same domain.  The AG is healty (synchronized), and replication is ok for 2 databases, but the third continuously shows the Publisher to Distributor history status as 'Replicated transactions are waiting for next Log backup or for mirroring to catch up.'

I have weekly full, nightly differential, and hourly log.  Those are running and I've tested restoring the publisher db from them into a test instance.  The option for sync_with_backup is 0.  I generated a new snapshot, no change (haven't reinitialized, that will be last possible option as this is production).  When the log backups run, status will briefly change to 'Approximately (x) log records have been scanned in pass # ..., 0 of which were marked for replication' and some data does replicate, but then status immediately changes back to the message about waiting for log backup.   We are only replicating tables (no views, sp's, etc).  All subscribers and AG secondaries are SQL 2012.  My db is less than 200 GB data. 

The jobs are continuously running and data updates are occurring on the primary.  The distribution database is on the same instance as the publishers.  Anyone have any ideas what could be happening? 

Thanks greatly!

Issue in change tracking table on subscriber after reinitialization the subscriber

April 3, 2014, 12:49 pm

≫ Next: Distribution add published

≪ Previous: SQL 2012 Transactional Replication Publisher is also AG Primary, AG fine, but Replication status continuously 'waiting for next Log backup'

$

0

0

Hi All,

We have enabled change tracking on the subscriber tables and its getting dropped during a reinitialization.we are running an ETL on the subscriber tables basing on change Tracking.Our Initial ETL runs once and incremental ETL runs after that but after reinitialization i am getting fresh data and my initial ETL has already run.So how can i resolve this issue.Can't renireinitialization be done without disabling the Change Tracking.

Kindly provide your feedback.

Thanks

Distribution add published

April 21, 2014, 9:05 pm

≫ Next: Can a trigger change a DROP to DELETE?

≪ Previous: Issue in change tracking table on subscriber after reinitialization the subscriber

$

0

0

Hi Team

we have configured transaction replication after that 

In Distribution  why we  need publisher?  what is the use we have to add publisher  could you please  explain me bit clearly.

V.new to replication  process..

---

subu

Can a trigger change a DROP to DELETE?

April 22, 2014, 9:20 am

≫ Next: merge replication

≪ Previous: Distribution add published

$

0

0

My company has software running our equipment that records information to a SQL Server 2005 database.  I would like to back up this information via replication.  I cannot do this at present because the information tables have no primary key.  I cannot just add primary keys to them because every two days the software DROPs one of the tables and recreates a blank table with the same structure.  (If we make the tables bigger than two days or about 10,000 rows the software starts recording nonsense information due to what I believe is poor database design, but can't change because we do not have any support from the software manufacturer.)

I did try adding a primary key to one table and setting it up for replication; the software apparently just ignored the error of not being able to drop a replicated table and started adding new data to the old table, which is a problem since it risks nonsense data being recorded.

I had the idea of adding a DDL trigger on DROP_TABLE to instead DELETE all the table's rows (if I could extract the table name from the command...).  Is this possible?  Or would the command try to DROP the table first, get the error about not being able to drop a replicated table, then abort and never activate the trigger?

merge replication

April 23, 2014, 12:21 am

≫ Next: Column Changed

≪ Previous: Can a trigger change a DROP to DELETE?

$

0

0

 please help me,

recently I got below error in my merge replication,

The replication agent has not logged a progress message in 5 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.

thanks in advance!

---

Column Changed

April 23, 2014, 12:09 am

≫ Next: Replication Issue

≪ Previous: merge replication

$

0

0

Hi Team,

In T-Replication in article one column was changed  char(200) To varchar(100).

Now  How  can we update in pulisher  and  publication  tables request  to you guys please  suggest me.

Thanks in advance.

---

subu

Replication Issue

April 24, 2014, 3:39 am

≫ Next: Non-Admin access to Replication Article using ReplMonitor role not working?

≪ Previous: Column Changed

$

0

0

I want to remove Snapshot Replication that was not configured well from a production Server and configure new one (Peer- to- Peer) Server to Server. What is the best way to do this without effecting the production Server?

Non-Admin access to Replication Article using ReplMonitor role not working?

April 22, 2014, 1:53 pm

≫ Next: Installing SP3 on MSSQL SERVER 2008 with Replication

≪ Previous: Replication Issue

$

0

0

Greetings, we are trying to get some non-sa users access to check replication monitor in our non-production environemnt, and I followed the article in the technet doc here:

http://technet.microsoft.com/en-us/library/ms151221.aspx

The user is an AD account, he can access the servers fine and is in the replmonitor role in the distrubution database on the distribution server which is separate from the publications on another sql server and separate to the subscriber database on another sql server. These are all running the same version of sql server 2008 r2 enterprise/developer. When I have the user try to start replication monitor, it will start and show the distributor, when I try to have them add a publisher, we get the error  "server xxxxx is neither a publisher nor a distributor, or you do not have permission to access replication functionality on this server".  Any idea what I am missing here as the article looks straight forward. Thanks

Installing SP3 on MSSQL SERVER 2008 with Replication

April 24, 2014, 5:28 am

≫ Next: Cannot drop publisher?

≪ Previous: Non-Admin access to Replication Article using ReplMonitor role not working?

$

0

0

Hi there

How would one go about installing SP3 on SQL 2008 with replication? Would i need to turn off replication to avoid schema changes taking place across the line?

Our servers are across the country and wouldn't want all that data to replicate over the tiny line we have.

Instead we would like to install SP3 at the publisher and then at the subscriber.

During testing on the dev instances, after stopping all agents ( log reader and queue reader) then installing and turning them back on didnt seem to work.Are there any whitepapers on the proper process on how to install SP3?

Thanks in advance

Cannot drop publisher?

April 24, 2014, 3:14 pm

≫ Next: [MS-SQL/SQLite] Sync MS-SQL Server DB with SQLite DB

≪ Previous: Installing SP3 on MSSQL SERVER 2008 with Replication

$

0

0

I want to drop an Oracle publisher from SQL Server (2008).

exec sp_dropdistpublisher @publisher='mypub'

However, I got the following error when executing the stored procedure. How to drop the publisher?

Msg 2812, Level 16, State 62, Procedure sp_dropdistpublisher, Line 194
Could not find stored procedure ''.
Msg 2812, Level 16, State 62, Procedure sp_dropdistpublisher, Line 204
Could not find stored procedure ''.

And `exec sp_helpdistpublisher @publisher='markit_sfprod'` returns no row. 

The following stored procedure called in sp_dropdistpublisher returns null for @distribdb. It caused the problem.

EXEC@retcode = sys.sp_MSrepl_getdistributorinfo    @publisher      =@publisher,@distributor    =@distributor    OUTPUT,@distribdb      =@distribdb      OUTPUT,@publisher_type =@publisher_type OUTPUT