I tried the same query on a testing machine, it was the only query reported by sp_whoisactive, with the same 'runnable' status, but there was nothing else 'running'.

I always...

It seems I found a solution but it is really weird....

I assumed that if I have Windows 2008 on 64bits and SQL Server 2008 on 64bit then I should use...

Nobody has any idea about this? How is it possible to debug this issue? I suppose I should check if some DLL's are registered or not, or maybe something else?

I have to prevent escalating because this causes deadlocks in queries like :

INSERT INTO table_name ...blablabla... and this is not acceptable 🙁

I agree it is probably the most weird request ever, it is a request from a client ...

They need one Excel column for each row in the dataset, and at...

I didn't post a specific DDL because I was trying to find out if there is a general solution better than just writing a cursor-based SP of my own...

The schema...

You would loose your money Sir, because I moved very carefully all the jobs before the full backup.

And besides this, I inspected the "job history" with the log viewer...

This is definitely a very good solution, THANK YOU!

I was looking for a hint to force the execution of subquery first, but I suppose there isn't one, so your solution...

I have to answer it - just a RAISERROR with a lower severity ....

:w00t: :w00t:

ORDER BY

CASE

WHEN SUBSTRING(Field,2,1)='D' THEN 'A' + SUBSTRING(Field,1,1)

WHEN SUBSTRING(Field,2,1)='W' THEN 'B' + SUBSTRING(Field,1,1)

...

SELECT ... ORDER BY REVERSE(field) should do the job if I got this right.

After all, even if the field is a combination of int+char, the result is a char..

Which is...

Thank you, tt works just perfect!

Excuse my ignorance, but what's a "Quirky Update" ?

Performance is not an issue in this case, I am just curious if just a set based solution is possible for this

I just have to partition (not group) the orders in partitions that have the total amount of a partition of maximum $3,000.

I found the answer - it is pretty simple - just restarting the sql service fixed the problem...