Thanks! That's what I figured, so most likely those sporadic Network errors during the proc call are authentication-related. I've seen a few references to buggy NIC drivers, too, but point...

There are no linked servers involved. They're not failed logins into SQL Server; it's configured to log those, and none appear. The system_health XE session is where we're seeing the...

Just in case you (or another server admin) did this...

Don't pre-create the Network Name resource in the cluster resource group. The installer isn't smart enough to recognize it as "oh,...

Confirmed; CU5 fixed this issue.

Thanks!!

Forgive the double-post here, but I wanted to make sure this was highlighted separately. MS has confirmed to us it's a bug. They claim it's fixed in CU5, though the...

We don't have an official answer from MS yet, but it is looking like a bug. And I just figured out a big key to it: Common Table Expressions.

Let me...

Yeah, I tried something simple like that, too... and it worked fine. So I know part of the problem is the "real" code. It's a lot more complex, and given...

Well, that does confirm or at least support what I'd already learned, that "rpc" is useless, according to anyone else that wondered and checked it out. But I'm still left...

That was a good idea. But sadly, it doesn't appear to be the case, either. I just tried that; didn't need "rpc".

SERVERA -> SERVERB -> SERVERC

A procedure on SERVERC simpy...

Excellent question! I hadn't thought about it before, actually. Unfortunately it didn't yield an answer, but it does clarify my question. So I tested.

I created a test procedure on a...

If you're not concerned about security, and just want the "least administrative effort"...

If there's no real risk in allowing him to read every single table in the database - including...

I hate to ask the "is it plugged in" question but... did you...