What's the best way to set up SQL Server for 50 developers?
If I run an organization that has 50.net developers and they all use SQL Server, what's the best way to make one SQL Server for them?
Here are some of the problems I want to be careful about
- Should I configure database users per project or per user? or both?
- Do I have to provide a separate instance of SQL Server? Edit:
- How can I track the changes made by each user in the database?
There are a few more problems, but I think getting those two's answer would be a good starting point.
a source to share
You should definitely set up a database for each project, as this database should only have specific project objects. Also for backup and recovery purposes, a database for each project would be a good idea.
Setting up databases for your developers depends on how many developers actually develop for the database: create tables, views, etc. Database developers should probably have some kind of test copy of the database that they can use to develop their end, while "regular" developers work against a published copy of that database:
So the setup could be: 2 databases for each project, one for db development and one for other development.
Thus, changes to the database schema can be developed and tested first before driving out the rest of the developers.
a source to share