Why does the V12 Help say "The -b option should not be used if you are using LOAD TABLE"?
I agree that -b might not help a lot if you are using LOAD TABLE, but "not help a lot" is quite different from "should not be used".
For example, consider an application that uses both INSERT and LOAD TABLE to load masses of data... the INSERT operations would benefit greatly from dbsrv12 -b (no giant transaction log).
Why should that application eschew dbsrv12 -b simply because it also uses LOAD TABLE?
asked 24 Dec '10, 11:30
I can't think of any technical reason not to use LOAD TABLE at the same time as -b. Again, I think the documentation lost the spirit of the original sentiment. It probably was meant to suggest that you could have the benefit of no logging by using LOAD TABLE rather than resorting to -b which has lots of other consequences too.
Do you find -b particularly useful? Personally, I'd love to see it disappear. Writing to the log certainly doesn't come for free but many performance improvements were made in the logging code. If necessary (and if possible) maybe a method of inserting without logging could be added at the statement level (with obvious disastrous implications for recovery). Oh, and please don't take that last statement and turn it into "John suggests..." -- I don't suggest it but maybe we could be bullied into it :)
answered 24 Dec '10, 12:51