Viewing 15 posts - 52,306 through 52,320 (of 59,091 total)
Heh... nah... it's only 0.229 M rows... same as the other two tests...
I did mislabel it though... probably due to low Caffeine with a Niquil kicker, as well... the last...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 5:40 pm
Okidoki... first things first... If you don't already have a Tally table, now is the time to add one to your arsenal of SQL prestidigitation... a Tally table (also known...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 5:26 pm
Perfect... I'll be back soon...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 3:34 pm
Sorry... just as a courtesy, I should post the code for making a Tally table, huh?
--===== Create and populate the Tally table on the fly
SELECT TOP 19000 --equates to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 3:31 pm
Yep... I'm aware of that, but thanks for making sure, Ian.
So far as using spt_Values as a source of numbers in production, I NEVER do it... I always use a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 3:27 pm
Ok... is there anything like a CustID or EmployeeNum or some column that I can relate back to that uniquely identifies a given row? Not quite the same as...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 3:04 pm
MH... seriously... just tell me what the PK of the table is...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 2:08 pm
Also, still need to know the PK of the table for the highspeed Tally table solution...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 1:37 pm
Mh (2/27/2008)
1. lastname, firstname MI
2. Lastname, Firstname, MI
There are some data issues, just for now let's consider the above...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 1:36 pm
Heh... it's real tough when the OP doesn't have a clue what they want... here's what he posted just before his edit for names...
NYSTROM, GRAHAM, A
CLOSSON, SEAN T
MOORE, AMANDA
In any...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 1:35 pm
Have you tried anything on your own??? Have you looked into CHARINDEX or PATINDEX?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 1:22 pm
Ummm... the example I posted is pretty clear... I'm thinking that you should be able to cut and paste a couple of table and column names on your own...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 1:05 pm
Sure... create a file called "CR.txt" and store a single blank line in it. Almost any editor including NotePad can do this just by opening a new file, pressing...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 11:32 am
Ummm... neither is Model...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 10:57 am
kurraraghu (2/27/2008)
set @dt = '1900-01-1 00:00:00.000'
select cast(@dt as float)
----------------------
0.105555555555556
(1 row(s) affected)
here how is the time calculate is it seconds of the day or milliseconds smthng like...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 27, 2008 at 10:29 am
Viewing 15 posts - 52,306 through 52,320 (of 59,091 total)