That's pretty much what you'd need to do. If you need to sum colors and then pick the max quantity, this works well.

jchapman (5/22/2014)

---

I've been experimenting... riddle me this...

My misbehaving share table is partitioned (with LightSpeed, this is 2005 environment) into 183ish partitions.

Here is what I did I just copied my 92...

Luis Cazares (5/22/2014)

---

The problem is that OBJECT_NAME expects an int value and l.resource_associated_entity_id is a bigint.

Maybe changing the last condition would solve the proble, but I'm not sure if it...

So looking at the queries, it really is nothing more than the lack of a covering index. This is normal behavior. The query is returning enough results that...

jchapman (5/22/2014)

---

Does it make sense to you though, that the query plan would change to a table scan just because one of the 4 columns in the select is not...

Looks to me like the issue is with the Kill statement

EXECUTE ('KILL ' + @spid)

you need to cast the spid to varchar because 'Kill ' cannot be converted to INT.

Then you will need to utilize a bunch of unions to get all of the database information.

An alternative is you could prepopulate a table with all of the data for...

erm - you can't...

The only possible conceivable advantage is in the case where you are unable to get more disk space so the only option is to shrink a database to try and...

I'm with Lowell. This looks to me like somebody did a reseed on backupset.

Out of curiosity, what is generating the query?

You'll also notice that the Recipe table has been removed from the execution plan. It looks like you probably have a trusted constraint between Recipe and RecipeMap. Based...

The query is a relatively low cost but is going parallel.

It looks like you might have set maxdop to 2 but left the cost threshold at 5.

You might want to...

Some of the report data will be cached locally on the report server. Large reports may error out due to memory issues. Depending on the number and size...

In this case you are going to a query that doesn't have a covering index. It also appears you do not have a clustered index because you are reverting...