FOREIGN KEYS IN DISTINCT PUBLICATIONS

July 7, 2014, 10:20 am

≫ Next: Transactional replication, management alter schema

≪ Previous: Full Replication with only selected tables merged

$

0

0

hi all, i have this doubt, i have 2 distinct publications, publication A and publication B

in the publication A i hava table A, in the publication B i have the table B,

the issue is this, the table B references to table A, with a a foreign key constraint but in the synchronization process does not creates the phisical foreign key on the object explorar but the others constraint are created correctly like unique contrasints and primary keys.

in the publication database object explorer the objectes appear correctly..

but .... as you can see in the next picture, in the suscription database object explorer does not appear the foreign key but the other constraints does appear correctly !!!

the option copy foreign key constrains is enabled on the articles properties of the publication.

if you can help me i will really, really apreciate you... 

NOTE: an apologize for my bad english :)

---

Transactional replication, management alter schema

July 8, 2014, 6:04 am

≫ Next: Transactional Replication starts failing when the Weekly maintenance job (Rebuild Index) runs

≪ Previous: FOREIGN KEYS IN DISTINCT PUBLICATIONS

$

0

0

Hello

Firstly, sorry for my english, I'm french.

I have a question on transactional replication system and specifically on the propagation of command who alter schema.

Contexte 1 :

In thetransactionalreplication, with initialization of subscribers bysnapshotagent and the option of parameter :« replicate schema changes » equal true.

Question 1 :

What is the system allowing the propagation of alter schema ?

            Example : ALTER TABLE …. DROP COLUMN

Contexte 2 :

In thetransactionalreplication, with initialization of subscribers bybackup restore and the option of parameter : « replicate schema changes » equal true.

Question 2 :

What is the system allowing the propagation of alter schema ?

            Example : ALTER TABLE …. DROP COLUMN

 Thank you.

Transactional Replication starts failing when the Weekly maintenance job (Rebuild Index) runs

January 13, 2012, 6:01 am

≫ Next: .ldf file is eating disk space in SImple recovery Model Sql server

≪ Previous: Transactional replication, management alter schema

$

0

0

Hi All,

We have a transactional replication setup between two servers in the same network which works fine throughout the weekdays. During almost every weekend (Saturday) when the maintenance job runs, the replications starts failing with the follwoing error:

Replication-Replication Transaction-Log Reader Subsystem: agent MyServerName-MyDBName-2 scheduled for retry. The process could not execute 'sp_replcmds' on 'MyDBName'.

Or

Replication-Replication Transaction-Log Reader Subsystem: agent MyServerName-MyDBName-2 scheduled for retry. The process could not execute 'sp_repldone/sp_replcounters' on 'MyDBName'.

Or

Replication-Replication Distribution Subsystem: agent MyServerName-MyDBName-MyPublicationName-MySubscriberServerName-22 scheduled for retry. The process could not execute '{call sp_MSget_subscription_guid(22)}' on ''.

We use to get any one of the above mentioned errors almost every weekend.

Additional information:

Database Size: ~ 1 TB

Replication is done for selective tables.

Maintenance job includes the following tasks:

1) DB Integrity Check

2) Rebuild Index

3) Cleanup History

4) Maintenance Cleanup

5) Replication Reinitialization

Replication starts failing when the Rebuild Index task have started and ran for some time.

At present we are dropping the replication completely and recreating it using a new snapshot because only reinitialization does not work.

Please let me know if you need more information.

Any help will be great.

Thanks!

Indeb

.ldf file is eating disk space in SImple recovery Model Sql server

May 12, 2014, 6:58 am

≫ Next: Replication related items are not restored from database backup

≪ Previous: Transactional Replication starts failing when the Weekly maintenance job (Rebuild Index) runs

$

0

0

Hi,

I've got an SQL SERVER 2005 which has a transactional replication running .

Our main concern is Log file is growing and we were not able to truncate the log space . We run "sp_MSdistribution_cleanup" stored procedure every alternative days to clean up the distribution database and also tried shrinking the log file .

It is not working. Is there any solution for this ? How to truncate the logpsace .

Appreciate your help.

Thanks in Advance

Cheers,
Sandy

Replication related items are not restored from database backup

July 9, 2014, 11:31 am

≫ Next: merge replication one table count mis match out of 229

≪ Previous: .ldf file is eating disk space in SImple recovery Model Sql server

$

0

0

I recently restored latest production database backup on my development machine. Production database has replication setup for some of the tables as a publisher.

I then made some changes to stored procedures and tables (modified some and created some new ones) and compared my local copy of database with current production database on production server using VS 2008 Schema compare. After comparison completed I realized (to my surprise) that changes related to replication (rowguid table columns and table triggers called MSMerge***) were not restored on local copy.

Is this an expected behavior? I don't really know anything about replication and it is not important if it doesn't work on my local copy of the database. I am modifying come tables and stored procedures for the project I am working on and was expecting that the only differences between schemas would be that I made but all these replication related items always come up (because they don't exist on local copy) and it is a bit of an inconvenience.

merge replication one table count mis match out of 229

July 10, 2014, 12:19 am

≫ Next: How to add a column to the article through Axapta AOT, on which standard transactional replication is configured

≪ Previous: Replication related items are not restored from database backup

$

0

0

dear team,

we are using  merge replication between 8 databases out of that in one database one table count not equal remaining all tables have the equal count .

and I am getting below error message in replication monitor.

please help me its urgent for me.

thanks in advance.

 Error messages:
The merge process could not query the last sent and received generations. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200929)
Get help: http://help/MSSQL_REPL-2147200929
TCP Provider: An existing connection was forcibly closed by the remote host. (Source: MSSQLServer, Error number: 10054)
Get help: http://help/10054
Communication link failure (Source: MSSQLServer, Error number: 10054)
Get help: http://help/10054

---

mastanvali shaik

How to add a column to the article through Axapta AOT, on which standard transactional replication is configured

July 10, 2014, 1:07 am

≫ Next: SQL Server 2008 Merge Replication crash and thousands of fake updates from subscriber to publisher

≪ Previous: merge replication one table count mis match out of 229

$

0

0

Hi Everybody,

Our existing production database is back end of MS Dynamics-AX ERP, We need to add a column to the existing table on which transactional replication is enabled. As AX will not support Add/delete columns from SSMS, we have to do the same through AX - AOT.

Through MS-BOL, i understood that there will not be any impact, when creating the column using the alter command, where as the replication will get failed, when we create the column through SSMS GUI. Pl correct me if i am wrong. I didn't found any information about the impact on replication, when it is done through AX-AOT

Could anybody guide me. what are the steps that has to be followed to avoid replication failure, while adding the column through AX-AOT  .

Thanks,

G.N.Rao.

---

Thanks, G.N.Rao.

SQL Server 2008 Merge Replication crash and thousands of fake updates from subscriber to publisher

July 10, 2014, 7:55 am

≫ Next: Can you setup CDC on Replicated Database and not the source database

≪ Previous: How to add a column to the article through Axapta AOT, on which standard transactional replication is configured

$

0

0

Hello,

We are experiencing strange updates from subscriber to publisher.

The system is a "default settings" merge replication, 1 publisher SQL Server 2008 Enterprise, 24 subscribers SQL Server 2008 Standard, with filtered partitions and pull subscritions.

Every 30 minutes each subscriptor replicates against publisher.

Normal update activity is 300 rows / 30 minutes. 

Sometimes 1 or 2 subscribers start to upload 200k rows that nobody changed (during the day and during the night, with no customer activity at all). There isn't any client updating those rows.

It seems that replication tables are somehow out of sync or corrupted and the merge agent needs to upload records.

The result is thousands of conflicts at publisher.

The short-term solution to conflicts is to apply mergedummypudate stored procedure to those records.

The problem disappears by reinitializing subscriber.

The issue has a suspicius frequency of 14 days (default snapshot generation frequency)

A suspicius memory dump of replication merge agent appears on subscriber.

WinDbg:

*******************************************************************************
*                                                                            *
*                        Exception Analysis                                   *
*                                                                            *
*******************************************************************************

*** WARNING: Unable to verify timestamp for replmerg.exe
*** ERROR: Module load completed but symbols could not be loaded for replmerg.exe
*** WARNING: Unable to verify timestamp for sqlncli10.dll

FAULTING_IP: 
replrec+6314d
4e6b314d 8b420c          mov     eax,dword ptr [edx+0Ch]

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 4e6b314d (replrec+0x0006314d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000000c
Attempt to read from address 0000000c

CONTEXT:  00000000 -- (.cxr 0x0;r)
eax=00000000 ebx=00000000 ecx=01d1d8c0 edx=00000020 esi=00000e3c edi=01d1e414
eip=772370f4 esp=01d1e3cc ebp=01d1e438 iopl=0         nv up ei ng nz ac pe cy
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000297
ntdll!KiFastSystemCallRet:
772370f4 c3              ret

PROCESS_NAME:  replmerg.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0000000c

READ_ADDRESS:  0000000c 

FOLLOWUP_IP: 
replrec+6314d
4e6b314d 8b420c          mov     eax,dword ptr [edx+0Ch]

NTGLOBALFLAG:  0

APP:  replmerg.exe

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

FAULTING_THREAD:  00000fc8

BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_BEFORE_CALL

PRIMARY_PROBLEM_CLASS:  NULL_CLASS_PTR_READ_BEFORE_CALL

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_READ_BEFORE_CALL

LAST_CONTROL_TRANSFER:  from 6b0beaba to 4e6b314d

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
01d1f7d0 6b0beaba 01040048 0416716c 02eadb6c replrec+0x6314d
01d1fe2c 6b0c0153 00000000 01d1fe5c 01d1fe78 replprov+0x5eaba
01d1fe3c 4e6898be 024b2ff8 01d1fe5c 01d1fe9c replprov+0x60153
01d1fe78 4e6ac0a1 04164424 02eaca2c 00368d6c replrec+0x398be
01d1fee8 4e6af01d 00000001 023a1b68 00000000 replrec+0x5c0a1
01d1ff1c 734429bb 00000000 ee206aa3 00000000 replrec+0x5f01d
01d1ff54 73442a47 00000000 76bcee1c 023a7478 msvcr80!_endthreadex+0x3b
01d1ff5c 76bcee1c 023a7478 01d1ffa8 772537eb msvcr80!_endthreadex+0xc7
01d1ff68 772537eb 023a7478 74e02971 00000000 kernel32!BaseThreadInitThunk+0xe
01d1ffa8 772537be 734429e1 023a7478 00000000 ntdll!__RtlUserThreadStart+0x70
01d1ffc0 00000000 734429e1 023a7478 00000000 ntdll!_RtlUserThreadStart+0x1b


STACK_COMMAND:  ~9s; .ecxr ; kb

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  replrec+6314d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: replrec

IMAGE_NAME:  replrec.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4e7aebe9

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_READ_BEFORE_CALL_c0000005_replrec.dll!Unknown

BUCKET_ID:  APPLICATION_FAULT_NULL_CLASS_PTR_READ_BEFORE_CALL_replrec+6314d

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:null_class_ptr_read_before_call_c0000005_replrec.dll!unknown

FAILURE_ID_HASH:  {0fe3e937-3154-07c1-51d1-be50efc87f87}

Followup: MachineOwner

Thank you in advance for any suggestion!

---

Can you setup CDC on Replicated Database and not the source database

July 10, 2014, 5:04 pm

≫ Next: How do I disable replication error logs in event viewer?

≪ Previous: SQL Server 2008 Merge Replication crash and thousands of fake updates from subscriber to publisher

$

0

0

I just want to confirm the following:

Can you setup Change Data Capture on the replicated database. (SQL 2008 R2, SQL 2012)

To be clear CDC will not be setup on the source server database, it will only be setup on the replicated database.

Everything I've read so far says you can but there are pit falls and probably is not a good idea.

What are the pros and cons?

What is best practice.

---

How do I disable replication error logs in event viewer?

July 10, 2014, 6:59 am

≫ Next: Merge Replication help

≪ Previous: Can you setup CDC on Replicated Database and not the source database

$

0

0

I have around 100 subscriptions for my publication, frequently subscriptions will be on/off the network. Replication errors are flooding my event viewer. How do I restrict sql server from logging replication errors in SQL server?

---

Vigneswaran S

Merge Replication help

June 30, 2014, 8:27 pm

≫ Next: Merge Replication recreates table for every sync

≪ Previous: How do I disable replication error logs in event viewer?

$

0

0

I'm trying to set up a merge replication between two sql server 2008 instances. The publisher server is running on server 2008 setup as a workgroup, the subscriber is on server 2008 domain. I have been able to get the subscriber to connect to the publisher, bur the initialization fails with 'schema 'xxx' was unable to be propagated to the subscriber'. I have specified the snapshot be placed in a network share and shared it with everyone and given everyone permission to read it. I'm not sure what else to do. This is a test environment, but the live implementation will be between domains without a trust relationship

Any iseas?

Merge Replication recreates table for every sync

June 13, 2012, 7:05 am

≫ Next: After updating to SQL 2012 SP2 merge replication gives error: Invalid column name 'last_local_sentgen'

≪ Previous: Merge Replication help

$

0

0

I have this weird issue with our merge topology.

When adding new tables to the already existing topology and after running the snapshot agent it recreates those new tables every time the sync happens by the merge agent.

And i checked at the publisher sysmergearticles table, the status was set to 6 instead of 2. So it recreates the table everytime.

Let me know if there are any fixes for them. I can think of updating the status back to 1 and check, but want to make sure if this can be done in a producation envrionment without any side effects.

PS: this happens if we add the non-filter or download-only articles to the topology.

---

- Kerobin

After updating to SQL 2012 SP2 merge replication gives error: Invalid column name 'last_local_sentgen'

July 11, 2014, 2:20 pm

≫ Next: Snapshot Replication fails - ALTER TABLE statement conflicted with the FOREIGN KEY constraint

≪ Previous: Merge Replication recreates table for every sync

$

0

0

After updating to SP2 on SQL 2012 merge replication gives this error on all subscriptions:

Error messages:
The merge process could not update the last sent generation sent to the Publisher. If this failure persists, reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201005)
Get help: http://help/MSSQL_REPL-2147201005
Invalid column name 'last_local_sentgen'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207

If I create a new subscription to a new database (not been part of any replication before) it gives the same error.

I also tried to recreate the publisher-part. Did not help.

---

Marcus

Snapshot Replication fails - ALTER TABLE statement conflicted with the FOREIGN KEY constraint

June 14, 2013, 7:39 am

≫ Next: Operand clash

≪ Previous: After updating to SQL 2012 SP2 merge replication gives error: Invalid column name 'last_local_sentgen'

$

0

0

Hi Everyone,

i have a strange problem when using Snapshot Replication on a Microsoft SQL Server 2012 - 11.0.2100.60 (X64) Standard Edition on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

I copy Data from a production-DB in a Test-DB. In "Article properties" I marked Copy foreign key constraints to "False" and ActionIfNameIsInUse to "Delete Data". When I ran the Replication the snapshot were created, but the distribution failed with the Error:

"The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_tbl1?GUID->tbl2?GUID". The conflict occurred in database "Training", table "tbl2", column 'GUID'."

First of all there are no FK's in the Test-Database. Second tbl1 is not part of the Snapshot. Maybe someone can help me out?

Dave

Operand clash

June 14, 2014, 9:39 am

≫ Next: P2P Replication Not working after DDL Chage has been replicated

≪ Previous: Snapshot Replication fails - ALTER TABLE statement conflicted with the FOREIGN KEY constraint

$

0

0

I have merge replication that has been working for 2 years. Recently the replmerge.log contains quite a few of these lines:

CommitBatchedUpdates failed with error Operand type clash: varbinary is incompatible with real

There does not seem to be any holes in my data that I can find. The error message is troubling. Any clue where I should start looking?

---

P2P Replication Not working after DDL Chage has been replicated

July 15, 2014, 2:20 am

≫ Next: error: the publication does not exist

≪ Previous: Operand clash

$

0

0

Hi Guru,

I am using SQL Server 2008. And I have configured the DC DR P2P replication for High availability.

In DC i  had dropped one column. after that my replication is not working i am getting "A DDL change has been replicated error" in replication monitor.

In order to resolve this issue i had tried to drop the same column in DR. But still the replication didn't work.

Please help me to resolve this issue. 

error: the publication does not exist

October 31, 2006, 1:47 pm

≫ Next: Adding Tables after Initializing Subscription from Backup

≪ Previous: P2P Replication Not working after DDL Chage has been replicated

$

0

0

I had a publication that I removed from the Local Publications folder but it still shows up in Replication Monitor (with a red 'X'). No jobs exist related to this publication either.

Everything is working ok, but I can't get rid of this from the Replication monitor.

Any help would be appreciated.

Thanks.

Adding Tables after Initializing Subscription from Backup

June 30, 2014, 12:22 pm

≫ Next: Transactional replication errored out as subscriber is corrupt

≪ Previous: error: the publication does not exist

$

0

0

We have a transaction publication with two subscribers. One was recently re-initialized using a backup. I'm now trying to add tables to the publication. When I do this and generate a snapshot to populate the added tables, the distribution agent ignores the snapshot and continues applying transactions. It then stops when a transaction hits one of the added tables because the "not for replication" identity column option that would have been taken care of by the snapshot isn't there. Is this because the subscription was initialized from a backup and is there a workaround?

System Info: The subscriber and publisher are both SQL 2012 64-bit.

Transactional replication errored out as subscriber is corrupt

July 16, 2014, 4:12 am

≫ Next: Replication Latancy

≪ Previous: Adding Tables after Initializing Subscription from Backup

$

0

0

Hello,

I received errors this am that my subscriber db is corrupt. I am using SQL 2008 R2 SE. I have stopped replication and restoring subscriber from last nights backup. After the restore is done will I be able to set up replication? The data missing will only be few hours.

Thanks

Replication Latancy

July 16, 2014, 11:12 pm

≫ Next: Replicated db & SSRS

≪ Previous: Transactional replication errored out as subscriber is corrupt

$

0

0

Hi All,

I am using transaction replication In my Environment. 
Question: At the time when batches completed from Application team, daily it will take  5  to 10min to apply all commands to replicated database, but from last 2-3 days it is taking  1 to 1 and half hour.
Can anybody suggest what might be the reason?
 
Environment on both servers prod as well as replicated
__________________________<o:p></o:p>

SQL Server 2008 r2 Standard
Windows server 2008r2 enterprise
CPU 64 (Hyper threading Enable)
64 GB Memory<o:p></o:p>