Viewing 15 posts - 53,776 through 53,790 (of 59,098 total)
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
Heh... You weren't supposed to remove the TOP... thought you only wanted ten random names at a time... and I sure didn't know you had a list of over 20,000...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2007 at 5:20 pm
Can you post what some of the output looked like? Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2007 at 3:53 pm
Ummm... maybe you can do it using OPENDATASOURCE or OPENROWSET...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2007 at 3:49 pm
Can't be done using EXEC... temp table must already exist.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2007 at 3:48 pm
So really it would depend on how many rows are returned?
Why do it two different ways?... and have one crawl if the scalability increases?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2007 at 3:44 pm
Dunno about others... but I've not needed anything but T-SQL with occasional trips through xp_CmdShell to use some "DOS" functionality.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2007 at 3:37 pm
Viewing 15 posts - 53,776 through 53,790 (of 59,098 total)