SQL Source Control shortcomings
Let me start by saying that we've been successfully integrating Red Gate SQL compare Pro with different source control systems even before the initial release of SQL Source Control became available.
I finally now got a chance to evaluate the product (shared db model, TFS) and I believe it has several shortcomings that would make it difficult for me to justify paying for extra licenses for each developer working on the project.
Commits are painfully slow.
Even if I only change one object, it takes me 2 minutes to bring up the dialog to commit this change. If understand the way SSC works correctly, this can even be longer for larger databases. for the comparison sake, this operation takes seconds using TFS shell integration tools.TFS rules are ignored.
Our CM team enforces several rules in TFS:- required check-in comment.
- check-in association with a work item also stored in TFS. None of those two are honored by SSC:
- Check-in can be made w/o supplying a comment
- there is no interface available to create the work item association.
Thanks,
Igor
I’m declining this because it’s 2 suggestions in 1.
For 1, please vote on http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/462220-don-t-refresh-the-commit-get-latest-automatically.
For 2, SQL Source Control v3.3 now checks TFS policies on commit. :-) You can find out more information at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/726952-evaluate-tfs-policies-rules-when-committing-db-c.