Viewing 15 posts - 56,956 through 56,970 (of 59,067 total)
Same as above but single column output...
DECLARE @StartDate DATETIME
DECLARE @EndDate DATETIME
SET @StartDate = '01/01/2006'
SET @EndDate = '10/02/2007'
PRINT DATEDIFF(dd,@StartDate,@EndDate)+1
SELECT STR(Number*90+1,4)
+ ' -'
+ STR(CASE
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2007 at 7:13 am
Set based solution... substitute a tally table for spt_Values if you have one...
DECLARE @StartDate DATETIME
DECLARE @EndDate DATETIME
SET @StartDate = '01/01/2006'
SET @EndDate = '10/02/2007'
PRINT DATEDIFF(dd,@StartDate,@EndDate)+1 --Just...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2007 at 7:10 am
Nope... not the NULL thing. My explanation is probably going to sound a little "dated" because I gave up the "GUI world" about 5 years ago when my boss (actually,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 10:18 pm
John,
What is the data type of the column you are calling "TimeStamp"?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 6:24 pm
Where is the "E" drive... on the server or on your local drive? If it's not on the server, you must use the UNC name back to the path where...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 6:18 pm
Post your cursor and let's see if we can help you get rid of it because it has the biggest and worst impact both on performance and resources.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 6:08 pm
I might MOVE the file to an "archive" directory, but I wouldn't delete it until I was sure the server had gone through a backup cycle.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 6:03 pm
Heh... well done... I'm thinking that if SP4 is so tough on cursors, then I like it a lot ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 5:19 pm
FYI... the WHERE 1=1 thing is what a lot of GUI programmers do when writing embedded SQL with dynamic WHERE clauses... they will always have a valid WHERE clause and they...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 5:15 pm
Another couple o' things to check...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 5:09 pm
I agree with that! The looping has got to interfere with the overall performance.
Anyway, Michael... I have a question about your wonderful F_TABLE_NUMBER_RANGE function... Since it's very fast (Surprisingly so! ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2007 at 4:42 pm
I'm not a .Net guy either... that's why I just right click on a proc in QA and select [OPEN]. A windows opens with all the parameters available which can...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2007 at 11:58 am
Obviously... ![]()
Like you said at the end of your last post, I'm still trying to get Lindsay to correctly identify the problem 
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2007 at 11:32 pm
Yep... that's what I was talking about... but that's week 14? Maybe I missed it somewhere but you still haven't given us all the info we need... like when the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2007 at 5:02 pm
But it won't always unless you have something that identifies the order of the task descriptions....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2007 at 10:46 am
Viewing 15 posts - 56,956 through 56,970 (of 59,067 total)