Viewing 15 posts - 45,256 through 45,270 (of 59,101 total)
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
Grant Fritchey (2/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 10:57 am
Garadin (2/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 10:54 am
The reason why is because the correlated subquery that makes the count gets executed for every row in your temp table. You need to do a little "pre-aggregation" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 10:47 am
You're welcome... just remember... if recursive triggers are turned on, you have to take special steps when a trigger updates it's own table or you end up with a really...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 9:17 am
Jonathan Kehayias (2/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 8:27 am
Richard M (2/7/2009)
Boy, am I glad to be "someone" now.....
More than that, I've got a pretty healthy respect for you because of the way you just responded and...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 8:06 am
Phil Factor (2/7/2009)
I see CLR more as a way of providing extensions to the SQL Server system to handle complex data. Now that is really exciting.......
For what it's worth, that's...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 7, 2009 at 7:36 am
idrees.butt (2/6/2009)
What on Earth are you talking about... you said you have an ap with performance problems and that you wanted to write some SQL to fix it. You...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2009 at 11:38 pm
Jonathan Kehayias (2/6/2009)
so I did it the right way, rather than the easy way
BWAA-HAA!!! Man, I'm right there with you on that one! Now, all we have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 6, 2009 at 11:15 pm
Viewing 15 posts - 45,256 through 45,270 (of 59,101 total)