New answers tagged

2

Lots of people use version control with databases. There's more than one pattern for doing so and any number of tools but fundamentally its a sound way to go. Similarly I strongly advocate for local databases for developers if at all reasonable - you will get merge issues if you're changing the schema a lot, but you should be able to work out practices to ...


0

I had thought about a similar setup a few years ago. If you happen to use MS SQL Server, then Visual Studio and/or SQL Server Management Studio have some good tools to help with that. (Check out the database project in Visual Studio. It's made a lot of progress in recent years.) The only downside is the amount of work that needs to be done upfront, to build ...


4

We have a set of SQL scripts that we use to create and modify the DB between versions - as its text, its stored in the VCS and tagged along with all the other code. One of the scripts is a "set up default data" one, and another is a dev-specific script that sets all the usual environment, such as developer users. When you want a new DB, its trivial to run ...



Top 50 recent answers are included