Viewing 15 posts - 47,161 through 47,175 (of 59,095 total)
I've got a hell of a lot of comments to make about this article... but, let me summarize, instead...
[font="Arial Black"]"Oh... very well done. Should be required reading for everyone...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:17 am
BWAA-HAA! I guess it's because I need more coffee, as well! Maybe that qualifies. ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:09 am
Just remember that you will get an advisory about total row length exceeding 8060 bytes if you use more than a very small handful of columns in the same table...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:07 am
Garadin (11/18/2008)
Jeff Moden (11/18/2008)
The really good part about it all is that no matter what goes wrong, I always learn something new even if it's only how to "read minds"...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:02 am
mpdillon (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:58 am
vkundar (11/18/2008)
gborasaniya you are right as this in data warehousing environment mainly in ETL we have constraints on using or creating indexes. we need to deal...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:35 am
Chris Morris (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:30 am
Dooza (11/18/2008)
... and was setup like this by the developers.
Heh... of that, I have no doubt. Thanks for the feedback, Steve. ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:27 am
Grant Scanlen (11/18/2008)
It will never be the case that the values in any of these columns will exceed 900 bytes, as the underlying data type is numeric(28,14).Grant
I guess SQL_Variant will...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:24 am
aaa (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:19 am
Dooza (11/18/2008)
am so glad my server ain't screwed!Steve
Man, me too! Thanks Chris. Sorry I forgot about the server maybe being case sensitive... that's the good thing about...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:08 am
Chris Morris (11/18/2008)
Jeff Moden (11/17/2008)
Chris Morris (11/17/2008)
Jeff, perfick solution as always!Serious or sarcasm? Can't tell from here.
Aw Jeff you should know me better than that!
This...
WHERE t.N BETWEEN CHARINDEX('(',@String)...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:05 am
Heh... thanks Jason. Maybe I should change my avatar to [font="Arial Black"]รพ[/font], huh? ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 4:58 am
Dunno which one you're looking for, but the following article has one of the better ways of doing it...
http://www.sqlservercentral.com/articles/T-SQL/63003/
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2008 at 9:37 pm
Why does the dimension table have dates that have been converted to varchar to begin with?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 17, 2008 at 9:34 pm
Viewing 15 posts - 47,161 through 47,175 (of 59,095 total)