Heh... it's not the undocumented features we should...

CrazyMan (8/4/2008)

---

Thanks Jeff

Its supposed to take only a few seconds, since the table is continusly accessed by applicaitons, this is taking me 3 minutes to delete on a Quite time,...

Most people think that FLOAT makes rounding issues... lemme as this... if you divide 1 by three and then multiply the answer times 3, what is the answer supposed to...

Heh... Ya Think? What do you want to do with it? 😉

Have you tried the clustered index solution I gave you yet? :blink:

CrazyMan (8/4/2008)

---

Hi Jeff

This is a nice way, but i cant block the table for this time, since the table is accessed by application...

Now we're talking... great post.

Thanks, Chris... :blush: (Didn't expect that)

What about the out of place 41?

I wonder how they do running totals in data warehouses in SQL Server?

Heh... during my most recent interview, I was informed that I had been "Googled".

Unfortunately, it's human nature to believe just about anything that appears on the web whether it's good...

I agree with Barry... if you are using CHAR instead of VARCHAR, then things don't appear quite the same way. Also, there's a lot of characters that look like...

I think the correlation between lazy and incompetent is almost 100% 😉

Heh... thanks for the feedback... I've done the same thing, many times. Didn't know for sure if you were on to something that I wasn't aware of or not...

He already did... 😉

SELECT *

FROM #NewTempTable

ORDER BY ID

...and, with NO indexes whatsoever on the table, it only took 289 milli-seconds...

Are you sure that the "table" you're looking at isn't a view? And, again, how many rows...