Viewing 15 posts - 30,451 through 30,465 (of 59,101 total)
GilaMonster (4/5/2012)
george sibbald (4/5/2012)
where I have added a clustered index to a heap I have achieved a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 6:16 pm
Considering that you input data is only a half of what your output data is, your going to have to describe how the data describes "in" and "out" times. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 6:10 pm
Jeff Moden (4/5/2012)
sharky (4/5/2012)
SQL Server parse and compile time:CPU time = 0 ms, elapsed time = 130 ms.
========== Craig's Method ======================================================
SQL Server Execution Times:
...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 5:59 pm
SQLKnowItAll (4/5/2012)
Jeff Moden (4/5/2012)
SQLKnowItAll (4/5/2012)
GilaMonster (4/5/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 5:38 pm
sharky (4/5/2012)
SQL Server parse and compile time:CPU time = 0 ms, elapsed time = 130 ms.
========== Craig's Method ======================================================
SQL Server Execution Times:
CPU...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 5:11 pm
Here's my whole test harness including the UPPER modification to make Stan's fine idea work correctly.
CREATE TABLE yourTable (name VARCHAR(50))
INSERT INTO yourTable
SELECT name
FROM (
SELECT 'Good' UNION ALL --Keep
SELECT 'Goabc'...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 5:08 pm
capn.hector (4/5/2012)
would you be able to slap an UPPER() or LOWER() around yt.Name in ASCII(SUBSTRING(yt.Name,t.N,1)) turning it into ASCII(SUBSTRING(UPPER(yt.Name),t.N,1)) to get around the Stu problem in stan's code?
Yes but you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 4:48 pm
SQLKnowItAll (4/5/2012)
GilaMonster (4/5/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 4:44 pm
sharky (4/5/2012)
I am not a huge fan of a Tally table as the code can break when you port it,
So can any other code that you try to port. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 4:39 pm
sharky (4/4/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 4:25 pm
binak_86 (4/5/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 3:15 pm
Steve Jones - SSC Editor (4/5/2012)
Lynn Pettis (4/5/2012)
I'm sorry, but I started laughing to myself when I read this one.As Jeff would say, bwahahaha
Whup? BWAAA_HAAAA!!! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 12:48 pm
I had a bug in the "usage" comments in the code I previously posted. I also took the time to add a usage comment very specific to this thread.
schillingt...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 5, 2012 at 6:34 am
{edit} Had a bug in the comments (believe it or not) I posted. I'll be back.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2012 at 10:44 pm
ColdCoffee (4/4/2012)
Jeff Moden (4/4/2012)
ColdCoffee (4/4/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 4, 2012 at 10:24 pm
Viewing 15 posts - 30,451 through 30,465 (of 59,101 total)