View Complete Post
I got this error in transactional replication in sql server
Error:The process could not execute 'sp_repldone/sp_replcounters' on 'FS001XSSQL110'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
The log scan number (54862:18189:10) passed to log scan in database 'Affinity' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the
publication. Otherwise, restore from backup if the problem results in a failure during startup. (Source: MSSQLServer, Error number: 9003)
Get help: http://help/9003
The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
Get help: http://help/MSSQL_REPL22017
The process could not execute 'sp_repldone/sp_replcounters' on 'FS001XSSQL110'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037
this is what i am getting when i viewed the log reader agent in replication monitor.
Tx Replication is giving an error
if @@trancount > 0 rollback tran
(Transaction sequence number: 0x00001E880000202E000800000000, Command ID: 1)
2010-09-16 20:10:17.543 Microsoft SQL Server Log Reader Agent 10.0.2531.0
2010-09-16 20:10:17.597 Copyright (c) 2008 Microsoft Corporation
2010-09-16 20:10:17.622 Microsoft SQL Server Replication Agent: logread
2010-09-16 20:10:17.663 The timestamps prepended to the output lines are expressed in terms of UTC time.
2010-09-16 20:10:17.717 User-specified agent parameter values:
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>
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.
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
I am setup a new DB replication, during which I discover that there is no place to name the agent jobs for publisher, snapshot and subscriber, system wizard will name these jobs for me. But these name are ramdon and I wish they can be finalized before setup.
Is there any way to do this work?
I have tried, 1) rename them after setup, but it seems risky since internally replication will interact with these jobs through name. 2) Setup place holder jobs before replication setup, and let new jobs overwrite these jobs, it does not work as wished
and some of the job setting is not applied to new job.
Could any one help me out? And it will be great if your way can be done programmatically.
When I try to set up a transactional replication, setting it up works fine, but then I get an error from the snapshot assistant:
the execution stops at the table sysdiagrams with the error message that the filed „definition“ uses the type varbinary(max).
There was no specific error code, i.e. the error code displayed was '0'
If I try to set up a snapshot replication the sysdiagrams table is not included and it runs through just fine.