Viewing 15 posts - 58,381 through 58,395 (of 59,053 total)
Serqiy,
The only problem I see is that there are folks that are over 99 years... just change the VARCHAR(2) to VARCHAR(3) and you're golden because you accounted for everything else...
February 20, 2006 at 7:43 pm
Jennifer,
I agree with Serqiy...
SELECT STR(yourcolumn,10,4)
FROM yourtable...
February 20, 2006 at 6:59 pm
Not quite true... table variables are also connection sensitive...
February 16, 2006 at 10:07 pm
Jesper... I don't believe your formula works correctly...
February 16, 2006 at 10:03 pm
Ya just gotta love what Microsoft did with their execution plans
... I absolutely agree that both execution plans came out the same for...
February 16, 2006 at 6:30 pm
Funny, I just posted a similar solution to remove everything except 0-9...
If you don't already have a "Tally" table, now's the time to make one... here's the code to make...
February 16, 2006 at 12:43 am
Govinn,
If you don't already have a "Tally" table, now's the time to make one... here's the code to make a Tally table...
--===== Create and populate a Tally table...
February 16, 2006 at 12:04 am
Steve,
What is the datatype of the column you are storing this data in?
February 13, 2006 at 6:07 pm
Just a couple of things...
If the Inserts will, more or less, be in order by [Date], then having a Clustered Index on date will be OK, otherwise, the Inserts will...
February 13, 2006 at 4:26 am
Yeah, but, good Lord... don't use a cursor to find and delete dupes (or for anything else for that matter)... here's a fully commented template for deleting dupes... you could...
February 12, 2006 at 8:59 pm
Ron,
This is what I posted on the "other" forum you posted the same question on...
> First, I have to do due diligence... what you're suggesting is, for so many reasons,...
February 11, 2006 at 7:00 pm
Bullfrog,
I'm thinking that your times are a bit screwed up in your example data... they're all 8:23:00. But, I'm thinking we get the idea...
The hard part is, I can figure...
February 11, 2006 at 6:58 pm
If you just want duration and not actual CPU seconds used, then something like this works...
--===== Declare a couple of variables to measure duration
DECLARE @StartTime DATETIME
DECLARE @EndTime DATETIME
February 10, 2006 at 11:48 pm
Hi Tushar,
Look up "cross-tab reports" in Books Online... it has a great example of how to do a "Cross Tab" which some call a "Pivot". If you want true pivots,...
February 10, 2006 at 11:39 pm
Viewing 15 posts - 58,381 through 58,395 (of 59,053 total)