October 14, 2011 at 5:39 am
Hi
I hope someone could provide me some feedback on this issue.
On day to day basis I (the DBA) interact with our in house development team regarding our web platform. One of my tasks is to implement changes to our SQL server databases that function as back-end to our websites. How does one normally handle handover of database scripts, so it's easy to go back and see what was done when, track changes etc.
Our devs use Git as source control, but as IT I don't want to have access to the Git repository since this also contains all our source code. It is not an ideal situation to mail over scripts regarding database changes, and store them in a mailbox.
I guess there might be some fellow DBAs out there with similar challenges. Any feedback on how we can do this process as streamlined as possible?
/Andy
October 14, 2011 at 5:59 am
andy.l (10/14/2011)
HiI hope someone could provide me some feedback on this issue.
On day to day basis I (the DBA) interact with our in house development team regarding our web platform. One of my tasks is to implement changes to our SQL server databases that function as back-end to our websites. How does one normally handle handover of database scripts, so it's easy to go back and see what was done when, track changes etc.
Our devs use Git as source control, but as IT I don't want to have access to the Git repository since this also contains all our source code. It is not an ideal situation to mail over scripts regarding database changes, and store them in a mailbox.
I guess there might be some fellow DBAs out there with similar challenges. Any feedback on how we can do this process as streamlined as possible?
/Andy
A similar discussion is going on SQL Central. Please follow it.
Source Control Vs Email -- Are you serious...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply