Open object's script file from Source Control
When I link a database to source control (TFS), and then open an object from the object explorer I would have expected the file script in source control to open in the management studio window. Instead it simply scripts the object from the database server. I don't think this is really sql source control, it seems more like a polished deployment engine.
When a database is linked to a TFS source location, it should open the TFS file no matter what you do in the object explorer.
hogsWild
shared this idea
-
James
commented
A few benefits of opening the script file from the source control side (say it's in a branch):
* If you are working on a large/complex object, you can simply save your work in the middle of coding without it having to compile and deploy to the server.
* This model fits the traditional development better - where the developer is always working from files in source control (or local versions) and not directly changing source on servers.
* This model would work for multiple developers working against the same development database. -
In SQL Source Control, the database is your working copy. We have not changed the behaviour of SSMS so that you can continue to work directly on your db.
If you made changes to the database, then that's what we would show you when you open the object so you can continue making changes and testing these changes until you are ready to commit/check in the changes. At the bottom of the Commit tab, you can see how your database object differs from the script in source control. This is very similar to doing TFS Compare my workspace to latest version in the source control server. (In SVN, this is like comparing the latest revision to your working copy.)
