Viewing 15 posts - 54,856 through 54,870 (of 59,072 total)
Heh... they won't be able to keep the appointment for the interview because their dates will be all haywire...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 9:28 pm
Actually, it's worse than nothing... leads folks into a false sense of security even though their data is flapping in the breeze 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 9:25 pm
Heh... yeah... please, hire me before you install it as a trigger 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 9:23 pm
Like what?
And, Yes, I know that inserting into the "middle" of a clustered index may not cause data movement right then, but it does take extra time to do the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 9:20 pm
Hi there, ol' friend...
Just a quick question... how would you use your fine function to split a whole table of data... or is that beyond the scope of the code?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 9:16 pm
Zee,
Couple of questions... trying to help a bit, if needed...
First, how long does it take your final code (thank you for posting it) to run on all of those rows?...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 8:56 pm
You can't... you would be sending unencrypted data over the wire. Defeats one of the two purposes of encryption altogether.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 8:24 pm
More generally the question is "when does a transaction end"? When the triggers on Table A are done processing or when all triggers on all tables touched by the insert...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 8:21 pm
Sheeeooottt... what I'm really amazed at is how many people ask for help, get it, use an answer to write a fix, and then don't share. :exclamation: I know...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 7:59 pm
Timeless jokes are always the best. Thanks, Steve!
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 7:52 pm
And, sorry about the triple spaced code... the IFCODE's used to work correctly and they don't seem to, anymore... can't even color the damned errors anymore... they really messed something...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 5:41 pm
I'm thinking there's a couple of bugs... I have a table that looks like this...
--===== Create and populate a 1,000,000 row test table.
-- Column RowNum...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 5:27 pm
Several hundred developers? What you really need is a good set of development standards... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 4:56 pm
Pass it forward, Jon... post the code you solved it with.
And, by the way, saving a timestamp (datetime) in a table as any character or integer based data is death...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 4:51 pm
Spot on! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
September 25, 2007 at 7:26 am
Viewing 15 posts - 54,856 through 54,870 (of 59,072 total)