Viewing 15 posts - 57,106 through 57,120 (of 59,101 total)
I don't know what either table has in it nor what either is used for and you left out the SELECT list so it's really hard to tell, but first...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2007 at 12:26 am
Jules,
The real fact of the matter is, both the ISNULL and the OR method really stink up the room in this situation (NULL being treated as "future dated")...
To answer the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2007 at 11:44 pm
Outstanding, Serqiy... at least SOMEBODY tried this and it figures that it would be you
Actually, I whole heartedly agree with you...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2007 at 11:16 pm
"REAL" certainly doesn't work that way on my box...
select convert ( real ,2.5000 )
select convert ( real ,10.0000)
select convert ( real ,20.0000)
select convert ( real ,2.0500 )
select convert (...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2007 at 2:59 pm
Heh... on Brian's note, Steve... I'm thinking "get the glue".
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2007 at 2:19 pm
Mark,
I'm thinking that you did not try the code. Use the table build code to build the table and the related indexes. Then do an execution plan on the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2007 at 11:36 am
Can you "sticky" this to the SQLServerCentral home page (ie. "How to ask a question and what to do with the answer" section) and force newbies to do a read (wishful...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2007 at 9:35 am
Make sure you run the code several times where indicated... you'll both be surprised... and remember the situation may change if a join is involved...
--Drop table MyHead
GO
--===== Create...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2006 at 11:39 pm
Actually, since RedGate just procurred this site, try RedGate SQL Compare ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2006 at 4:22 pm
Yes, it will fail if your server isn't setup to "see" the path. The SQL Server "service" must be started as a power user that can "see" the UNC path...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2006 at 7:33 am
IF you will always have 4 columns, then this will work nicely...
DECLARE @TestText VARCHAR(100)
SET @TestText = 'FIN - TIN - LIN - BIN'
SELECT PARSENAME(REPLACE(@TestText,' -...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2006 at 1:44 pm
You bet, Sol,
Sorry for the apparent rambling
in my last post... was a bit late and I just started typing without much thought to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2006 at 6:43 am
James,
I did a search in BOL 2005 and on google... couldn't find reference to a FIRST or LAST function. Probably my problem since I don't use 2005, yet, but do...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2006 at 9:32 pm
Heh... Good luck, Yves. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
December 25, 2006 at 7:00 pm
Kinda like when your car runs bad but you won't let the mechanic pop the hood, isn't it Sol? Heck, I don't even know what your "car" looks like... --Jeff Moden Change is inevitable... Change for the better is not.
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
December 25, 2006 at 12:55 pm
Viewing 15 posts - 57,106 through 57,120 (of 59,101 total)