And the execution plan for the update query.

There's no way to simply guess what is happening. You have to gather metrics to understand and the one metric that describes how...

Yep. Sachin has it right. Once the log chain is broken, you have to reset.

Execution plans to understand why this is occurring would be helpful.

Not precisely. It's just a question of running a query against the database or server through a SQL Agent Job. There isn't that much to it. Agent can run independent...

You should be able to do anything with other mechanisms without having to use SSIS. I'm really not aware of anyone who uses SSIS as a monitoring tool. I'll be...

From what I can tell, the statement complete is just the definition of the prepared statement that the sp_execute command is going to run. There are differences between the slow...

I go to hit reply and see Luis has not only answered the question (better than I was going to), but has also raised my biggest concern, it doesn't sound...

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...