Create more store procedure in Database

Posted by Dot Net Team under Sql Server on 12/14/2011 | Points: 10 | Views : 931 | Status : [Member] | Replies : 2
Create more store procedure in Database, any drawback or low performance problem occuring, it is true/false ? Explain it




Responses

Posted by: Hmanjarawala on: 12/14/2011 [Member] Bronze | Points: 25

Up
0
Down
kindly refer this url

http://www.codinghorror.com/blog/2005/05/stored-procedures-vs-ad-hoc-sql.html

Himanshu Manjarawala
Sr. Software Engineer@AutomationAnywhere
http://fieredotnet.wordpress.com/

Dot Net Team, if this helps please login to Mark As Answer. | Alert Moderator

Posted by: Hmanjarawala on: 12/14/2011 [Member] Bronze | Points: 25

Up
0
Down
Or in short

.Applications that involve extensive business logic and processing could place an excessive load on the server if the logic was implemented entirely in stored procedures. Examples of this type of processing include data transfers, data traversals, data transformations and intensive computational operations. You should move this type of processing to business process or data access logic components, which are a more scalable resource than your database server.

.Do not put all of your business logic into stored procedures. Maintenance and the agility of your application becomes an issue when you must modify business logic in T-SQL. For example, ISV applications that support multiple RDBMS should not need to maintain separate stored procedures for each system.

.Writing and maintaining stored procedures is most often a specialized skill set that not all developers possess. This situation may introduce bottlenecks in the project development schedule.

Himanshu Manjarawala
Sr. Software Engineer@AutomationAnywhere
http://fieredotnet.wordpress.com/

Dot Net Team, if this helps please login to Mark As Answer. | Alert Moderator

Login to post response