Skip to main content
The 2026 Annual Developer Survey is live— take the Survey today!
added 93 characters in body
Source Link
EndangeredMassa

We've used MS Team System Database EditionMS Team System Database Edition with pretty good success. It integrates with TFS version control and Visual Studio more-or-less seamlessly and allows us to manages stored procs, views, etc., easily. Conflict resolution can be a pain, but version history is complete once it's done. Thereafter, migrations to QA and production are extremely simple.

It's fair to say that it's a version 1.0 product, though, and is not without a few issues.

We've used MS Team System Database Edition with pretty good success. It integrates with TFS version control and Visual Studio more-or-less seamlessly and allows us to manages stored procs, views, etc., easily. Conflict resolution can be a pain, but version history is complete once it's done. Thereafter, migrations to QA and production are extremely simple.

It's fair to say that it's a version 1.0 product, though, and is not without a few issues.

We've used MS Team System Database Edition with pretty good success. It integrates with TFS version control and Visual Studio more-or-less seamlessly and allows us to manages stored procs, views, etc., easily. Conflict resolution can be a pain, but version history is complete once it's done. Thereafter, migrations to QA and production are extremely simple.

It's fair to say that it's a version 1.0 product, though, and is not without a few issues.

Source Link
marc

We've used MS Team System Database Edition with pretty good success. It integrates with TFS version control and Visual Studio more-or-less seamlessly and allows us to manages stored procs, views, etc., easily. Conflict resolution can be a pain, but version history is complete once it's done. Thereafter, migrations to QA and production are extremely simple.

It's fair to say that it's a version 1.0 product, though, and is not without a few issues.

lang-sql