Viewing 15 posts - 57,661 through 57,675 (of 59,067 total)
If the columns a VARCHAR or the like, you can use SOUNDEX (won't work on numbers).
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 7:05 pm
It's not SQLAgent that you need to be concerned with... it's the security setting on the server itself... WHO is the SQL Server SERVICE logging in as? If it's not...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 7:02 pm
What's wrong with LEFT(somentextval,100) ??? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 6:54 pm
I absolutely agree with using a tally table as Remi and Sreejith have... I just can't bring myself to create a tool that helps avoid cursors and loops by using...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 6:42 pm
Yes... instead of using the "-o somefilename" parameter, use the DOS "redirect as append" characters ">> somefilename".
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 6:33 pm
Sorry Vandy... I just can't read minds today... what's not right about the total sum?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 6:37 am
Vandy... how about telling us which columns the +ive and =ive numbers are stored in? If they are both in the InvoicedValue column, then Marino's should have done the trick...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 5:30 am
Better make sure you do a backup before you truncate the log or you won't be able to recover to a point in time which is the purpose of Full...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2006 at 5:00 am
Sure... what's the Primary Key of the person table?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2006 at 5:24 pm
Maybe this weekend... right now, I'm still sucking my thumb wonder what the heck I was thinking ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2006 at 5:21 pm
I'll say... as for me, I can't find the examples I had made for something else (might not even be the same problem
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2006 at 7:27 am
Outstanding... thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2006 at 6:52 am
Ok... first things first...
Rob... I'm confused... I thought you were saying that some sproc OUTSIDE of the trigger was being rolled back and that you need what was happening inside...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2006 at 8:56 pm
The only way to keep from rolling back the record inserted by the trigger, is to do it with another connection.
SP_OA could be used to create such a connection...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2006 at 6:54 pm
...and, still, if you have FULL RECOVERY set, none of that will help the LOG file because all of the updates will be recorded whether they be single updates, batches,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2006 at 5:54 pm
Viewing 15 posts - 57,661 through 57,675 (of 59,067 total)