Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 Sprocs - general question

Author  Topic 

Jake Shelton
Yak Posting Veteran

74 Posts

Posted - 2010-09-09 : 13:51:18
I know Procs are primarily used for repeated, 'on-call' results using precompiled plans, but are there any instances of SProcs being implemented after a system has gone live? Apologies if it's an odd question, I'm just curious.

Also, do you create your SP's more as a response to user requests or application vendor requirement? Or do you find vendors giving you scripts to run to creeat them?

Thanks,


Jake

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-09-09 : 14:02:17
I don't understand your first question.

We recommend stored procedures for application data access.

For vendor applications, the vendor's typically provide an installer or scripts to run.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Jake Shelton
Yak Posting Veteran

74 Posts

Posted - 2010-09-09 : 14:13:20
To put it another way, are there any types of procedures that are often added after a system is already live, perhaps to correct an oversight by the dev team or some other reason? Just wanted to get an idea of whether that kind of thing happens, and if it happens often.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2010-09-09 : 16:41:14
We have most of our Business Logic in Stored procedures. Because of their small "unit size" it is easy for us to release a change, or indeed to add more SProcs. They can be tested easily, and the risk of rolling out single-fixes / single-changes is contained.

Conversely if we made even a small change which was then compiled into a larger application module we would need to perform full QA tests - even if the risk was limited we might have screwed something up in the build process, accidentally checked out an incorrect version of a source code component (that wasn't intended to have changed) etc. etc.

Our system also has the the ability to have pages added (its a website) which are associated with stored procedures. So we can add a new web page, and stored procedure, and not change any application code at all. Thus easy to add extra functionality / additional maintenance / admin pages, and so on. They are most definitely in the category of "after the fact"
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-09-09 : 16:46:26
We regularly deploy new stored procedures and alter existing stored procedures for our applications. Our system is constantly evolving. We have regular application deployments that require SQL changes.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -