May 21, 2010 at 11:17 am
Hi guys,
I am trying to write the procedures for everyone on how to use SQL Server, at this time programers,managers go create tables,views, logins and delete/insert/update when they like it.
Is anyone have writen procedures what DBA role and what users need to do on creating thing?? Thank you
May 21, 2010 at 11:46 am
There are many different flavors of such policies.
The best thing to do is to write up a policy proposal and get your manager to sign-off on it.
The most straightforward starting point is that nobody creates objects directly in production and the object does not get into production except after review and testing and done via the dba group.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
May 21, 2010 at 11:57 am
Here's a quick guide. I typed it in 4 minutes, so it's just the basic idea.
1) A "Change Request" is created, specifying modifications needed
2) Developers make changes in Development area and test it.
3) Code Push document is created specifying all changes to push to Production
Include scripts. For instance, don't say "add field to table x". Include the code to add the field when it was done in DEV
4) DBA backs up stored procedures, views, table structures, data as needed. Full database backup could be required for major updates.
5) DBA pushes code and objects to Production, checking off items as completed
6) Any rollbacks can be done from the backed up objects
Ideally you have a Test area in between DEV and PROD and go through the process there first.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply