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 |
|
bogey
Posting Yak Master
166 Posts |
 Posted - 2011-06-15 : 10:37:20
|
| We ran into an issue recently that has caused some confusion between the dba and developer. The issue being i was requested to move a table to another database with the same structure (its a test server). When the table was moved there were was another table that should of moved because of PK and FK constraints. I told the developer that as a dba I'm only moving what was requested and it shouldn't be the dba's job to search for any other objects that reference the initial object.Whats the consensus on dba duties in such a situation. Should the dba have to search for "all" other objects that need to be moved or is it the responsibility of the developer to communicate exactly what they want moved e.g. tables, constraints (disabling and enabling), indexes....thanks. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-06-15 : 11:01:24
|
| Both.The developers should know what they want and the implications of their request.It's our job to help them though. Especially when the change is to production. Then it is definitely our job to make sure the request is valid and complete.Remember it's a team effort. Too many DBAs make themselves the "bad guy" by always being the one to say "no." It's a giant mistake.I created a Migration Document that I expect developers to fill out for migration requests. It eliminates a lot of communication issues. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2011-06-15 : 11:28:57
|
| Agree 100% with Russell (well, I'm not too worried about being the "bad guy") :) If you don't have a defined process in place, with documentation, it's completely fair and professional for you to say "I can't/won't do this." Your responsibility is to maintain the system and keep it working. Even a test environment, because your change could impact other people's testing. If the devs feel that's too strict or time consuming then let them test on their own desktops. |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2011-06-15 : 11:34:44
|
quote:
Originally posted by russell
Both.The developers should know what they want and the implications of their request.It's our job to help them though. Especially when the change is to production. Then it is definitely our job to make sure the request is valid and complete.Remember it's a team effort. Too many DBAs make themselves the "bad guy" by always being the one to say "no." It's a giant mistake.I created a Migration Document that I expect developers to fill out for migration requests. It eliminates a lot of communication issues.
This was my first thought 
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
|
|
|
|
|
How developers communicate to you