Viewing 15 posts - 50,326 through 50,340 (of 59,099 total)
FROM LD_SDT
LEFT OUTER JOIN WK_SDT_ORGANIZER B ON
...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 5:48 pm
Please check you post... can't see what you posted for the "view".
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 4:43 pm
It's easy... don't try to remove the SA login... just change the password and don't give it out to anyone, ever...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 4:23 pm
Matt Miller (5/23/2008)
The funny clothes I can deal with. The tin foil hat on the other hand...:)
Heh! C'mon... I don't wear the hat in public... and no one...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 4:17 pm
Heh... TODD!!!??? Why are you having me figure it out... run it against the table generator I provided and report your findings! 😀
The answer to your question is...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 4:13 pm
Heh... post the other data from the other table and let's see if we can get it down to a couple of minutes, eh? 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 3:55 pm
CrazyMan,
I have a similar situation at work... Just to be sure... you're talking about 24 tables, correct?
Just to be sure, you ARE using 2005, correct?
How many (order of magnitude) rows...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 9:44 am
Marvin,
I'm a bit confused and I'm obviously missing something.... I looked at the 100 rows of test data you attached... Without me wading through all the code you posted, what...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 9:33 am
Alright, Venki... you've given us just about nothing to go on... no table Create statement, no data, no column names... and your sample query of...
1st query:
select month, count(*) from ...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 24, 2008 at 9:04 am
Sorry about that... BitBucket's method for deleting dupes when an IDENTITY column is present is just as fast as what I posted. Here's his code "Modenized" for the test...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2008 at 7:37 pm
Jeff Moden (5/23/2008)
I'll crank out an example tonight...
Wow! I think I just figured out what to write about in an article!
Terry,
IF there's and IDENTITY column on the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2008 at 7:25 pm
tosscrosby (5/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2008 at 5:36 pm
True enough...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2008 at 5:34 pm
Matt Miller (5/23/2008)
Jeff Moden (5/23/2008)
Heh... just imagine me writing a book... 11 pages every 2 days... it would take an eon for me to write one. I don't know...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2008 at 5:28 pm
Peso (5/23/2008)
Even simpler
ALTER FUNCTION TruncDate
(
@InDate DATETIME
)
RETURNS DATETIME
AS
BEGIN
RETURN DATEDIFF(DAY, '19000101', @InDate)
END
Simple... yes. Clever... very....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2008 at 5:24 pm
Viewing 15 posts - 50,326 through 50,340 (of 59,099 total)