Last post Feb 20, 2011 12:10 PM by Lannie
Feb 17, 2011 01:11 PM|mrrogers|LINK
I am working on an ASP.NET project that has significant backend processing existing in PL\SQL. I was wondering if I re-write this code properly in C# can I get similar performance results or is the PL/SQL code going to beat my C# code every time?
Feb 17, 2011 01:29 PM|Shuvo Aymon|LINK
I will go for pl/sql. If anyone is an expert of C#.net with less knowledge in pl/sql then his c# code may perform better. but if properly written then most of the time pl/sql should bit it. You may choose your way depending on the situation. Performance
vs code readability. lake of time. better knowlege in which platform etc... you may also consider sqlclr based on your requirement.
Feb 17, 2011 10:34 PM|Lannie|LINK
PL/SQL is okay for calling a SQL statement to return, insert, or update data,
but if you need any kind of processing like LOOPS, PL/SQL is SLOOWWW compared to VB.NET or CS.NET.
Feb 18, 2011 07:50 AM|mrrogers|LINK
That is what I have always found, I do not buy that just having a compiled procedure close to the database garuntees that it will run faster. Not to mention C# can handle operations like multthreading that PL/SQL cannot.
Feb 20, 2011 09:27 AM|mrrogers|LINK
You are joking right? Have you hever hear of Oracle CLR stored procedures?
Feb 20, 2011 12:10 PM|Lannie|LINK
I use PL/SQL less and less, and move just about all database manipulations now into VB.NET and CS.NET in code behind form or code classes.
For some of my mega projects with millions of rows, avoiding PL/SQL and use of SQL Oracle Analytics has cut complex analytic processing time down from hours to minutes.
So for me, PL/SQL is history (toast), except for maybe some occasional inline functions for commandline SQL or JOBs used outside of the business intelligence applications.