Viewing 15 posts - 53,161 through 53,175 (of 59,072 total)
Actually, I'm pretty much out of line here... I do everything from T-SQL... I've never written a DTS package and will probably never write an SSIS "package". My appologies...
......
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 9:38 pm
The real point here is that you should not be using any form of RBAR in a trigger... no matter how you do it, calling a RBAR proc from a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 9:34 pm
Sadly, no... no such luck.
About the only thing you could to is have the function return a special value and check that value in the calling code... if your code...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 9:26 pm
For future reference, please see:
Forum Etiquette: How to post data/code on a forum to get the best help
http://www.sqlservercentral.com/articles/Best+Practices/61537/
This will show you how to build a test case for others to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 9:12 pm
george sibbald (1/2/2008)
an object created by a sysadmin will always be owned by dbo...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 9:07 pm
My personnel belief is that cursors are the tools invented by the evil....
Heh... HOT DAMN! A kindred spirit! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 9:01 pm
There is a third option that lot's of folks forget about... that is the one of a formula in the code instead of an extra join or a dip on...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 8:59 pm
Aye... nicely done... glad to see you back in the swing of things.
Yep, I'm aware that ROW_NUMBER doesn't imply NOT NULL like IDENTITY does...
... but both Itzek's method and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 8:39 pm
Michael Valentine Jones (1/2/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 8:24 pm
Kenneth Fisher (1/2/2008)
Jeff Moden (12/28/2007)
This should do it, Mike...SELECT *
FROM yourtable
WHERE ISDATE(LEFT(yourcolumn,4))=1
AND yourcolumn LIKE '[0-9][0-9][0-9][0-9]-[0-9][0-9][0-9][0-9][0-9]'
Jeff,
Would this have been faster
SELECT *
FROM yourtable
WHERE yourcolumn LIKE '[12][089][0-9][0-9]-[0-9][0-9][0-9][0-9][0-9]'
AND ISDATE(LEFT(yourcolumn,4))=1
i.e. Restrict the 1st...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 8:17 pm
Mike Levan (1/2/2008)
thanks jeff.How can i enter time in tenths of an hour or has to check if the time entered is in tenths of an hour
Instead of adding "1"...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 7:44 pm
Heh... well done, Kenneth... that's one of my favorites, as well. The only time you really need a "split", is if you have to insert the rows into another...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 7:22 pm
Ian Yates (1/2/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:59 pm
Eric Stimpson (1/2/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:54 pm
Eric Stimpson (1/2/2008)
My message would be to challenge any use of distinct...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2008 at 6:47 pm
Viewing 15 posts - 53,161 through 53,175 (of 59,072 total)