Viewing 15 posts - 58,651 through 58,665 (of 59,053 total)
I think what you are looking for is SELECT/INTO... it faster than any other method especially if you turn SELECT INTO/BULK COPY on...
It creates the table on the fly fut...
September 3, 2005 at 4:00 pm
Try this, instead...
SELECT "This is a test"
September 3, 2005 at 3:46 pm
HRen,
You could certainly change the meat of this to a user defined function to, as they say, enforce an enterprise wide standard or if the output is required for something...
September 3, 2005 at 9:23 am
Serqiy,
That might work fine on small tables but I stopped the run after 37 minutes just trying to return the first page on my large table... here's the code...
SELECT...
August 30, 2005 at 5:32 pm
Adam, I think part of the problem is, the formula doesn't work as everyone expects
because DATEDIFF only looks at boundaries crossed of the date part...
August 30, 2005 at 7:21 am
As someone else suggested, why make the AGE persist? I'm thinking it would be much easier to add a calculated column to the table so that you don't have to...
August 29, 2005 at 7:26 pm
Well, I retuested with the correction Giovanni noticed (see last posting) and was a bit surprised... the change did nothing to the low end (1st page still returns in 13 milliseconds)...
August 29, 2005 at 5:20 pm
Giovanni... thanks for the questions.
The * selection in the top select of "d" was a nasty oversite
... it was a leftover from testing...
August 29, 2005 at 5:06 pm
Subhash,
I'm sorry I left out the the "--" on the comment
. It sure did make a mess of things. You all set now?
August 29, 2005 at 6:39 am
... or try Books OnLine which comes with SQL Server.
August 27, 2005 at 10:47 pm
That would do it, but be careful... setting the transaction isolation level in procs may sometimes cause a conflict for lock type. You could use the WITH (NOLOCK) hint after the...
August 27, 2005 at 10:45 pm
Just so you know, you can use VARCHAR(8000) for this... won't help with things over 8000 characters like Peter's suggestion but you don't have to limit yourself to 4000 characters...
August 27, 2005 at 10:23 pm
Better late than never, I guess...
DECLARE @Year CHAR(4)
DECLARE @NextYear CHAR(4)
DECLARE @ISOWeek VARCHAR(2)
SET @Year = '2001'
SET @ISOWeek = '53'
SET @NextYear = @Year+1
SELECT
CASE
WHEN...
August 27, 2005 at 12:21 pm
Oh CRUD! No, you don't even want to think of building a sequence table for this... here's why...
You said that the 3rd party stuff
August 27, 2005 at 11:21 am
Viewing 15 posts - 58,651 through 58,665 (of 59,053 total)