That is strange behavior. I've never seen anything like it. If you can, post the code. If it's huge, post it as an attachment.

Do you have lots of PRINT statements...

Perry Whittle (4/2/2009)

---

once you start the restore process if you then kill it you have to wait for it to roll back, this could take some time, hence why it...

I'm not sure, I haven't used this myself, and I don't see anything in the documentation. One point, Books Online suggests using the dynamic management function sys.dm_io_virtual_file_stats instead of...

Yeah, I've read those. I was never completely dependent on IO, but it sure made me second guess even how much I used it.

But Gail was write to call me...

I've never tried achieving that kind of measure before. But, I will say that you shouldn't be surprised if there are lots of reads even on a system that you...

I think he's referring to the statistics being out of date or insufficiently sampled. Just because you have auto-stats turned on doesn't mean that all the statistics are getting updated...

GilaMonster (4/2/2009)

---

Grant Fritchey (3/27/2009)

---

1. The first query, by a long shot. Although it has a higher number of physical reads. But if both these queries are accessing the same data...

Yeah, Barry's right, table variables aren't logged, but what is it that you're doing that's causing so much logging?

I think Gail has it right. They "fixed" the incorrect behavior from 2000. That leads to problems like what you encountered.

I don't see it on her blog[/url]. It was in a presentation she gave at the PASS Summit last November.

Nice to...

Maybe I'm wrong. Wouldn't be the first time (today). Hang on, testing... might be a while.

Regardless of default schema, if you don't reference the schema in the query, SQL Server will try to find the query in dbo. I don't think it's a bug. It's...

It doesn't look like it from the code you showed, but are you using qualified names in the queries?

SELECT *

FROM schema.table

--not

SELECT *

FROM table

That would absolutely explain the problem.

According to the Upgrade Advisor column aliases in the ORDER BY clause cannot be prefixed by the table alias.

Why not try dropping the alias and then using the column name...