RE: More Ammo Against Dynamic SQL?
- From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
- To: <kjped1313@xxxxxxxxx>, "oracle Freelists" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 23 Nov 2009 15:49:45 -0500
Kelly,
Well, let's see from by history:
1) Syntax errors due to changing objects.
2) Syntax errors due to new versions of rdbms
3) Ease of troubleshooting when something does go wrong.
4) Less code to do the same job.
5) Increases in efficiency of the application. Try parsing a couple
thousand statements per minute & you can really start talking response
time.
6) Shorter lock intervals & the resulting increase on concurrency.
Dick Goulet
Senior Oracle DBA/NA Team Lead
PAREXEL International
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kellyn Pedersen
Sent: Monday, November 23, 2009 3:01 PM
To: oracle Freelists
Subject: More Ammo Against Dynamic SQL?
I am working on a presentation to convince my company against some of
the dastardly dynamic SQL that we have in our code. We perform
everything from inserts, updates, deletes, selects and CTAS' all with
dynamic SQL and it's killing me!
I would love any new reasons NOT to use it, as I have all the standard
reasons like, inability to reuse sql in the buffer, parsing issues, bind
peeking issues, execution plan instability, etc..
Thanks for the assist! :)
Kellyn Pedersen
Multi-Platform DBA
I-Behavior Inc.
http://www.linkedin.com/in/kellynpedersen
"Go away before I replace you with a very small and efficient shell
script..."
Other related posts:
