Viewing 15 posts - 41,626 through 41,640 (of 59,102 total)
It's easier than that. To reject things that are either blank or null in VARCHAR columns, you simply need to check for anything greater than a blank...
WHERE somecolumn >...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 3:59 pm
Any kind of job is scarce right now. If you log onto "Michigan Works" and take a look, there are more than 1.2 million resumes available for a bit...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 3:50 pm
dzirkelb (10/7/2009)
8.0
12
1SQLCHAR0255"\t"1Allied ""
2 SQLCHAR 0 255 "\t"...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 3:44 pm
Roy Ernest (10/7/2009)
The recoil usually is pretty strong and your 12 yr old can handle that. And still hit a clay pigeon.
10 year old, 12 guage gun.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 3:36 pm
Andy DBA (10/7/2009)
SuperDBA-207096 (10/7/2009)
You might want to mention in the:
"Excluding the Intersection of the Sets" section this is similar to
select... where not in (select... from table2) but it performs...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 3:08 pm
Chris Howarth-536003 (10/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 3:05 pm
Heh... of course, I will admit that, no matter which method someone uses to identify the column/table relationships, just about anything would be better than a format like the following...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 2:21 pm
Wow. "Brilliant" is an understatement.
Try the following...
Select "Field[1]" from
... then find the Developer, the Manager, and the DBA that allowed the brackets and see if they like porkchops... at...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 2:13 pm
Lynn Pettis (10/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 1:49 pm
wagner crivelini (10/7/2009)
I understand your point.
But it came out so naturally to me writing statements with aliases that it never crossed my mind to say they are optional.
But I...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 1:41 pm
davidpenton (10/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 1:34 pm
David Walker-278941 (10/7/2009)
ryan.mcatee (10/7/2009)
Speaking of queries, the ones in the article are simple examples, but when you're pulling many columns and joining on multiple keys, repeating full table names over...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 1:28 pm
sushila (10/7/2009)
Jeff - ...are on your way to becoming a famous author as well...could you not teach people the art of keeping an even tone..?!;-)
Hello my long-time and trusted friend....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 1:20 pm
sql.varun (10/7/2009)
I have a question on Joins.Can anyone help me.
When I run below query it is running for 40 mins as it is using Table Spool.
Query:
select a.*,b.*
from table a
left...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 12:54 pm
David Walker-278941 (10/7/2009)
Jeff Moden (10/7/2009)
Actually, they ARE becoming required. The use of table names instead of aliases has been deprecated.
Even if they weren't, short table names may work fine...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2009 at 12:51 pm
Viewing 15 posts - 41,626 through 41,640 (of 59,102 total)