Viewing 15 posts - 56,986 through 57,000 (of 59,101 total)
Thanks Farrell,
That's a high compliment coming from folks like yourself.
Vamsi,
On my way to work so can't answer in detail just now but, I need to know, what are the boundaries...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2007 at 6:25 am
Nicely done, Robert.
I'm still waiting for the original poster to definitely describe the datatype of the column he named "TimeStamp" (instead of guessing
).
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2007 at 7:15 pm
Ok, here's some sample code using Michael's function that I renamed as "fnTally" and changed the "Numbers" column to just an "N" to match what I also have in my...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2007 at 7:09 pm
1) WHERE Name IS NULL - is that specific to your Master.dbo.spt_Values table?
It is specific to the Master.dbo.spt_Values table... however, the table isn't "my" table, it's part of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2007 at 5:22 pm
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
Viewing 15 posts - 56,986 through 57,000 (of 59,101 total)