Is SQL Source Control meant to be used in production?
We are a very small team (five) that have a number of SQL Server DBs that we manage for an internal set of users. We have a development server and a production server. Sometimes changes are made in production for expedience. Should the source code control be set up against the production DBs, and if so is there overhead imposed by doing this? Will a production DB slow down because SQL Source Control is attached to it?
0 · Share on Twitter