Settings and activity
4 results found
-
215 votes
jrummell
supported this idea
·
-
6 votesjrummell
shared this idea
·
-
24 votes
An error occurred while saving the comment An error occurred while saving the comment jrummell
commented
Perhaps. In my scenario, which may not be all that common, I'm writing views and stored procedures in our ERP database so that we can compose meaningful reports. Our ERP database has ~40,000 tables, and we don't care about the schema for 99% of these. We only care about the few that we've added. So if we could use SQL Source Control for only selected database objects, then we wouldn't need SSMS solutions.
An error occurred while saving the comment jrummell
commented
VisualSVN nor AnkhSVN will work because Management Studio doesn't officially support the Visual Studio add-in model. I've already submitted feature requests to both projects =).
An error occurred while saving the comment jrummell
commented
Or perhaps you could ignore (i.e. svn:ignore) certain objects?
jrummell
supported this idea
·
-
34 votes
That's something I've been pondering. There may be another issue for us. We only have two copies of the database, one for development and one for production. The database is just too big for each developer to have their own local copy. If multiple developers could use SQL Source Control on the same database connection (with svn:ignore), then we would prefer to do that. Otherwise, we would probably have to stick with SSMS solutions.