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.
| Author |
Topic |
|
denis_the_thief
Aged Yak Warrior
596 Posts |
 Posted - 2012-01-04 : 09:27:26
|
| Sorry cause this is probably been posted before. But how do you administer table changes in Development? Our conundrum is this. Before, we let Developers make their own table changes. The problem was that when we got ready for testing or Release, things were out of sync amongst Development databases and we often did not know if a column existed as a Developer just trying something out or if it was a requirement. It was somewhat caotic. Now we have the table structure 'locked down' and all changes must got through the DBA. The new problem is that we get so many bits and pieces of requests. So either we have to keep dropping what we are doing to implement these requests or we are holding up the developers.I am sort of scrathing my head over the fact that Developers can maintain their own code with a software tool like Source Safe so why do we need a person to maintain the Database.Any ideas on a good solution or even a bit of an improvment? |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2012-01-04 : 10:02:12
|
quote:
Originally posted by denis_the_thief
Sorry cause this is probably been posted before. But how do you administer table changes in Development? Our conundrum is this. Before, we let Developers make their own table changes.
....and there is your problem...We review all requested changes to the databaseWe then, invariable say: "ARE YOU NUTS"Then figure out what they really need, and guide them to the correct solutionDevelopers DO NOT make changes to the databaseBrett8-)Hint: Want your questions answered fast? Follow the direction in this linkhttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspxWant to help yourself?http://msdn.microsoft.com/en-us/library/ms130214.aspxhttp://weblogs.sqlteam.com/brettk/http://brettkaiser.blogspot.com/ |
 |
|
|
Sachin.Nand
2937 Posts |
Posted - 2012-01-05 : 00:35:49
|
quote:
Originally posted by denis_the_thief
Sorry cause this is probably been posted before. But how do you administer table changes in Development? Our conundrum is this. Before, we let Developers make their own table changes. The problem was that when we got ready for testing or Release, things were out of sync amongst Development databases and we often did not know if a column existed as a Developer just trying something out or if it was a requirement. It was somewhat caotic. Now we have the table structure 'locked down' and all changes must got through the DBA. The new problem is that we get so many bits and pieces of requests. So either we have to keep dropping what we are doing to implement these requests or we are holding up the developers.I am sort of scrathing my head over the fact that Developers can maintain their own code with a software tool like Source Safe so why do we need a person to maintain the Database.Any ideas on a good solution or even a bit of an improvment?
Let me guess.. The developers are either having db_owner or ddl_admin rights.I would first remove those rights.Then I would create a ddl trigger on create and alter table and maintain a log the entries.After Monday and Tuesday even the calendar says W T F .... |
|
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2012-01-05 : 09:48:59
|
quote:
Let me guess.. The developers are either having db_owner or ddl_admin rights.I would first remove those rights.
No, they use to have full priviledges (Now we have the table structure 'locked down'). The new problems is this: Takes a lot of time to implement the Developer's requests and we have to keep dropping what we are doing otherwise we are holding them up |
|
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2012-01-05 : 09:59:42
|
quote:
....and there is your problem...
Maybe I didn't write this correctly but as I mentioned: Before, we let Developers make their own table changes. Now we don't.quote:
We review all requested changes to the databaseWe then, invariable say: "ARE YOU NUTS"Then figure out what they really need, and guide them to the correct solution
Thanks for the feedback. Partly why I asked is just to see how other departments/DBAs handle this situation.We didn't quite have the problem as you describe it. In our Department the thing is the Developers work closer to the business. So although their database experience may be less, they understand the business better than the DBAs and receive the requirements from the business.We are more in a maintenance mode so we have so many bits and pieces of requests sometimes we just wish there was a way they could administer this stuff themselves. Maybe there is software out there just like there is software to manage source code changes. |
|
|
|
|
|
|
|
|
Administering Table Changes