Thanks Gail. I obviously didn't read the original question well enough. Thanks for catching that.

Yes, if you have a good full backup (you may want to restore that full on your test server and run DBCC CheckDB to ensure it's clean), start with restoring...

Oh...and, if you ever run into instances that participate in clustering or AlwaysOn, the default "virtual" accounts are a MASSIVE headache to get to work. Domain accounts (and using the...

I must have misread that part in the MSDN article, or they're referring to something else.
I've always used a domain account, simply because its domain permissions (which would be...

Good additional reading can be found here: https://dba.stackexchange.com/questions/165363/recommended-sql-server-service-accounts
It boils down to what is best in your environment. I've worked at several organizations, and I always advocate for the...

It also depends on whether the physical drives are going to be separated into logical drives in Windows. For example, you could carve out 100 GB on the D:\ for...

DOH!!! I was scrolling the main screen and not the code window. Thanks Lynn for the catch...I can see it now.

You're missing "AS" in the "CREATE PROCEDURE" statement.

It sounds like the databases are still functional and you just can't login to the servers, yes? Assuming that is the case, on node 3, fail the databases over to...

Can you clarify what you're asking and what you're trying to accomplish? In its current form, the question doesn't really make sense.
If you only have SSMS onsite, where are...

If you have SSMS and can connect to the instance, execute @@VERSION. That will tell you definitively whether or not the instance is Enterprise.

The ABC\AppTeam_Test group has server level permission, and thus will be able to create (restore) a database, but since the group does not have specific database level permission, that is...

Yes...sort of. Assuming you start out with the databases on the 2012 instance, and set it as primary, you can restore the database(s) to the 2014 and 2016 instances and...

I found the problem--and, as usual, the problem had nothing to do with the error message generated in the applications. The problem was an incorrect join on a third...

The join is not occuring on the oracle server at all. It is occurring with a linked server, and if I leave out the table from Server1, I get...