Jeff Moden (11/14/2012)
Want a cool sig (11/13/2012)
Wow Jeff that is wicked fast... thanks a lot... the time for returning 2600 rows really shows how much faster your method is...Jeff's wicked fast script
SQL Server Execution Times:
CPU time = 563 ms, elapsed time = 682 ms.
My wicked slow script
SQL Server Execution Times:
CPU time = 25500 ms, elapsed time = 25696 ms.
Ugh! I appreciate the compliment but more than 1/2 a second to process just 2600 rows is pretty bad for me. The right kind of index might help it, though.
I say it's slow because a "Quirky Update" would do such a thing to a million rows in about 2 or 3 seconds. If you have a large nnumber of rows, let me know and we'll see what we can put together for you.
it's part of a larger query that hits a table with 530k records and joins 5 other tables... the 2600 records is the largest recordset that I can find in the table... and unfortunately the columns I'm using isn't indexed... I'm happy with 1/2 a second... 🙂 Thanks
---------------------------------------------------------------
Mike Hahn - MCSomething someday:-)
Right way to ask for help!!
http://www.sqlservercentral.com/articles/Best+Practices/61537/
I post so I can see my avatar :hehe:
I want a personal webpage 😎
I want to win the lotto 😀
I want a gf like Tiffa :w00t: Oh wait I'm married!:-D