I have been looking for solutions to providing source control for my SQL Server 2012 instance. I have looked at Red-Gate's solution but it is outside my price range. Since I already make use of Visual Studio Online (VSO) source control for my .NET projects I was wondering if it was able to provide source control for SQL Server?
I have seen articles (listed below) that discuss using Team Foundation Server (TFS) for source control however I do not have a dedicated TFS server, just VSO.
Use Team Foundation Server (TFS) as your Source Control in SSMS
Using the TFS as a source control repository for SSMS projects
Has anyone made use of VSO to handle source control for their SQL Server database?
I would definitely recommend using Visual Studio Online or Team Foundation Server to hold your database scheme in version control. There is a fairly recent article in Visual Studio Magazine that discusses using the SQL Server Data Tools (SSDT) to be able to make that easier for you: Simplifying Development with Visual Studio Database Projects. SSDT is available for any version of Visual Studio including the Community and Express editions.
Redgate was out of my price range too unfortunately...
The SSDT tools for VS are amazing, and i recently started using it for comparing DB versions - and then generating change scripts.
Here's a start point if you want to get into that...
Other Free Alternatives?
Liquibase
gitSQL
Liquibase - i couldn't get my head around but if you can get it working, it may be better for other databases, if you have the requirement to use other databases.
I use gitSQL - it's free up to 20 tables...
If you have more than 20 tables then it costs $40 - which is still so much cheaper than the redgate solution.
gitSQL are also setting up command line options in a future release, so potentially you could run it via a batch file, and set up continuous integration.
gitSQL are also talking about postgres, mysql editions in the future.
Related
I need to create a database project in Visual Studio 2015 for PostgreSQL databases. Then we can maintain version control of each database object in the form of SQL script file. So, is there any such provision (may be in the form of plug-in) in Visual Studio 2015?
EDITED:
We're already using Team Foundation System (TFS) as our version control system for all of our projects. So, we would like to use the same for Postgres scripts also. Our projects are developed in .Net on Windows OS, even the Postgres is now running on Windows Server. What we want is to use Visual Studio only for creating a database project for Postgres (similar .sqlproj for Microsoft SQL Server) so that we can maintain version history of table schemas in the form of SQL files, build the project and deploy whatever server we need. Hope I have provided enough information now.
This tool looks promising when I went through the available information on website. But when I downloaded free version and when I am trying to install in my local I came across the following error.
OPS-008: OpsHub Visual Studio Migration Utility requires Team Foundation Server 2012 Update 1 Object Model or above.
Do I need to install this software on the server ? No where I could find instructions for installing this software.
Can I get this explained please, we are planning to migrate our project to VSTS.
If you want to migrate from TFS on premise to VSTS, I would suggest you to evaluate which of the three options listed by Microsoft documentation suite your need.
The easier way would be to chose option 2, especially if you already have TFS2015update3 or TFS 2017, as you need to upgrade your TFS collection to one of those version anyway before migrating (and you save the upgrade hassle).
If you want to use OpsHub tool, then you need to install the standalone TFS Object Model for TFS 2012 update 4 where you run the OpsHub tool, not on any of the TFS servers.
In order to run OVSMU, you will have to install TFS Object Model 2012 on the machine where you are installing the tool. This is a pre-requisite and be rest assured this version of OM will not conflict with any other (newer) version of Object Model already existing (which comes bundled with Visual Studio installer) on that machine.
I am looking to migrate from TFS 2012 on-premises to Visual Studio Online using the OpsHub Visual Studio Online Migration Utility. I have run into an issue that I can't seem to find a resolution for. To eliminate any customization, I have created a brand new team project in TFS 2012 using the process template SCRUM 2.0. I did nothing else after creating that new project. The goal was to run the migration utility on this new project to see if I can get it to work. During the migration, it fails with the error "Template Customization or Template Mismatch Error". Since I know for sure we never modified the SCRUM 2.0 process template that I used to create this new project, I assume the error is more with the fact that TFS 2012 SCRUM 2.0 template is different that Visual Studio Online. Using TFS Team Project manager utility I can see they are quite different.
So the question is, does OpsHub not support migration from TFS 2012 to Visual Studio Online when no customization to process template was made? It does not look like it does unless I am missing something. Can anyone help me determine what I need to do to make this migration a success.
Thanks,
The OpsHub tool supports migration only when the local template matches the target template. You will need to upgrade your Scrum team project to the latest scrum template to proceed.
You can also use the TFS Integration Tools to migrate with a mapping between the two templates. That might work better for you, but the TFSIP is significantly more complicated than the free OpsHub took. But that complexity brings features.
Tool is throwing error because the fields listed in error have display name do not match fields in VSO. In upgraded process template version 2.2 and other above version they have space included in display name such as Related Link Count. To overcome this error you can upgrade the process template version to 2.2 or use witadmin.exe tool to change the field display name. For more details visit here
I want to migrate all the source code from a TFS 2008 server to a new installation of TFS 2010. There are no work items, reports or portal to migrate, only source code. We want to move to a new process template and don't want to make an upgrade of the template used in TFS 2008 projects. Are there any good tools to only migrate source code? I've done some tests with TimelyMigrations TfsToTfs but they don't seem to work well when migrating a lot of source code.
Has anyone tried to use Team Foundation Server Integration Tool? I suppose you need to upgrade the TFS 2008 to TFS 2010 before you are able to move the source code to a new TPC/TP with the process template we want to use (with fresh portal and reports). Is this correct?
Does no such plugin exist?
So to be clear, I realize that RedGate has their own SSMS SCC app, and I realize that VSS2k5 will integrate in. I'm looking to stay with Hg as that's where my source already is, and I'ld like to find something that my team can stay consistent with on their tools.
As is, I guess I'm going to have to just run it through TortoiseHg and a folder with manual maintenance. Which isn't terrible, but naturally it would be nicer if there was an app pre-existing that I could consume.
And no, I don't have the time or inclination to write one myself. Not before Summer 2011.
Thoughts or ideas?
There are two versions of HgScc plugin:
HgScc - uses old MS SCCI API, works with MS VS2005/2008/2010 and with some third party IDEs. Last version of this plugin was released in 2008. It is not actively developed anymore, because MS SCCI API is very limiting and does not allow a tight integration with Visual Studio.
HgSccPackage - uses MS SCC Package, works only with MS VS2008/2010. This version of plugin currently in active development.
To get the first version of HgScc follow the instructions here:
MSSCCI compliant Mercurial client
Red Gate SQL Source Control is looking into supporting Mercurial in a future version, http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/803713-mercurial-support-as-source-control-system.
SQL Server 2012 (Denali) is using the Visual Studio 2010 Shell as the basis for the new Management Studio. I haven't tried it yet but I am hoping that tools such as VisualHg will work in Sql Server 2012. I will update this post after I get on my laptop that has the 2012 SQL Management Studio installed.
Have you tried hgscc? I know it integrates with Visual Studio, but I haven't tried it with SSM