Viewing 15 posts - 54,391 through 54,405 (of 59,098 total)
Not sure I'd waste my time benchmarking for that...
Why not just Google a bunch of articles about SQL Server Maintenance... lot's of them say "why"...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2007 at 5:27 pm
It doesn't... from the way you were talking, I thought you were using a "blank formatted" spreadsheet file as a template that you copied for new files.
What are you currently...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2007 at 5:22 pm
Nice 2k5 solution... but I'm pretty sure that it won't work in 2k... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2007 at 5:15 pm
What in format 1 identifies which column something should go into in format 2? Also, please describe the column names in format 1... I don't think they start off...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2007 at 4:56 pm
SET ROWCOUNT can sometimes be a lot slower than TOP... if it turns out to be too slow, you could always use dynamic SQL (observing, of course, all the warnings...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2007 at 4:52 pm
Change the spreadsheet template to have a "freeze panes" in the correct spot.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 1, 2007 at 8:19 am
VBS MsgBox from Cmd prompt...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2007 at 8:46 pm
Close! Not seeing StockCode 12 anywhere in the result, though...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2007 at 1:47 am
Parts or people, it's still a hierarchy... take a look at "Expanding Hierarchies" in Books Online... they've got a decent example. There's a couple of other ways to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2007 at 5:48 pm
The only way to guarantee the same time would be to store it in a variable and then do the SELECT using the variable instead of GETDATE().
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2007 at 9:18 pm
Yeh... 2nd mistake today... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2007 at 9:12 pm
OH! How embarassing... I thought you were talking about "LDF's"... sorry...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2007 at 5:39 pm
Kenneth Wilhelmsson (10/29/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2007 at 5:35 pm
BaldNomad (10/29/2007)
you're validating data that's already been validated? why?
According to the OP, the data is in a file... much like storing dates as datetimes, I always valid even supposedly...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2007 at 5:32 pm
mrpolecat (10/29/2007)
Jeff--It throws errors
Server: Msg 156, Level 15, State 1, Line 27
Incorrect syntax near the keyword 'ASC'.
Server: Msg 208, Level 16, State 1, Line 12
Invalid object name '#yourtable'.
It's gotta be...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2007 at 5:29 pm
Viewing 15 posts - 54,391 through 54,405 (of 59,098 total)