Viewing 15 posts - 45,301 through 45,315 (of 59,095 total)
Grant Fritchey (2/3/2009)
I read that three times and didn't see the word concatenate until now... [putting on the blind fold, lighting a cigarette] Fire the pork chops when ready...
Heh... nah......
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 7:46 pm
Max (2/3/2009)
I don't know, it's tough to say what with RBAR holding out.
Heh... had to stick with the "No RBAR" theme, somehow and still do the Star Wars thingy... changed...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 7:25 pm
charlesz (2/2/2009)
Our product DB-WAN Accel communicates with SQL Server using TDS...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 6:02 am
steve (2/2/2009)
This 'clever' ranking trick is just the latest incarnation of characteristic functions.
BWAA-HAAA! So what? Heh... Consider this... If the people who wrote T-SQL and other languages got...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 5:54 am
Sanjay (2/2/2009)
Server: Msg 197, Level 15, State 1, Procedure x_TruncateTable, Line 126
EXECUTE cannot be used as a source when inserting into a...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 5:42 am
benlatham (2/3/2009)
Heh... on that note, I'm glad I do all this stuff in T-SQL. 😛
I agree in general that TSQL should be used to do all the work but in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 5:26 am
kevriley (2/3/2009)
Jeff Moden (2/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 5:14 am
ghughes (2/2/2009)
in...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 4:38 am
... and, if your programs are running slowly, the best tip I can give you is to make the paradigm shift from thinking in rows (RBAR) to thinking in set...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 4:33 am
idrees.butt (2/2/2009)
Can you tell some articles that list common mistakes?
http://www.sqlservercentral.com/Forums/Topic627665-338-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 4:15 am
Go for it. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2009 at 4:08 am
Bruce W Cassidy (2/2/2009)
Ooops, really should read all of the replies before posting....
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2009 at 8:26 pm
Max (2/2/2009)
Jeff Moden (2/2/2009)
The chicken was loyal...... the pig was dedicated. 😛
Only problem was that the pig didn't last that long - minor omission though, everyone give Jeff a round...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2009 at 8:24 pm
charlesz (2/2/2009)
Second, NVarchar(MAX) and Varchar(MAX) can only hold up to 65535 bytes ( The number posted by Gail Shaw was wrong).
Any bets on that?
DECLARE @test-2 VARCHAR(MAX),
...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2009 at 8:19 pm
ghughes (2/2/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 2, 2009 at 7:58 pm
Viewing 15 posts - 45,301 through 45,315 (of 59,095 total)