>>Raising the max server memory on each instance would be a sensible option

Yes, I understand your line of thinking, however, the failures *abruptly* started around 02/25/2015. Prior to that date,...

Yes. We are using:

(128 GB - 12 GB) / 9 instances = ~12 GB max memory for each instance

We took this route because we did not want to overcommit RAM...

All three nodes are essentially identical blades with 128 GB of RAM. I don't have access to the servers from home, but, as I recall (per Microsoft recommendation), we have...

Is DBSophic Qure Profiler still free? I am...

I ran across a copy of your "SQL Server 2012 Query Performance Tuning" book this morning. This looks...

I didn't know about the Ford/Davidson book http://www.red-gate.com/community/books/dynamic-management-views. I...

We use our own custom PowerShell script (scheduled via Task Scheduler, not SQL Server Agent) to backup our databases because we have 40+ instances spread across several clusters, and it...

I'd still like to hear from someone who has actually created a (physical or virtual) cluster using SMB shares.

I ran across this link, in case anyone is looking for the same kind of information.

“Yes, today you can create an entire cluster based on SMB File shares.”

http://www.pythian.com/blog/smb-file-share-and-sql-server-an-option-to-consider/

By the way, we have been using 2012 for over a year, and our software is patched regularly.

We (3 DBAs) have not had any issues with our install.

>>Are all the servers in the same location?

Yes.

>>Are you running each SQL node on separate VM hosts?

We would prefer to do so.

>>http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959

Actually, that link is why I posted...

We never go it to work. We opened a call with Microsoft, and, to my dismay, Microsoft told me that this is unsupported software. Way to listen to your customers,...

We migrated to fresh hardware and fresh Reporting Services databases for SQL Server 2012. When I copied the Reporting Services reports to the new SQL Server 2012 instance, I noticed...

I'm not sure if this helped or not (because I found some additional links posted below at about the same time), but the description matched my error and the syntax...