Hi,
I am faced with a critical problem.
We want to ensure that all the changes made to databases by developers are source controlled. Source control can be achieved by using TFS with VS DBPro. But users can use the same authentication (as they would know the userid and passwords) to make modifications in an offline DBPro project or through enterprise manager as well. Is there any way (by means of events raised in TFS etc) by which we can ensure that all database changes are through TFS, so that they can be tracked and source controlled
We cannot totally restrict access of developers. They need to have ddl_admin rights on database objects in Development servers.
Kindly give some suggestions as to how to solve this problem.
Thanks,
Restrict Access to databases other than through TFS
Gilles Lafreniere
Sanjukta -
Team Edition for Database Professionals should fit your need, if you follow our recommended model. We suggest that the developers use TEDP to build and deploy the database project to a isolated development environment (or sandbox), not to the staging or production servers. If you follow this approach, the developers can work on the database project; build, deploy, and test in their sandbox; and never have to touch the staging or production servers.
You, or another administrator, when the database is ready to roll out, would sync to the release version, generate the build script and them you'd be the one(s) to deploy it to a staging server, perform final testing, and then deploy it into production. The primary scenario for the first release of Team Edition for Database Professionals is exactly your desired scenario.
There are more details in the overviews in the user documentation.
let us know if you have additional questions,