http://blogs.microsoft.com/blog/2016/03/07/announcing-sql-server-on-linux/

I did a bit of testing in my environment and I believe this also requires VIEW ANY DEFINITION permissions on the instance. This MSDN article seems to corroborate that.

Does the [Obfuscated\User] account have sufficient privileges to query the DMVs and return results?

Thanks. That is exactly what we are doing today for the one to one relationship in mirroring between PRD and DR. It works well and we can "replay"...

With 2.6 billion rows, be mindful of those INT datatypes. You have probably already considered that, just throwing it out there.

We use only DBA-created databases in our environment and the only permission granted to the Sharepoint account is the db_owner role in each database. We do not grant securityadmin...

I might also recommend checking the max degree of parallelism across the instances. If each instance has numerous queries constantly going parallel, this will quickly consume whatever CPUs are...

My thought is that the slowdown is occurring either as the backup traverses the network or on the storage on which it is being created. Is that SAN storage...

You have most likely already verified this, but do you have another other database maintenance running during the backup window? Any bulk imports, ETL, etc.?

No apology necessary, these configurations can be confusing the first few times. Ask me how I know.

But yes, you can either change the connection and hand it off to...

No, before the package even gets to the point of reading the config values from the configuration database, it has to know on what server.database that information resides. So...

I would not say that it is your problem per se, but it is a problem.

Basically, say you are making the connection to the dev configuration table using a connection...

I would recommend you take a look at some of the information_schema views. Specifically:

select * from information_schema.tables

select * from information_schema.columns

Well, on an OLTP system, typically the cost of splitting the query across several CPUs, executing, then bringing the results back together would actually be a more expensive (time mainly)...

My recommendation for a server with 16 CPUs is no more than half, so:

sp_configure 'max degree of parallelism',8

reconfigure with override

If you examine the wait stats on your server, I suspect...