Elvis Budimlic wrote:
My point is that by introducing constraints on System i, you're not only
enhancing database data integrity, you're potentially IMPROVING the
performance of your application(s). I've seen this scenario played out more than once (the ever elusive "magical
index").
The key word is potentially, of course. A lot of that depends on your use of SQL; you will not enhance the performance of native I/O by adding constraints. As Rob's numbers show (and mine even moreso), constraints really hog the machine. Rob's indicate that UNIQUE doesn't hurt at all, but my guess is that it will.

I guess my point is that the more we move into mixed-mode access and heavy use of SQL, the more we'll need a DBA position to help tweak the database. Because just leaving it to a blanket application of the most widely adopted practice of the day is almost certainly *not* going to give you the best results.

Joe

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].