Viewing 15 posts - 53,506 through 53,520 (of 59,098 total)
Sushila! Haven't run into any of your posts in quite a while! So very happy that you're still part of the "community" and very happy to "see" you...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 8:39 am
DonaldW (12/20/2007)
GilaMonster (12/19/2007)
Jeff Moden (12/19/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 8:05 am
You bet... let me know how it works out for you. And thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 7:30 am
Actually, those are pretty good links... Thanks, Steve.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 20, 2007 at 7:29 am
Heh... you've all probably seen me post this before... Interviews with people who claim to be experts at T-SQL usually stink. In particular, I had one guy with (supposedly)...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 11:22 pm
Heh... You forgot some.... 😀
Protect the data, at all costs.
Protect the server the data is on, at all costs.
Help most developers tune queries while teaching them what good set based...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 11:03 pm
... and don't panic... hit the books on those areas that you're light in... remind the future employer that your resume said "developer" and that you've got some boning up...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 10:35 pm
FP (8/8/2007)
True Love is Like A Ghost. Everyone Talks About It & Nobody have seen...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 10:09 pm
Not that it matters, but I really like the BCP method... it's pretty darned fast, too. As Adam mentioned, it call also capture the bad rows in a separate...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 4:37 pm
EXEC sp_Help tablename
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 4:31 pm
Funny how things work out... the original poster ended up helping a rider 😉 Nicely done, Hilderman!
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 4:22 pm
Want a great answer that's actually been tested to work... quickly? Then read this, please...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 4:16 pm
What were the "tweaks"?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 4:13 pm
P.S.
Technically speaking, the LEN() example does, in fact, come up with the WRONG answer if you are looking for precisely 3 digits...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 3:04 pm
Heh... no need :blush: ... dunno what I was thinking about, but I was wrong... the LIKE will use and Index Seek... the LEN will not... here's the code...
DROP TABLE...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2007 at 2:53 pm
Viewing 15 posts - 53,506 through 53,520 (of 59,098 total)