I have an issue with @filter_clause parameter of sp_addarticle procedure. I try to set a very long filter value (about 10000 symbols), and then i have an error:

First message are different when i change filter value and it looks like @filter_clause parameter has an restrinction on the length.

Can i avoid this error?

Additionaly this procedure has parameter - @filter, and i think that error occurs when sp_addarticle trying to create filter procedure.

Can i create filter procedure manually and set it to @filter parameter, is this the same as setting @filter_clause parameter?

After moving to new servers with SQL 2012 I'm tasked with configuring SQL CE 3.5 merge replication through a separate IIS7 server.

How do I install SQL Server 2012 replication compontents on the IIS server?

When selecting the feature "SQL Server Replication" the installer includes the full database engine, how do I install just the components needed to install SSCEServerTools?

Thanks,

Fredrik

Hello all,

I have a SQL Server 2008 instance that runs on failover cluster with 2 nodes, I have also set up push transactional replication that goes to a different server.  The instance in the cluster is both the publisher and distributor.  Everything works great when the cluster is in node 1, however if the cluster fails over to node 2 for whatever reason (including a manual switch) the replica does not work.  Specifically the distribution, log reader, and queue reader jobs will not start and give the following error:

Executed as user: XX\XXXXXX. A required privilege is not held by the client.  The step failed.

If the cluster is then switched over to node 1 the replica starts up just fine and works normally.  Both the SQL Server Service and SQL Agent Service run as the same domain account which is a system administrator.  The startup accounts have not been changed and the snapshot folder is shared and resides in a cluster drive.  Also all other SQL Agent jobs run just fine in node 2, the only problem is with the replica starting up.  

Any help would be greatly appreciated.

I'm running heterogenous replication between Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit and SQL Server 2008 R2 10.50.2500.0 SP1 Enterprise Edition (64-bit). I have found a situation where the Log Reader Agent appears to stall. If I stop the log reader agent and restart it all of a sudden appears to complete all task and log all the activity it has performed. I have full logging on the log reader agent to file and a capture of the agent window after restarting. I've attached 2 diagrams of the monitor; one before restarting the log reader agent and one after restarting. I've also embedded the log file after the images and the point in the log file markedWAS HUNG HERE is where I restarted the log reader agent. This is a pretty serious issue that I need resolved as soon as possible, thanks.

 publisher                      publisher_db                   entry_time              tran_count  cmd_count   cmd_2_tran_ratio
 ------------------------------ ------------------------------ ----------------------- ----------- ----------- ----------------       CRM                            distribution                   2013-01-11 00:32:00.000           1      131526        131526.50
 CRM                            distribution                   2013-01-11 05:39:00.000           2       11395          5698.00
 CRM                            distribution                   2013-01-11 05:40:00.000          12        2437           203.58
 CRM                            distribution                   2013-01-11 05:51:00.000           1           1             1.50

 publisher_db                   article                        entry_time              cmd_count  
 ------------------------------ ------------------------------ ----------------------- -----------

 distribution                   PROV_TPL_CURRENT               2013-01-11 00:00:00.000           1
 distribution                   PROV_TPL_CURRENT               2013-01-11 00:30:00.000           1
 distribution                   PROV_TPL_CURRENT               2013-01-11 05:39:00.000       11395
 distribution                   PROV_TPL_CURRENT               2013-01-11 05:40:00.000          10
 distribution                   PROV_TPL_CURRENT               2013-01-11 05:51:00.000           1

 distribution                   PROV_TVL_CURRENT               2013-01-11 00:32:00.000      131526
 distribution                   PROV_TVL_CURRENT               2013-01-11 05:40:00.000        2427

David Ryan

Before Restarting Agent

After Restarting Agent ( roughly 5 hours later)

******************** STATISTICS SINCE AGENT STARTED ***************************
01-11-2013 00:29:23

Execution time (ms): 42808624
Work time (ms): 417538
Distribute Repl Cmds Time(ms): 144087
Fetch time(ms): 4294965940
Repldone time (ms): 138248
Write time (ms): 2838
  Num Trans: 46  Num Trans/Sec: 0.110170
  Num Cmds: 50197  Num Cmds/Sec: 120.221393

LoadReplCmds time(ms): 277883

Publisher status requests          (ms): 43973
 GetPublisherStatus             (ms): 15
 GetChangeStatus                (ms): 43958
Publisher synchronization requests (ms): 230307
 PollBegin                      (ms): 149972
 PollSync                       (ms): 0
 PollEnd                        (ms): 80335
Publisher data queries             (ms): 717
 SyncInit                       (ms): 0
 SyncDone                       (ms): 0
 InReconciliation               (ms): 0
 Change                         (ms): 501
 RowCount                       (ms): 0
 TracerToken                    (ms): 216
Distribution thread requests       (ms): 1590
 SyncInit                       (ms): 0
 SyncDone                       (ms): 0
 RowCount                       (ms): 0
 TracerToken                    (ms): 0
 Change                         (ms): 1590
 Commit                         (ms): 0
Distributor queries                (ms): 15
 SetSubStateActive              (ms): 0
 SetSubStateInitiated           (ms): 0
 GetDistributorFlushTime        (ms): 15
Log Reader processing              (ms): 1266
 SyncInit                       (ms): 0
 SyncDone                       (ms): 0
 InReconciliation               (ms): 0
 RowCount                       (ms): 0
 TracerToken                    (ms): 32
 Change processing              (ms): 1093
 SetupCache                     (ms): 141

SyncInit Total                     (ms): 0
 SyncInit request to publisher  (ms): 0
 SetSubStateInitiated query     (ms): 0
 SyncInit distribution thread   (ms): 0
 SyncInit log reader processing (ms): 0
SyncDone Total                     (ms): 0
 SyncDone request to publisher  (ms): 0
 SetSubStateActive query        (ms): 0
 SyncDone distribution thread   (ms): 0
 SyncDone log reader processing (ms): 0
InReconciliation Total             (ms): 0
 SyncDone request to publisher  (ms): 0
 InRecon log reader processing  (ms): 0
RowCount Total                     (ms): 0
 RowCount request to publisher  (ms): 0
 RowCount distribution thread   (ms): 0
 RowCount log reader processing (ms): 0
TracerToken Total                  (ms): 248
 Tracer request to publisher    (ms): 216
 Tracer distribution thread     (ms): 0
 Tracer log reader processing   (ms): 32
Change Total                       (ms): 3184
 Change request to publisher    (ms): 501
 Change distribution thread     (ms): 1590
 Gather change data             (ms): 796
 Format change commands         (ms): 297
SetupCache                         (ms): 141

Repldone time                      (ms): 138248

Publisher synchronization requests (ms): 138248
 PollSync                       (ms): 0
    PollEnd                        (ms): 138248

SyncDone Total                     (ms): 0
 SyncDone request to publisher  (ms): 0
 SetSubStateActive              (ms): 0
 SyncDone distribution thread   (ms): 0
 SyncDone log reader processing (ms): 0
*******************************************************************************

2013-01-11 06:30:00.582 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 06:30:00.751 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x00000000000000000035, '0x00000000000000000035'.'.
2013-01-11 06:31:03.484 Status: 16384, code: 20007, text: 'No replicated transactions are available.'.
2013-01-11 06:32:07.518 Status: 16384, code: 20007, text: 'No replicated transactions are available.'.
2013-01-11 06:32:34.373 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.

WAS HUNG HERE

2013-01-11 11:39:05.134 Microsoft SQL Server Log Reader Agent 10.50.2500.0
2013-01-11 11:39:05.148 Copyright (c) 2008 Microsoft Corporation
2013-01-11 11:39:05.149 Microsoft SQL Server Replication Agent: logread
2013-01-11 11:39:05.150
2013-01-11 11:39:05.150 The timestamps prepended to the output lines are expressed in terms of UTC time.
2013-01-11 11:39:05.151 User-specified agent parameter values:
   -Publisher CRM
   -Distributor RTN1
   -DistributorSecurityMode 1
   -Continuous
   -output d:\repllog\crm_logreader.txt
   -outputverboselevel 3
   -XJOBID 0xF165ADD24A0ECE49B45BCFBE12CAA01A
   -XJOBNAME CRM-CRM-1
   -XSTEPID 2
   -XSUBSYSTEM LogReader
   -XSERVER CRM
   -XCMDLINE 0
   -XCancelEventHandle 0000000000000774
   -XParentProcessHandle 00000000000006E8
2013-01-11 11:39:05.209 Parameter values obtained from agent profile:
   -pollinginterval 2000
   -historyverboselevel 2
   -logintimeout 15
   -querytimeout 1800
   -readbatchsize 500
   -readbatchsize 500000
2013-01-11 11:39:05.211 Connecting to OLE DB Publisher at datasource: 'RTN1', location: '', catalog: 'distribution', providerstring: '' using provider 'SQLNCLI10'
2013-01-11 11:39:05.214 OLE DB Publisher: RTN1
   DBMS: Microsoft SQL Server
   Version: 10.50.2500
   catalog name: distribution
   user name: HTMS\logagent
   API conformance: 0
   SQL conformance: 0
   transaction capable: 1
   read only: F
   identifier quote char: "
   non_nullable_columns: 0
   owner usage: 15
   max table name len: 128
   max column name len: 128
   need long data len:
   max columns in table: 1000
   max columns in index: 16
   max char literal len: 131072
   max statement len: 131072
   max row size: 131072
2013-01-11 11:39:06.394 OLE DB Publisher: RTN1
   DBMS: Microsoft SQL Server
   Version: 10.50.2500
   catalog name: distribution
   user name: HTMS\logagent
   API conformance: 0
   SQL conformance: 0
   transaction capable: 1
   read only: F
   identifier quote char: "
   non_nullable_columns: 0
   owner usage: 15
   max table name len: 128
   max column name len: 128
   need long data len:
   max columns in table: 1000
   max columns in index: 16
   max char literal len: 131072
   max statement len: 131072
   max row size: 131072
2013-01-11 11:39:06.395 OLE DB Publisher 'RTN1': select @@SERVERNAME
2013-01-11 11:39:06.397 Connecting to OLE DB DISTOLE at datasource: 'RTN1', location: '', catalog: 'distribution', providerstring: '' using provider 'SQLNCLI10'
2013-01-11 11:39:06.402 OLE DB DISTOLE: RTN1
   DBMS: Microsoft SQL Server
   Version: 10.50.2500
   catalog name: distribution
   user name: HTMS\logagent
   API conformance: 0
   SQL conformance: 0
   transaction capable: 1
   read only: F
   identifier quote char: "
   non_nullable_columns: 0
   owner usage: 15
   max table name len: 128
   max column name len: 128
   need long data len:
   max columns in table: 1000
   max columns in index: 16
   max char literal len: 131072
   max statement len: 131072
   max row size: 131072
2013-01-11 11:39:06.403 OLE DB DISTOLE: RTN1
   DBMS: Microsoft SQL Server
   Version: 10.50.2500
   catalog name: distribution
   user name: HTMS\logagent
   API conformance: 0
   SQL conformance: 0
   transaction capable: 1
   read only: F
   identifier quote char: "
   non_nullable_columns: 0
   owner usage: 15
   max table name len: 128
   max column name len: 128
   need long data len:
   max columns in table: 1000
   max columns in index: 16
   max char literal len: 131072
   max statement len: 131072
   max row size: 131072
2013-01-11 11:39:06.403 OLE DB DISTOLE 'RTN1': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'CRM')
2013-01-11 11:39:06.406 OLE DB Publisher 'RTN1': sp_MSgetversion
2013-01-11 11:39:06.408 Status: 4096, code: 20024, text: 'Initializing'.
2013-01-11 11:39:06.409 The agent is running. Use Replication Monitor to view the details of this agent session.
2013-01-11 11:39:06.410 OLE DB DISTOLE 'RTN1': sp_MSget_last_transaction @publisher_id = 2, @publisher_db = N'distribution', @for_truncate = 0x0
2013-01-11 11:39:06.411 OLE DB DISTOLE 'RTN1': sp_MSquery_syncstates 2, N'distribution'
2013-01-11 11:39:07.585 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:39:07.677 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x00000000000000000037, '0x00000000000000000037'.'.
2013-01-11 11:39:08.721 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:16.254 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 11394 commands, 1 xacts.  Last xact: 0x00000000000000000038, '0x00000000000000000038'.'.
2013-01-11 11:40:16.569 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:18.548 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1427 commands, 1 xacts.  Last xact: 0x00000000000000000039, '0x00000000000000000039'.'.
2013-01-11 11:40:18.569 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:18.589 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x0000000000000000003a, '0x0000000000000000003a'.'.
2013-01-11 11:40:18.610 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:18.629 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x0000000000000000003b, '0x0000000000000000003b'.'.
2013-01-11 11:40:20.432 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:20.887 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1000 commands, 1 xacts.  Last xact: 0x0000000000000000003c, '0x0000000000000000003c'.'.
2013-01-11 11:40:20.912 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:20.932 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x0000000000000000003d, '0x0000000000000000003d'.'.
2013-01-11 11:40:20.952 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:20.975 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x0000000000000000003e, '0x0000000000000000003e'.'.
2013-01-11 11:40:20.996 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:21.013 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x0000000000000000003f, '0x0000000000000000003f'.'.
2013-01-11 11:40:21.040 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:21.059 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x00000000000000000040, '0x00000000000000000040'.'.
2013-01-11 11:40:21.081 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:21.098 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x00000000000000000041, '0x00000000000000000041'.'.
2013-01-11 11:40:21.119 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:21.137 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x00000000000000000042, '0x00000000000000000042'.'.
2013-01-11 11:40:21.158 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:21.182 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x00000000000000000043, '0x00000000000000000043'.'.
2013-01-11 11:40:21.206 Status: 4, code: 6002, text: 'Committed batch to distribution database.'.
2013-01-11 11:40:21.223 Status: 4, code: 22021, text: 'Batch committed.  Batch consisted of 1 commands, 1 xacts.  Last xact: 0x00000000000000000044, '0x00000000000000000044'.'.
2013-01-11 11:41:22.901 Status: 16384, code: 20007, text: 'No replicated transactions are available.'.

I have a column-level transactional replication. Usually, I use the following query to check if a column is replicated or not.

selectis_replicated

  fromsys.columns

 wherename='Column_Name'

This works most of the time.

However, after increasing the width of a published column, the is_replicated value is set to 0. However, in SSMS the column still shows as enabled for replication.

I ran an update on the column and found that data is replicated to the subscriber. So replication is working fine. Only the is_replicated flag is set to zero.

In this case, what’s the true test to check if a column is replicated or not? (I need a T-SQL code to verify this to be used in one of my stored procedures.)

Note: People who want to dive deep into this, I found a system view, syncobj_0xNNNNNNNNN, created when I altered the column. I did some research and found that the view is used to replication thenceforth. However, I am not bothered about this view much, as long as replication works fine.

Hi All,

I'm in the process of creating some Replication Publishers for all our sites. I will have 1 subscriber (for now) that will collect the data from the Publishers (8 databases). What I'd like to know is there a way to tell/set the  publisher with a siteID without having to change the database structure.

For example for the Subscriber db I setup those tables with a SiteId field.  When the publisher pushes the data to the subscriber, I'd like the publisher also send the siteID of the site. Is there a way to do this without changing the db structure? If not and I need to change the structure, should I make the siteid as part of the primary key of each table? Is there any draw backs to doing so?

Thanks for any help that you can provide.

Hi

We have oracle 11g (publisher)-> SQL 2008 R2(Subscriber) transaction replication set up; we need the real time data from publisher to Subscriber. We have done all the performance improvement set up provided by Microsoft(like oracle gateway, xact jobs frequency, polling interval , increase the priority of logreader.)

Till certain Load the data transfer is realtime but then it moves into Batch Processing mode and log reader shows messageBatch Processing in progress XXX commands with 0 transactions..." and every batch takes 1-2 hours to process and we dont have real time data.

I have seen similar post but there was not any solution to this question.

Vivek Patle Sum Total Systems

In transactional replication, is it possible to use the option @identityrangemanagementoption = auto without having updateable subscriptions.  We believe we have a legitimate business reason for doing this, and see no technical reason why we shouldn't be able to, but attempting to do so from a script gives us an error telling us we need to allow updateable subscriptions.

The reason we want to run this combination is that we are replicating from a live database (the publisher) to a BCP database (the subscriber). It's possible that, outside of replication, changes may be made to the BCP database (for example during routine tests we might log in to the BCP server to check that it is working, which will automatically trigger new log records being added in the BCP database). There is absolutely no need for such changes to be replicated back to production - the intended replication is one-way only to BCP, so there's no need for the overhead of having this 'reverse' replication enabled (and we also don't want the extra columns added to the replicated database tables that happens as soon as we switch on updateable subscriptions.   Hence we do not want updateable subscriptions.

On the other hand, clearly we need to make sure that if extra records are added to the BCP database from outside replication, the identity columns don't clash with anything propagated through replication. Hence we believe we need the automatic identity management.

Is there any way to achieve this?

Thanks

I have users getting an error when trying to delete a business contact or account.  "error converting data type int to smallint".  I know it is a sql error, but have been unable to find the field causing the problem.  You can make changes to the contact, just not delete it.

Any ideas on how to fix this would be appreciated.

Thanks.

Hi all,

we have a bizarre situation...we have about 15 publications and about 30 subscriber for each of them. Yesterday we re-ran the generic snapshot and after that all the partitioned snapshot agents. 

After that 4 of the 15 publications had a bizarre behavior. The value of the sentgen column of the subscriber of these 4 publications is 1 and this seems to mean that every time a sync takes place the subscriber has to cycle through all of his records for the upload portion of the sync (a long time is being spent because of this).

Does anyone have some idea?

We meet an issue that the undistributed commands is very large and keep increasing.

Here is a background:

DBA stopped the replication to implement a solution to fix the incorrect 'del_cmd' for some articles by using sp_addarticle.

It was stopped no less than 24h, the undistributed commands was very large and keep increasing after starting replication again. While comparing the total count and min/max timestamp from publication and subscription, it looks all of the data should be replicated has already replicated without issue.

Get some tips that maybe a bug exists on such operation from SQL Server 2005 to SQL Server 2008, we restarted distribution agent, and the undistributed commands was cleared.

Since the restarted action was done on Friday, and I see the undistributed commands is queued again on Monday after the weekends. I am confusing that if it is really reflected the undistributed commands now....

How can I know which transactions or commands are being replicated, and what kind of commands are waiting for to be subscriber?

Best Regards, Lisa J

I have a transaction database and need to be sync up constantly to a reporting database.  I've tried Mirroring with Snapshot in sql08r2.  Snapshot works great until there are long running queries as well as queries requires little latencies.  There is no medium ground in this application to change the snapshot frequency to satisfy both long running and real time queries.

So, I need to find the best way to replicate data.  Currently, there is a transaction repl., which I think is overkill, because, the need is a one way replication.  secondly, there are frequent slow down (liked 1 update /sec ) on the subscriber table as the transactions are applying from the publishers.

how best to build a real time one way replication, which can handle millions of updates in a day and be able to refresh to subscriber right away in real time? 

-- IBM has jobs for USA employee to work oversea (India) and get their wages.

I have a transactional replication with 2 subscriptions: 

1 is located at the same instance as the publisher, the other is the remote server. The distributor is at another instance. Both publisher and distributor are SQL Server 2005, the local subscriber is SQL Server 2005 too, the remote subscriber is SQL Server 2008.

we have a purge job running every day to purge the data older than 8 days in publisher.

The replication is working fine till the publisher and distributor migrated to another data center. After migration, it is detected that the data were purged periodically because of the 'del_cmd' were configured as default value to allow delivery delete statement.

This incorrect configuration was corrected later, and after monitoring for some time, we dont find the delete is still replicated. while it seems that the data is decreasing on the local subscriber since after the distributor agent restarted 3 days ago when there was a big queue of undistributed commands to remote subscriber.

Does anyone have any idea on this strange situation?

Thanks a lot

Best Regards, Lisa J

Merge Replication any ideas please?

I have a table with, say 2000 rows some 500 of these are rows which are updated by every user when their application closes, clearly this causes a lot of conflicts which are unnecessary because each user will update when they run the app.

Inserts MUST be passed to every user

jnc

Hi,
I have a sql server 2005 enterprise server (on 64 bit win 2003 server)  with transactional replication in place. Intermittently I get the following error.

TCP Provider: The specified network name is no longer available. (Source: MSSQLServer, Error number: 64)
Get help: http://help/64

Communication link failure (Source: MSSQLServer, Error number: 64)
Get help: http://help/64

The process could not execute 'sp_replcmds' on 'Server Name' . (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037

The log reader agent fails. Can anyone out there help me to fix this issue or to find more information on this error.

Cheers,
Vije 

Hello everyone,

I come up with a problem when I tried to configure Peer-to-Peer Transactional Replication on my environment. Following is the steps how I did this:

1. Create a Database in SQL, say DBSource, with one table that has a column as Primary Key. And add some records.

2. Backup this Database and restore to SQL Server with a new name, say DBDestination, now I get two dbs with the same schema.

3. Create a new Publication based on DBSource, and a Subscription based on DBDestination and the Publication created.

4. When I go to the properties of the Publication I just created, the "Allow Peer-to-Peer Subscriptions" option is grayed out and not selectable. Any ideas?

There is one more problem that when I right-click the publication I created, there's no "Configure Peer-to-Peer Topology" option in the popup menu. Is there some other component I need to install or some feature I need to enable?

Any advice is highly appreciated. Thanks very much in advance.

Cavendish Feng

I am working with setting up Replication Publishers in AlwaysOn Availability Groups, and after running sp_redirect_publisher, there is a new stored procedure in SQL 2012 called sys.sp_validate_replica_hosts_as_publishers that validates your configuration is correct.  Occording to BOL this procedure creates a temporary linked server to the nodes in the Availability Group and validates they are suitable for handling replication and uses the windows credentials of who is currently logged in.  I am logged in as a windows account that is both domain admin as well as SQL sysadmin on all my instances but keep getting an error when running this procedure.

Here is the code I am running from the distributor

declare @redirected_publisher sysname
exec sys.sp_validate_replica_hosts_as_publishers 
     @original_publisher = 'SQL1', 
     @publisher_db = 'TestPub', 
     @redirected_publisher = @redirected_publisher output
select @redirected_publisher

I am getting the following error.  I am running SQL 2012 SP1 and am wondering is I am missing some sort of security configuration or if this is a bug that needs to be filed

Msg 21892, Level 16, State 1, Procedure sp_hadr_validate_replica_hosts_as_publishers, Line 60
Unable to query sys.availability_replicas at the availability group primary associated with virtual network name 'CHAD-PUB-AGList' for the server names of the member replicas: error = 18456, error message = Error 18456, Level 14, State 1, Message: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'..',

Convert DTS to SSIS | Document SSIS | 30+ SSIS Tasks | Real-time SSIS Monitoring | Quick Starts | BI Blitz

Hi All,

We are using Transactional Replication, Can we maintain publisher, distributor in 2005 and subscriber in 2008? Is it possible to maintain or not.

in case if it's possible, please explain how we can maintain it.

Raveendra