Viewing 15 posts - 43,201 through 43,215 (of 59,102 total)
Lynn Pettis (6/29/2009)
And that will work until the SQL Server 2000 system table "views", like sys.syscolumns, go away in a future version od SQL Server. They have been depreciated.
I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 8:41 am
Peso (6/29/2009)
Or use COLLATIONCONSTRAINT ss CHECK (adp IN ('T', 'F') COLLATE SQL_Latin1_General_Cp437_BIN)
That's a good check but I'd have to introduce someone to a serious volley of high speed pork chops...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:41 am
As a side bar, I'm still waiting for the OP to post code where the things he wants to use aren't actually commented out so I can be sure of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:37 am
Scott Coleman (6/29/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:33 am
Paul White (6/29/2009)
Peso (6/29/2009)
This is because I have an edited very slim version of MASTER database.
This is not something common, but you should...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 6:14 am
In order to do the concatenation to create the CSV list, some form of sub-query either in the form of an actual sub-query or in the form of a UDF...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 5:58 am
Sinshith S Anand (6/28/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 5:53 am
Chandra Sekhar Manchukonda (6/29/2009)
We can use replace function for handling them.
DECLARE @test-2...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 5:42 am
sam.walker (6/29/2009)
I've just simply compared on my server.
Rows 4096 based on huge repitition of AAAA,BB,CCCCCCCCC,D
Inline function
126 ms
123 ms
130 ms
Partial CLR plus tally table
3 ms
3 ms
3 ms
I used...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 5:39 am
You're welcome. Thanks for the response.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 29, 2009 at 5:20 am
The article is well written and my hat is off to the author for that. I have to agree with the others, though... using XML to split delimited data...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2009 at 7:47 pm
lmu92 (6/28/2009)
Paul White (6/28/2009)
lmu92 (6/28/2009)
Paul White (6/27/2009)
Clearly, in this case, and with this data distribution, there is nothing to choose between the three methods. ...Paul
But how about the method I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2009 at 8:40 am
Paul White (6/28/2009)
Jeff, could you let me have the number of your handrail-installation team please? 😀
PIVOT can be used with dynamic SQL, just the same as the CASE...SUM idea.
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2009 at 8:31 am
Paul White (6/28/2009)
Guys,Does it really matter that much what was meant by the word 'correct'?
Taking the poor guy to task over semantics seems unfair.
Paul
Nah... not the word "correct"... I want...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 28, 2009 at 8:18 am
At least the correct answer wasn't "close" to all the other answers because none of the answers are correct in 2k.
1.2345679E+9
Before you start beating the "latest version" drum on that......
--Jeff Moden
Change is inevitable... Change for the better is not.
June 27, 2009 at 9:47 pm
Viewing 15 posts - 43,201 through 43,215 (of 59,102 total)