First off I would have posted your question in the SQL 2012 forum as Always on Availability Groups are only supported by SQL 2012.

Anyway. I am in the process...

Each option has its own merits.

For example Always on supports active secondaries so you can support read\write operations on one instance and read operation only on others allowing...

This looks very like the type of code LYNQ \ Nhibernate generates. It may not be that someone has coded a cursor but the application is generating cursor code.

Providing the windows login is created on both the principal and the seconday then upon failover the should work. There is no dependancy on the SID with windows logins...

Sorry I had skimmed through your question and thought it said over a specifc size. Yes, as mentioned in the other reply perfoming index maintenance on very small indexes...

SQLSteve (10/10/2013)

---

I am going to incorporate into my reindexing script that any index under a certain size should be ignored.

Whats the rule of thumb for this? There must be a...

Adding a new subscriber is a different situation. You would need to generate a new snapshot but you do not need to reinitialise the exiting subscribers as they will...

In theory the statistics and indexes should be fine at a logical level as they have not changed when the VM was moved. The physical disk allocation may be...

You can't, as the message explains the publication which includes all articles has to be re-initialised which in turn will generally mean creating a new snapshot depending on how old...

Personally I would start by looking at the waits on the system and trying to identify if there is any particular wait type that is causing the problem, this will...

You can remove the files from the update cache folder as these are generally install files left over when applying a service pack or a cumulative update.

PS, worth mentioning that its been a while since I did this last, so may have missed something, but that should cover what you need.

Not difficult to do,

1. first within failover manager remove NodeA as a possible owner from the cluster group for your SQL Instances.

2. Then remove the...

The mail agent only runs when it has emails to process, you can see that here:

select * from msdb.dbo.sysmail_log

You can then check emails that were sent here:

select * from...

The easiest way is to launch replication monitor, connect to the distributor and then view each of the agent types in the "Agents" tab.