<div>
Stored procedure have a number of advantages over direct queries from PHP<br />
<br />
1. It separates your logic layer from your data layer. You can change the mechanics of the SP without changing the interface - so your code remains unchanged<br />
<br />
2. It is less prone to injection attacks and other security issues<br />
<br />
3. You can control access to the stored procedure with DB security independently of the application using it.<br />
<br />
5. A stored procedure is the domain of a DB admin who is skilled at ensuring queries are optimal. Programmers might not have the same skill<br />
<br />
6. There can be a performance benefit - stored procedures are cached <br />
<br />
7. Network load can be reduced. If your have a complex operation that needs to be done with multiple calls to the DB based on finite set of parameters - you can do that by calling the SP with the parameters in one call rather than multiple round trips<br />
<br />
8. Stored procedures can provide the same functionality across multiple applications.<br />
<br />
Drawbacks<br />
1. Programmability is limited compared to a language like PHP <br />
<br />
2. It might require employing an additional (DB) resource so has an impact on cost<br />
<br />
3. Only means of grouping functionality is by naming convention
</div>


<div>
You may think stored procedures will perform better, you may think defining stored procedures in the database layer is a better architecturial design than defining the queries in the application business logic layer.<br />
<br />
Here's a &quot;rant&quot; on the first assumption: <a href="http://www.joinfu.com/2010/05/mysql-stored-procedures-aint-all-that/" rel="ugc">http://www.joinfu.com/2010/05/mysql-stored-procedures-aint-all-that/</a><br />
<br />
Think about other metrics than performance, about maintainability, releaseability, tastabililty, flexibility and portability. <br />
<br />
Then look at some CMS or other PHP systems and see what part of the data access logic is put into their MySQL database.<br />
<br />
If you look at it from the perspecitive of using a Framework like laravel, which uses Eloquent ORM which is based on ActiveRecord, you are really far off using SQL in the implementation of an application. For a simple create, reade, update, delete example, look here: <br />
<a href="http://www.phpactiverecord.org/projects/3/wiki/Basic_CRUD" rel="ugc">http://www.phpactiverecord.org/projects/3/wiki/Basic_CRUD</a><br />
<br />
You are not concerned about how data access is done, this is managed by frameworks. Notice especially in the create sample code, first an object of a user is created in memory, not in the database. This new user is stored to the database with the save call. It's naturally also with SQL you first need to know what to save before you can do an insert. The intersting part is whether the ActiveRecord class uses stored procs to find,save,update, or delete data. What's your guess?<br />
<br />
Bye, Olaf.
</div>


<div>
@Ray Paseur<br />
&nbsp;In object-oriented design should I use stored procedures or use normal php queries?
</div>


<div>
Either one is OK. &nbsp;Use whatever you are more comfortable with!
</div>


<div>
While all Ray says is true there still are implementation decisions having been made by todays frameworks and/or CRMs, some may be old fashioned ways some modern API/CRUD or ORM type of approaches. To be very concrete about stored procs: I haven't seen anything using them, really. Laravel/Eloquent ORM/ActiveRecord in the end use PDO with prepared statements. That's close to stored procs, as it also makes use of caching, and - as the article about the misconception of stored procedure caching says - that's the same amount of caching per session/connection you can only have with stored procs, too, anyway. Besides MySQL is only one possible database to use as backend. ActiveRecord also supports MSSQL and Oracle. And thats thanks to PDO drivers for these databases, but also thanks to declaring that OOP abstraction Ray talks about.<br />
<br />
Setting up stored procs you just have another level of things to maintain, need a developer capable to maintain it, and that is not a php developer capable to do MySQL queries alone, you have to have a bit more knowlegde of MySQL specifics in terms of procedures, so this at least has the need for some more experienced PHP/MySQL dev.<br />
<br />
You are very new here and I don't know about your experience in PHP or development in general, databases or desktop application/website development, etc. If you begin, I'd not suggest learning MySQL up to stored procs, you'll find more info, tutorials and tools for the approach to handle querying with the &quot;normal queries&quot; approach, of which there are still plenty different ones, obviously starting on mysqli vs PDO and very directly using SQL queries or ORM (object relational mapping) frameworks, <br />
<br />
Bye, Olaf.
</div>


<div>
<div class="content wysiwyg-content">
Hello, All<br />
&nbsp; &nbsp;I want to know what is pros and cons between write application with stored procedures in php &nbsp;or with normal php queries.<br />
<br />
Is necessary to write each query with stored procedures.<br />
Which is the best way to create large application like any portal (ecom, travel, property etc.). <br />
in which scenario use stored procedures or use normal php queries.
</div>
</div>


Hello, All
   I want to know what is pros and cons between write application with stored procedures in php  or with normal php queries.

Is necessary to write each query with stored procedures.
Which is the best way to create large application like any portal (ecom, travel, property etc.). 
in which scenario use stored procedures or use normal php queries.

What is pros and cons between write application with stored procedures in php  OR with normal php queries.

PHP is a widely-used server-side scripting language especially suited for web development, powering tens of millions of sites from Facebook to personal WordPress blogs. PHP is often paired with the MySQL relational database, but includes support for most other mainstream databases. By utilizing different Server APIs, PHP can work on many different web servers as a server-side scripting language.