Visual Studio Online migration utility very slow - azure-devops

we are migrating from TFS 2010 to Visual Studio Online. Our biggest Team Proyect has 14k ChangeSets. We are trying to migrate but based on the current "speed" it would take about 18 days to migrate.
I now there is a similar thread but:
Slow TFS migration from on-premise to TFS online with OpsHub tool
but it does not provide a solution. So I'm asking for help.
For TFS 2010 we have one Application Tier Server, a Database Tier Server.
Both Servers are performing ok (Memory, CPU,Network) during the migration
We are launching the migration Utility from a differect computer which also has ok performace (Memory, CPU, Network)
But in 12 hours, only 400 changesets has been migrated.
We are using version 1.0.1.008
Thanks in advance

Update from OpsHub.
We have done major performance improvements in the current release.
It would be available to public by the end of this week.
Thank you Christian for your assistance in this case.

A rule of thumb is that it will take as long to migrate your history as it took to make it in the first place and those times are not outside the bounds of reality. I would ditch the history and move just the tip.
Clarification: No that is not slow that's just how long it takes to do migrations.
If you have a lot of modifications to code and or work items then it will take a very long time. You can make things faster by throwing processor at your source server and sticking a fat pipe in the way, but you are network bound.
You could spin up an Azure server in the same data center as your target VSO and install and configure your TFS 2010 environment there. Then run the migration. That will be much faster, and will still take a long time.

Related

Using Visual Studio Online (VSO) for SQL Server Source Control

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.

iPhone: For integrating Code versioning thru SVN, is it necessary to upload files on a Server?

Please forgive my ignorance, but I am noob.
I have 4 Macs in my Office. I want to integrate SVN repository with XCode so that all of us can work on same project at the same time.
Is it necessary to setup SVN repository on a remote server? Can it be installed on any of these 4 Macs?
Please let me know.
No it's not necessary, but it definitely helps to avoid some nagging problems that can come up when you install the SVN server on a developer machine. For example:
Developer machine needs to be rebooted because he installed software, or ran into memory issues, or applied a patch etc etc.
Developer forgets that he is hosting the server and shuts down for the night. Meanwhile you were wanting to burn the midnite oil but don't have the latest revs.
Developer kicks power cord while you were in the middle of a commit.
Developer browses to a 'work related' site and now he's getting Russian bride pop-ups every few seconds. Frack, time for a reformat and darn if you don't gotta move the SVN server too.
... I'm sure you get the drift
SVN is pretty forgiving, and to be honest you could probably scrape by with installing it on a dev machine, but using a dedicated server is so much better.
Now, if you really want an SCM solution that Just Works, take a look at Git. XCode actually supports it natively and it's designed to work server-lessly. IMO it's a much better tool than SVN and worth dedicating some time to learn.
Good luck!
You can certainly use SVN locally with a repository that is a file on your local machine. However that's not what you want. You want to share files between computers, in which case you'll need one of the computers to be a server.
Here is a good guide for setting up svn on the mac: Subversion Server Guide Mac
The quickest option is to use a service like Beanstalk (http://beanstalkapp.com) to host the repository. Then you wont' have to mess with server setup and admin.

Mercurial and SQL Server Management Studio GUI plugins?

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

TFS2008 to TFS2010 migration upgrade

All,
I'm currently in the process of attempting to create a repeatable process for the upgrade of a TFS 2008 installation to new hardware in what Microsoft call a migration upgrade, but am experiencing issues when building the VS 2008 projects on the new hardware.
Our TFS 2008 installation consists of two machines; one which houses the SQL databases and Application Tier, and the other which acts as a dedicated Build Server.
The new hardware for our TFS 2010 installation consists of two machines; one which houses the SQL databases, Application Tier, SharePoint and the Reporting Services.
So far, I have managed to successfully repeat the backup of the necessary TFS databases from the original server to the new server and restore them, followed by the 'tfsconfig import' command to successfully import and upgrade the databases to a Team Project Collection. The Team Project Collection appears correctly, and it is immediately usable. All security settings, shelvesets, workspaces etc. are intact.
Our issues start when we begin trying to build solutions. We are initially trying to build these solutions without upgrading them to the VS 2010 format, nor modifying the target Framework of any of the projects.
We get the following errors when various projects build:
< filename>.resx(x,y): error RG0000: Could not find a type for a name. The type name was 'System.Collections.Generic.List`1[[< class>, < assemnbly>, Version=a.b.c.d, Culture=neutral, PublicKeyToken=9557797252b44220]], mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Line x, position y. [< projectfilename>]
ResGen : error RG0000: Could not load referenced assembly "< filename>.dll". Caught a FileNotFoundException saying "Could not load file or assembly '< filename>.dll' or one of its dependencies. The system cannot find the file specified.". [< projectfilename>]
Various 'ambiguous' MSBuild target references when compiling workflow-related projects:
C:\Program Files (x86)\MSBuild\Microsoft\Windows Workflow Foundation\v3.5\Workflow.VisualBasic.Targets (153): 'GeneratedCodeAttribute' is ambiguous in the namespace 'System.CodeDom.Compiler'.
There are various suggestions about how to eliminate these issues, including modifying the 32-bit support flag on ResGen, or forcing the use of the 64-bit ResGen, and upgrading projects to VS 2010 format and changing them to target Framework 4.
Issue 1. can be fixed by changing the offending projects to target Framework 4, however this particular project cannot be upgraded yet due to compatibility issues, and I have not yet found a solution for issues 2. & 3.
We have upwards of 20 Team Projects, with multiple branches in each, and would therefore (due to the amount of work involved) like to avoid manually changing all projects/solutions (especially as some products cannot be upgraded to Framework 4 yet for compatibility reasons, and building Framework 3.5 targeted projects in Framework 4 MSBuild does not appear to be as compatible as Microsoft would have us believe).
If anybody has any ideas which may prove helpful, then please let me know.
Cheers,
Antony
EDIT:
Issue 1 has been seen by other people, and relates to resource files referencing generic lists of a custom type. As it turns out, these were superfluous in our project, so I simply removed them, and that build issue was history.
Issue 2 seems to have dissappeared all by itself, possibly as a result of fixing issue 1.
Issue 3 relates to building VS2008 Workflow projects in MSBuild 4, when they target Framework 3.5. Microsoft, in their infinite wisdom, have apparently chosen to not address this issue (Link to Connect site), and there are several ideas to fix it (referencing specific versions of the Framework, changing the build workflow to use MSBuild 3.5), none of which work.
So our upgrade to 2010 is on hold it would seem, until either the products for which we build the 3.5 workflows (CRM 4.0 and SharePoint 2007/2010) support Framework 4, or until Microsoft fix the issue.
EDIT:
Microsoft have admitted that there is an issue, and have released the following information relating to the above KB number: http://support.microsoft.com/kb/2023579
As stated in my commented addition on my original post, this issue relating to the workflows not building is indeed resolved by a patch for the Microsot .Net Framework 4 Extended, which is outlined in KB2023579, which has not yet been made public (at the time of this post).
This solution was provided by Microsoft through a support call, and as such I am bound by the terms and conditions of that call, which prevent me from distributing a link to the patch until the official KB article is made available, at which point I will post the link. Sorry.
Hotfix that worked for us: http://support.microsoft.com/kb/2249629

Are there really any production issues in using memcached in Windows?

I'm currently testing Memcached in a Windows machine and we are planning to use it in production while Microsoft Velocity is still in CTP. It is running well so I believe that Memcached for Windows will do well when our site is already in production. I'm reading some blogs pertaining to this issue and some of them just mentioned that it must not yet be used in production.
If there are issues, please tell why? And please, if you have any links about this matter, just post it here. Thanks.
There is no official release of memcached on Windows. We're working on it right now, but unless you're pulling from a dev branch or you've downloaded a pre-release, you've definitely got an unsupported version with a large number of bugs and missing features from the last couple of years.
I've been using memcached in production for several years now (since early 2008). We're currently using a 12-instance cluster and it absolutely hums. I would recommend memcached any day of the week.