Viewing 15 posts - 50,371 through 50,385 (of 59,091 total)
4 table idea sounds good to me. Could be 3 tables because a deposit is nothing more than a credit transaction. Payments are certainly different and should be...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:59 pm
Did you ever figure this one out?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:51 pm
Thanks for the explanation... why not just import the XML into a table as "real" data and use DateTime columns? Again, just curious...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:32 pm
Indexes don't interfere with the load if the table is empty at the beginning of the load.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:28 pm
Heh... wasn't meant to be personal, at all.
I'd make the startup size of TempDB whatever size it grew to after a month. 1 GB may not be enough... shoot,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:27 pm
Thanks for the feedback, Mike. I've been involved with such undocumented legacy systems before and I know the hell you're going to go through. Just remember the old...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:22 pm
Not a problem... thanks for the feedback. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:19 pm
15 table join with a non-indexable WHERE clause and a killer ORDER BY and we wonder why this code takes a bit to run? First thing to do would...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:16 pm
I think an ALTER instead of a DROP would probably work faster.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:10 pm
Yes... the INSERT/EXEC would be used to save the results in a table. If you get different results, use more than 1 table... nothing wrong with that.
Of course, you...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 7:07 pm
David Burrows (5/21/2008)
Keep think about submitting something but can't think of anything that ain't already been done 🙁
Actually.... everything I've written about is NOT new... Tally table is old...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 6:50 pm
On the truncation problem, everyone realizes that the table columns must be in the same cardinal order as the input file unless you use a format file, right?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 6:09 pm
Do you mean "ISO Standard"?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 6:06 pm
Consistency didn't stop 20 inch wheels from coming out nor has it prevented the use of 13" wheels on some small cars.
Whatever... we could go on forever... our ideas of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 5:27 pm
ntaylor (5/21/2008)
Jeff Moden (5/21/2008)
Properly done, written enforced standards won't prevent someone from trying something new,
Again, though. How do you measure when it's being properly done? You can easily measure...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2008 at 4:35 pm
Viewing 15 posts - 50,371 through 50,385 (of 59,091 total)