Right now when there are duplicate measurement data points oracle database does a batch insert (in one transaction), if that fails it will switch between a batch insert with commits and updates until all the data is inserted.
Oracle has the ability to use a MERGE statement to avoid all of this spinning.
Description
Right now when there are duplicate measurement data points oracle database does a batch insert (in one transaction), if that fails it will switch between a batch insert with commits and updates until all the data is inserted.
Oracle has the ability to use a MERGE statement to avoid all of this spinning.
added support for oracle MERGE statement in 3.2.5. Test using backfiller by cutting network connection. Also a performance test on oracle would be a good thing here as well.
Scott Feldstein added a comment - 13/Aug/08 11:26 PM added support for oracle MERGE statement in 3.2.5. Test using backfiller by cutting network connection. Also a performance test on oracle would be a good thing here as well.
Improvement
Closed
Major
Oracle needs to avoid spinning on duplicate data points
