Viewing 15 posts - 53,761 through 53,775 (of 59,089 total)
Cast to INT will get rid of leading zeros.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 5:49 pm
Heh...
Step 1... search SysComments for the word "Cursor".
Step 2... search SysComments for the word WHILE
Step 3... search SysComments for the occurance of any view.
Step 4... review all User Defined...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 5:44 pm
Interesting site with more than what I ever wanted to know... 😀
I did find some files to "play" with...
http://www.census.gov/genealogy/names/names_files.html
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 5:36 pm
I'll ger it a try... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 5:26 pm
Gosh... what's wrong with just...
EXEC master.dbo.xp_fixeddrives
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 5:14 pm
Heh... thanks for the feedback, Mark... and no problem...
Say, do you have the URL for that census data? Might be fun to play with... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 5:09 pm
Steve,
Heh... this is one of the things on my upcoming wish list... it would be great to be able to control a lookup for posts that have <= X replies...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 7:24 am
The content is more important than the grammar.
True... but I'd still try. And, it's not just grammer... using the correct words can mean the difference between someone thinking that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 7:19 am
Heh... stop watch or ...
DECLARE @StartTime DATETIME
SET @StartTime = GETDATE()
--...code to measure duration of goes here...
PRINT CONVERT(CHAR(12),GETDATE()-@StartTime,114) + ' Duration (hh:mi:ss:mmm)'
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 7:06 am
GilaMonster (12/3/2007)
Jeff Moden (12/2/2007)
A
Why would you say that?
I'd say B. Dates should be stored in datetime columns, not seperated out. There are a couple of good reasons
There are some quite...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 6:37 am
Sergiy (12/1/2007)
Jeff Moden (12/1/2007)
Hmmm... and what do you do for sprocs that are used by multiple applications?
Well, procedure is doing the same thing to the same object (or, better, "object").
If...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 6:33 am
I still want to know why it's necessary to return a 42 million row result set... THAT's the performance problem... especially if ANY of the "dim" tables are actually, ugh,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 6:25 am
You can gain some very fine control over the "order" of what get's done by triggers... put all the code in the correct order in one trigger.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 6:20 am
you can run the solution against it and see th results
Heh... no... I can't... don't have 2k5...
From what I understand, Cross Apply has some performance limitations... I was looking...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 6:17 am
And Vivian's good script lists the FreeSpace in Mega Bytes.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2007 at 6:08 am
Viewing 15 posts - 53,761 through 53,775 (of 59,089 total)