Viewing 15 posts - 45,241 through 45,255 (of 59,095 total)
Garadin (2/8/2009)
Is it good practice then to add all criteria to the derived tables instead of the outer query? Guess that makes more sense overall anyways.
I hate to use...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2009 at 10:52 am
andrewd.smith (2/8/2009)
OP does state the following which Jeff's query doesn't do.
I also want to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2009 at 10:46 am
Thanks, Osskey... I appreciate the feedback.
This doesn't apply just to forums when it comes to readability and self or embedded documentation. I started a consulting job about 7 months...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2009 at 10:43 am
webrunner (2/9/2009)
Thanks, Jeff,This is good advice for any type of forum post for help. But especially useful for SQL.
- webrunner
Thanks, WebRunner... I appreciate the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 9, 2009 at 9:37 am
heh... I was actually considering that. I just haven't had the time to do the animation.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2009 at 9:28 am
brian (2/8/2009)
There are other corrections...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2009 at 9:11 am
peace2007 (2/8/2009)
our tempdb file is 12GB, and he says it's so strange...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2009 at 9:06 am
aram_golbaghi (2/8/2009)
hii think smith is right
About what and why?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2009 at 9:01 am
Grant Fritchey (2/8/2009)
Guild?
Heh... better.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2009 at 9:00 am
Got it... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 6:09 pm
Then, it would seem to me that the data is being collected incorrectly. The GUI should prevent more than 3 answers from being entered. Otherwise, you're not following...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 6:08 pm
SELECT Name,
SUBSTRING(Name,NULLIF(CHARINDEX('.',Name,NULLIF(CHARINDEX('.',Name,NULLIF(CHARINDEX('.',Name),0)+1),0)+1),0)+1,100)
FROM dbo.ITEMS
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 12:14 pm
There's no link to the article you're talking about.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 11:47 am
Dave (2/7/2009)
Works perfectly. Thanks!
You bet... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 11:18 am
Ok... now... my question would be, why do you want to destroy data that you have by overwriting it? The answers to those questions, whatever they are, may prove...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 11:17 am
Viewing 15 posts - 45,241 through 45,255 (of 59,095 total)