To get radical differences in behavior, something has to be different. Did you check the execution plans as I suggested? Are they different? If so, are the parameters that compiled...

Generally, just delete the data. It's the best approach. Sometimes, breaking the data into chunks can help. Here's an article to give you some ideas.

There is absolutely ZERO way to tune a query that is selecting all columns and all rows. You can't do it.

What you can do, is tune the hardware...

Sure, this kind of thing happens all the time. Have you compared execution plans, the one running fast the one running slowly? Are they the same? Probably not. What are...

When you create a stored procedure, it doesn't validate the existence of objects, just syntax. It's when you execute the code that you hit the problems. So yeah, CREATE or...

Honestly, a single shrink of the database, I wouldn't sweat it too much. It's repeated, even scheduled, shrinks that lead to all sorts of problems. One time, one shrink, no...

Here is the link to the GoFundMe for Robert's family in case you're interested.

No details yet, but word has been spread that Robert Davis has died. I'm so very sorry to be the one to pass this on to you all. However, I...

Assuming you mean remove either unnecessary or unwanted data when you say "purge" (although I'm with everyone else, what do you mean?).

Normally, a properly structured database will foreign...