Viewing 15 posts - 54,211 through 54,225 (of 59,072 total)
John Mitchell (11/5/2007)
MarkMy suggestion would be not to bother with an extra column, but instead to store that single extra value in a variable.
John
That would be my suggestion, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 7:47 am
There's a thousand different reasons for things like this...
Do the tables have the same number of rows?
Do the tables have the same indexes?
Are the indexes up to date?
Are the statistics...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 7:44 am
Both...
The DBA's need to verify that the SQL Server instance is logged in either as a Super User that can see everything or must be logged in as a user...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 7:38 am
Vincent Chute (11/9/2007)
I learnt != in maths so seeing <> has always been a wtf moment for me.
Just different notation dialects.
"!" being a shorthand for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 7:12 am
Shaun McGuile (11/9/2007)
!= is th inequality in C# get used to it as CLR programming takes off!:hehe:
Heh... good point. But have had this argument with many other folks... there's...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 7:00 am
Although the "OR" in your example allows each value to be matched and displayed, it does not form a Cartesian product...
DECLARE @TableA TABLE (SNo CHAR(1),ENo INT)
INSERT INTO @TableA (SNo,ENo)
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 6:56 am
Sure... how many rows in the temp table?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 12:18 am
I don't know for sure... but I think it's highly unlikely that MySQL will have the same nameing structure convention... never mind a user called "dbo".
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2007 at 12:12 am
SO... what does all of that mean? Did you use Ramesh's solution or not? If not, would you post your solution, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 10:51 pm
Perfect, John...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 10:40 pm
You give up too soon 😉
[font="Courier New"]DECLARE @CrLf char(2)
SET @CrLf = Char(13) + Char(10)
SELECT COALESCE(NULLIF(Add1,' ') + @CrLf, '') + COALESCE(NULLIF(Add2,' ') + @CrLf, '') + COALESCE(NULLIF(Add3,' ') + @CrLf,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 10:37 pm
Jason Selburg (11/8/2007)
Thanks Jeff! I've never worked with Oracle so that info was very informative ... :hehe:
You bet, Jason... thanks for the feedback...
ps. I hate Oracle 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 10:33 pm
Heh... thanks for the feedback... I actually wrote a cursor once or twice... it was to show how slow they were... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 10:30 pm
Greg,
I'm working on a couple of work arounds and a full "wish list" to Tony... I'll get back on these formatting issues... just not right now...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 10:23 pm
edit math error...
Ummm... what's that mean? :blink:
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 10:18 pm
Viewing 15 posts - 54,211 through 54,225 (of 59,072 total)