Viewing 15 posts - 58,081 through 58,095 (of 59,067 total)
Thought I'd take a bit more time to show what you can do with a template (this also correct's a minor logic error in the WHERE clause of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2006 at 1:34 pm
You bet, Ed. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 25, 2006 at 12:18 pm
Aye. Thank you for the tips... there have been several discussions over temp tables and table variables and most have involved some form of blood-letting ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2006 at 6:37 pm
Thanks Brian... looking forward to it. Enjoying my weekend, too! Slept the whole day! First time in more than a year! ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
June 24, 2006 at 4:11 pm
Shoot... here we go... this is a perfect example of what I've spoken of in the past...
You had to write a little VB...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 23, 2006 at 10:16 pm
Using ISNUMERIC to determine if something is all numeric digits is a form of "Death by SQL"...
IF IsNumeric(RIGHT(RTRIM('ABCDEF$-1,'), 4)) = 1
print 'yay'
else
print 'boo'
IF IsNumeric(RIGHT(RTRIM('ABCDEF0D01'), 4)) = 1
print 'yay'
else
print 'boo'
IF IsNumeric(RIGHT(RTRIM('ABCDEF23E2'),...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 23, 2006 at 8:19 pm
Although I agree that doing an ORDER BY in a view is a bit crazy, I'd have to disagree with the author of the blog because I tried the methods...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 23, 2006 at 7:09 am
Sorry for my obvious post, Jason... I pulled to reply to Mick's post and got distracted... in that time, you answered and I didn't see it.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 23, 2006 at 7:02 am
True but you have to be careful not to allow things so large that you have the potential for trying to store more than 8060 bytes (or less) in a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2006 at 9:05 pm
Which one worked? The merge or the reregister?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2006 at 8:46 pm
You cannot say SELECT @somevariable = * and get away with it...
While OPENROWSET is fine, it exposes passwords and logins... it would be far better to create a Linked Server.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2006 at 8:41 pm
I don't know if DTS has a way to modify that output but, if it can, replace the 1234567 in the following code with whatever DTS uses...
SELECT CONVERT(CHAR(8),DATEADD(ms,1234567,0),108)
Converts 1234567 milliseconds...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2006 at 8:36 pm
>>[Subquery returned more than 1 value] error
That usually has more to do with what you're doing in the code... you should post it so we can take a look for...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2006 at 8:28 pm
Peter used two "AND"s just due to a cut'n'paste error... remove one of the "AND"s and it'll probably work just fine.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2006 at 8:25 pm
Yes,
It "pukes" because you first compare a variable to null so it must first try to compare every record to a condition that does not exist.
Use the first form...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 22, 2006 at 7:41 pm
Viewing 15 posts - 58,081 through 58,095 (of 59,067 total)