SVN - Show Log (TFS - View History)
To have a tab that would simply grab and display the Log/History would be invaluable. This would be a fairly simple addition I would think.
Show history is now available as of v18.104.22.168. Please use Help > Check for Updates on the SQL Source Control tab within SSMS to make sure you have the latest version.
Ken - We're also looking at min/max support and hope to have that in the next release too. :-)
You're right. This early access release always shows the history at a db level. The next release, expected in Sept, will limit this to an object's history if you right-click and Show History from an object.
Steve Kaye commented
I've tried this feature and it doesn't behave as I'd expect. When I select an object and then right click > show history it shows the history of the database, not the object.
I think that it is very important to be able to show the history of individual objects to help track down when errors were introduced.
For example, suppose a particular stored procedure worked last month and appears to be faulty now. I want to look at the changes that have occurred in the time between when I know it worked and when I know it doesn't work.
I very rarely want to just look at the history of the project, I almost always want to examine the history of particular objects.
Looks great! Couple things (but they're lower priority and can probably go on as a separate case from this one):
1) The title bar should be clickable so we can expand the window quickly. Min/Max support basically.
2) It would be nice (from a process perspective) to be able to right click or select then click a button to revert individual objects or an entire revision. Helps when there's an issue that requires us to rollback a set or an individual change temporarily from a test DB or even a dev DB.
3) In the middle list (the list of objects), it would be nice to have a sortable column listing the object type. We can sort by the path which includes the object type but it'd be cleaner...in fact, having the type of object in one column, the name in another and the path off to the right (in case we need it) would be a better interface.
Again, all of these can probably be pushed into a separate set of cases.
If you take a look at how Tortoise SVN does it on Windows, you can see a nice way of doing it...not saying it's the best interface but it works. They list the revision history with revision number, date/time, person who committed and the first line of the comments. Click on an item and a second pane shows the full comments while a third shows the list of objects included in the commit. Right-clicking the object gives you various options which include diffs and the like. At the same time, you could leverage what you do in SQL Compare with the added layer of being able to highlight individual revisions to get the rest of that interface (showing the changed objects and diffs).
Andrew Tregonning commented
This should be integrated with the Diff feature requested here:
I think that the ability to be able to view and revert back to a previous version of a stored proc is essential for database development. As a previous person mentioned, there are some many commits that not having the ability to view and get back to an older one almost makes this tool not worth using.
I also think history would be an important feature to add.
Neil Burnett commented
With frequent commits, it is essential to see history so you know what you have done so far. I always use show log to show me where I got to last time I was working on a .NET project, so why not get it on database projects too?
I merged in another suggestion where the user thought this would be really nice to have the possibility to right click on an stored procedure and select view history in context menu. Then I in modal form with all revision of the procedure, select the one I want to see.
history will let me see who is getting in what in the event I need to trace a bug and indentify who did what and when.
Also will let me do Check Point Releases of the Database (i.e. when we release to customer x) so we can review what customers got and when.
history is really important to find out who checked in what and when.