Interesting stuff. The bad plan, on the higher memory machine is using less memory than the good plan on the more memory machine. I'm thinking though that the statistics on...

You can try using query hints, but the fundamental problem is the approach you're taking with the query. Ad hoc or dynamic SQL like this will create a different execution...

castillo.sergio (12/17/2009)

---

Hi. Thank you very much for your responses.

After a lot of tests in production and test environments, the result is that when we change the amount of RAM memory...

And... Same number of processors, same cost threshold for parallelism, same ANSI settings on the connections...

Just a few more things that can result in execution plans changing.

You'll also need VIEW DATABASE STATE for some of the DMV's.

GilaMonster (12/16/2009)

---

As far as I'm aware, what's in the log is the uid, the database user id. If the person who deleted the data was a sysadmin, that'll be dbo...

The Dixie Flatline (12/16/2009)

---

Grant... I saw Kentucky Fried Movie wayyyy back when .... and your comment just gave me a sudden vision of a clown with a whip... an image...

This is more or less a paging problem. There are a number of possible solutions:

http://www.sqlservercentral.com/articles/66030/%5B/url%5D

http://www.sqlservercentral.com/scripts/31280/%5B/url%5D

These are just the first couple that I came across after searching on the site. There...

Everything else is absolutely equal, identical databases, identical indexes on the databases, identical statistics on the indexes, identical queries, identical parameters... I've moved databases between servers before without the execution...

The only way you can do this is if you've set up some auditing method prior to the deletes occurring or if you've got a trace running that captured the...

I'm sorry, I'm not there, so I can only answer based on the information you've provided.

From what you've said, a long running process was reading some large piece of data....

You're asking the...

It really depends on what you're doing with SQL Server. Let's say you implement the hierarchy data type. VS 2005 won't be able to consume it. But if you keep...

Then use a derived table and join against it. That would, more or less, be the equivalent of maintaining one WHERE clause and then using it for sub-selects.

Compression is only available for Enterprise.

Cool stuff though.