vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| |||
| Subbu wrote: > Could anyone tell me the overheads involved in inserting/updating > records using MERGE statement and normal DML statements if any. As opposed to doing the same work with pl/sql? Run some tests and benchmark it against your system. Measurements of overhead will be more accurate that way. FWIW, I use merge statements hundreds of times per day (in jobs), and it works fine for my needs. |
| |||
| Subbu wrote: > Could anyone tell me the overheads involved in inserting/updating > records using MERGE statement and normal DML statements if any. Not sure whether I understand the question .... are you asking whether "the Merge statement, with it's ability to perform the merge operation in one pass, is better or worse than multiple passes using separate DML sequeneces like {update where matched, delete where matched, insert new} or {insert new, update all} or other variant?" (If you are asking this, then I suggest you could perform your own tests and look at the resulting stats - much easier to understand that way.) /Hans |
| ||||
| subramanianl@coolgoose.com (Subbu) wrote in message news:<5453a1e4.0404201459.bd3c0cc@posting.google.c om>... > Could anyone tell me the overheads involved in inserting/updating > records using MERGE statement and normal DML statements if any. http://download-west.oracle.com/docs...6sqlpl.htm#432 for the basics. http://otn.oracle.com/products/oracl...ily/dec11.html for examples. http://otn.oracle.com/products/oracl...iroment_9i.pdf for Oracle idea of the performance gain with specific percentages for a specific test. jg -- @home.com is bogus. Heck, I've seen better than this: http://www.interactivetools.com/staf...damons_office/ |