I'm not familiar with this error at all. Can you post your procedure code?

If I understand the functionality right I think it's the "force order" hint. But as theSQLGuru said: just use it if you really know what you're doing.

don't think so 🙁

Please provide a DDL script for your tables as well as some sample data and the expected result.

Please have a look here: http://www.sqlservercentral.com/articles/Best+Practices/61537/

not sure I understand right.

In Always On you have 1 primary instance and up to 4 secondary instances.

Whereas only the primary is writeable, all the secondarys are readable.

You can...

As far as I've seen you can connect from a Management Studio 2008 to a SQL 2012 instance.

The object explorer might throw some errors when expanding the different trees but...

As you already identified the SELECT statement check the indexes on all referenced tables.

Don't forget to check the overall server performance. SOS_SCHEDULER_YIELD could be a hint that the processor is...

Not sure if I understand you right.

If you fear that the snapshot does changes on the tables on the subscriber, this depends on the snapthot settings.

First, have the table...

let's do it step by step.

Replication tries to copy a record from publisher to subscriber. If it tells you a PK violation one of the records to be transferred already...

There are many reasons why the performance is different.

Without getting in detail I would say investigate in 2 directions:

1) network traffic

Is the distribution agent slow because it cannot read...

You could add the column without a default value, that usually works quite quick.

Afterwards you could update the column in chunks of for example 1 Mio rows.

I did some testing and figured it out.

It does not matter if you initialized the subscribers using restore a database, snapshot or whatever.

As we know: initializing the subscription using initialize...

I think I have bad news :ermm: I found this note in books online (/http://technet.microsoft.com/en-us/library/ms151705.aspx):

When restoring a backup, you must ensure that the backup came from the Publisher if you...

Hi,

same problem here but no solution too 🙁

At least I can commit that there might be something wrong with Microsoft's whitepapers.

I have an Always On Group on SQL...

Then activate trace flag 1222 for the whole server.

When the next deadlock occurs, have a look at the sql server log file. You will see the deadlock information quite exactly.