May 4, 2011 at 11:33 am
In our environment, we have sql developers and web developers(.net). is there an article that tells the best practice how sql developers work with web programmers, what their job boundaries, and what are the work flow, how they cooperate well?
Thanks
May 4, 2011 at 12:11 pm
There isn't a single set of rules on that.
Some places, the .NET devs can't put anything in the databases without approval from the DBA. Others, the DBA just helps when something in the code isn't working right, or causes a problem that the devs can't figure out. And everything in between those in other places.
Really, it'll be up to you to sort out territories and boundaries, or lacks thereof, with them. What works best for one team may not work at all for another.
- 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
May 4, 2011 at 12:45 pm
Thanks, here I really mean sql developers not dba,
I'm interesting to be a sql developers too, so just curious what is the work flow and how web developers work with sql developers?
For example , the web programmers will tell sql developers:
I would like to a stored procedure to pull ...
May 4, 2011 at 12:50 pm
SQLMyFriend (5/4/2011)
Thanks, here I really mean sql developers not dba,I'm interesting to be a sql developers too, so just curious what is the work flow and how web developers work with sql developers?
For example , the web programmers will tell sql developers:
I would like to a stored procedure to pull ...
I think it really comes down to the strengths of the individuals. If the SQL developers are the best at writing the stored procedures, then the web developers should tell them what data they want back and let the SQL developers create the stored procedure for them and the web developers should test it.
If the web developers happen to be better at creating stored procedures, then they should write them and have the SQL developers implement them. Flexibility is key.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply