Probably the best approach here is to use UNION ALL. Then the query would be the same query, repeated, over and over again, for each of your databases.

My question is,...

I agree with LinksUp. You need to use the modern syntax. That old method, while still partially supported (you can't do OUTER JOIN using the old mechanism any more), it's...

I'm unclear why you would do this using SSIS? If you're just polling the instances for connectivity, you could easily do this through T-SQL or Powershell. Building SSIS is an...

I think it's likely that you're going to need some admin privileges to get things worked out. You won't need them permanently, but I don't think you have enough currently...

At this point, you might be better served by uninstalling and reinstalling SQL Server. Go slow. Understand each step, especially when you get to the naming of the instances and...

Ah. I really didn't have a clue. That's why I went to people who know more than I do.

This isn't something I've done, but according to Joey D'Antoni, there's a chance that someone has enabled automatic backups at the VM level, including SQL Server. So it's doing backups...

That's not something I've normally seen. Ever. I'll see if I can track someone down that knows what this might be. You've eliminated any other third party backup from within...

Yeah, only the compile values will ever be in cache. If you need the run-time values, you have to capture them using some mechanism.

Extended Events are much safer than trace...

Steve Jones - SSC Editor (3/24/2016)

WayneS (3/24/2016)

Yes it does... even those that speak frequently. I know of a fellow threadizen that is...

But, but, but, we've ALWAYS done it that way.

There's nothing wrong with triggers... used appropriately. Same thing goes for just about every other object within SQL Server (except multi-statement table-valued user-defined functions, those things are pure EVIL and...

With the execution plan it'll be easier, but just looking at the query and the indexes, it can't use any of those indexes because the WHERE clause filters on Invalid...

The query that was used to generate the execution plan is stored with the plan. So getting a runnable query is just a matter of retrieving that information. Same thing...

But, something you've done or are doing on your server has grown the tempdb out to this size. Unless you know for certain what that was and that it won't...