Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

deploying sp into production Expand / Collapse
Author
Message
Posted Friday, June 6, 2008 11:24 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, February 18, 2013 9:50 PM
Points: 119, Visits: 650
Hi to all.
I have a small doubt.
If we create a new stored procedure how we have to deploy it in the production environment.
Is there any down time required.
Is there any need to send any mail to the clients while deploying the sp.
Could any one tell me the exact procedure we have to follow while moving
the sp in to production environment.


thanks,
Sandhya
Post #513099
Posted Friday, June 6, 2008 11:45 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 15,444, Visits: 9,596
I can't say what procedure you must follow. It depends on the company policy, etc.

Technically, it doesn't require anything at all except running the script. It's policy, customer and technical desires, etc., that make it more complex.

Most of the time, it shouldn't require any down-time to deploy a new proc (or modified version of an existing proc). If it requires any changes to the front-end application, then that might require some downtime, or might not, depending on the application and the change.

The right thing to do is figure out what impact the new proc will have. Will it affect what customers see/do? If so, letting them know is at least polite, and possibly necessary.


- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #513117
Posted Friday, June 6, 2008 11:48 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Friday, June 27, 2014 12:43 PM
Points: 15,444, Visits: 9,596
I realized after I read my first post here that I'm making some assumptions.

I'm assuming you've tested the proc thoroughly.

I'm assuming you have a rollback script, so you can undo the change if it becomes necessary.

I'm assuming you have backups of the production database that can be restored if something goes horribly wrong.

I'm assuming you've coordinated the deployment with anyone else in IT/IS and with management.

Have you done those things?


- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #513118
Posted Saturday, June 7, 2008 4:49 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, August 14, 2014 8:21 AM
Points: 3,087, Visits: 1,433
If you have done all the things Gsquare mentioned, then my guess is that you will not have any problems deploying the new store procedure. It will help if you will say what the sp does.




My blog
Post #513380
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse