I am currently working on a TFS 2008 to 2012 upgrade. Here is my situation: my current TFS 2008 box is Server 2K3 with SQL Server 2005 backend. I am not entirely sure what my upgrade paths are but I think the following 2 scenarios are the most likely:
Migrate the databases from SQL 2005 to SQL 2012 and then point TFS 2008 at the new SQL Server. From there I can upgrade TFS 2008 to 2012.
Spin up a new Server 2008R2 box and do a clean install of TFS 2012 with a SQL Server 2012 backend.
The network guys would really like me to do option 2 because they want to decommission the Server 2003 box but my concern is how would I get all of the data in TFS 2008 over to the TFS 2012 instance? I have looked around the MSDN and Google but I haven't come across any documents that explain how to do this kind of upgrade.
Additionally are there any pitfalls that I should be on the look out for?
Any help would be greatly appreciated!
The Microsoft Documentation doesn't make this abundantly clear so for anyone in the future that is in a similar situation this is a great little how to. Some of the screens vary to what you actually see but it is mostly spot on.
Some points
If you spread your Data and Application Tier across multiple servers make sure the user account you specify for 'Report Reader Account' has access to both servers and has the 'Log on locally' permission.
Pitfall: After getting TFS 2012 configured I was getting a strange URL exception when VS2012 attempted to connect to the imported project collection but not when trying to connect to a project collection created from within 2012. A server bounce corrected this problem.
All and all the process is very straightforward and TFS2012 stands up pretty quickly.
There is great documentation on MSDN: http://msdn.microsoft.com/en-us/library/ms404860(v=vs.100).aspx
Related
After cloning a 2010 TFS server, upgrading the clone's OS to 2012R2, upgrading SQL Server to 2012 SP2 (11.0.5343), uninstalling TFS 2010, and upgrading to TFS 2013 with update 5, we are running into issues starting the Build Service on the clone.
I've removed the agents and build controllers referencing the other original server through Manage Build Controllers, in Visual Studio 2013.
I've tried to use the TFS 2013 upgrade wizard and it fails when attempting to start the build service so I tried to unconfigure: "tfsconfig.exe setup /uninstall:TeamBuild" and reconfigure through the TFS 2013 upgrade wizard but it yielded the same result.
The TFS database server, Build Server, controller, and agent are located on the same box
For measure, I've even deleted the agents, controllers, and Unregistered and Registered the Build Service in the Team Foundation Server Administration Console as both the batch account used on the original server but that failed so to rule out authentication, I used my domain account (I'm a Local Admin, SQL Server Admin, and TFS Admin) but still had the same result with both accounts.
The Windows event log states “Service cannot be started. The handle is invalid”.
I'm not sure what else could be missed does anyone have any pointers?
There were over 100 Microsoft patches/updates applied over the weekend and the issue went away. Microsoft confirmed that the issue was related to the OS, not the TFS configuration or installation/upgrade.
Thanks for all your suggestions. Hopefully this will help someone else out if they are in the same situation and spinning wheels to find the answer. Keep your systems as up to date as possible!
Try to remove build service by going to Team Foundation Server Administration Console, select server name, and click Remove Feature, to remove build service feature, then re-configure it.
I am setting up VS 2013 for development with Azure SQL Database (I am new to Azure). I have set up a database on Azure and a Solution on VS 2013. The local machine is Windows 8.1 Pro, with SQL server 2014 Express. I am trying to import the database on Azure into the VS solution. I have changed the Target platform on VS to “Microsoft Azure SQL Database”. I have checked that VS can see the Azure database by using “Test Connection” – all appears well.
When I start the Import Database, I get the following error:
You cannot import a 1025 database because you project’s target platform is set to 130. To learn more about changing your target platform and/or source database, or the supported database editions for specific target platforms, please refer to Import Schema help page.
I cannot find the help referred to in the error message. I have tried changing the target to SQL server 2014, no joy. Can anyone give me some pointers?
This issue could be SSDT version issue. Can you download and install the latest RTM or Preview version of SSDT from https://msdn.microsoft.com/en-us/library/mt204009.aspx
If you need to try out all GA and Preview features of Azure SQL DB, SSDT Preview would cover it. Otherwise SSDT RTM version will provide the stability.
For this:
Created the SQL project
Set target to Azure SQL
Instead of "Import" did "Synchronize"
The numbers refer to they type of sql installation, with 130 being 2014, and 1025 being the azure cloud. Exporting data from azure is a little more complicated than you would expect with a VM, because of the way SQL Azure works behind the scenes. First to literally answer your question here is the link to how to use the import export services so you can get the DB on your local 2014 install. However I imagine what you want to do is actually develop for that server without some painful import export process, which is why I think this link that talks about what tools to use might be more helpful.
Anyway, good luck, SQL azure is very much a product in it's infancy.
I was able to work around the problem by working from VS 2013 and creating the Db in VS and publishing to Azure following the tutorial:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-get-started/
I hope I will not need to import a Db in the future!
Thank you to all those that edited & answered. I hope to be able to return the favour.
Importing from Azure into a Sql Server Project works in Visual Studio 2015 with no issues.
I am creating a site that is mainly used to view reports. The database is SQL Server 2008 R2 Express with Reporting Services. I was thinking of using Business Intelligence Development Studion to create reports since it integrates well and is easy to use. The site does not exist yet as the reports are its main feature.
I started using Visual Web Developer 2010 for the site since I thought it would work well. A Microsoft rep recommended that I use Visual Studio 2012 since it's compatible with SQL Server 2008 R2 and is the latest version. HOWEVER, it seems that report integration was stopped since Visual Studio 2008.
What tools should I be using for my reports and site? The database must be Microsoft but I am flexible about everything else. I am looking for tools that work well with the database.
I also want to use source control software that is compatible/works well with whatever IDE/software I'm using. Any recommendations?
Right now, I am the sole developer. I want to be prepared to expand to a small team once the project is underway and I want to be set up right the first time!
If predefined reports is the main feature of your site, i recommend you to go a level higher and use some tool that let you create and design reports easily, like DBxtra.
I don't know how else to ask this, and I think the title could be changed. I've been downloading different SQL Server Express versions, and I can't seem to find the one that has the Management Studio Express, the fulltext search, and the Reporting Services, replication, bi dev studio, management tools basic, sql client connectivity sdk, ms sync framework. I have found some installations have some of these, but not all of these features. To be honest I would like the full text search, the management studio express, and the bi dev studio, but they are lacking. where can I get these? Any help. I found info here:
http://www.mssqltips.com/sqlservertip/2024/introduction-to-sql-server-express-2008-r2/
http://www.sqlmag.com/article/sql-server/sql-server-2008-r2-express-installation-options
I've downloaded and tried:
SQLEXPR32_x86_ENU
SQLEXPRADV_x86_ENU
SQLManagementStudio_x86_ENU
SQLEXPRWT_x86_ENU
I installed the bare bones SQL Server 2008 R2 Express and I notice if I go to add shared features it doesn't show some of the other features, but if I add a new instance it gives me some (but not the ones I need). Can someone guide me please? Do I need to uninstall everything and try again?
My solution was to uninstall the sql express that I originally installed and then reinstall with advanced services and that included everything. I have no idea why it was not letting add anything additionally. Maybe someone has some thoughts on that (or some facts). Anyways it installed completely now. Thank you Dan for your efforts. Greatly appreciated.
What you're looking for is probably SQL Server 2008 R2 Express with Advanced Services. It's not SQLEXPRADV_x86_ENU which was mentioned in your post - that one looks not R2 version.
It's always difficult to find anything on Microsoft's site:
http://www.microsoft.com/download/en/details.aspx?id=22985
Thats the Microsoft SQL Server 2008 R2 RTM - Management Studio Express
The most actual link:
Microsoft® SQL Server® 2008 R2 SP2 - Express Edition
http://www.microsoft.com/en-us/download/confirmation.aspx?id=30438
Basic setup:
SQLEXPR_x64_ENU.exe - SQL Express 2008 R2 SP
Include SSMS:
SQLEXPRWT_x64_ENU.exe
Include Reporting Services:
SQLEXPRADV_x64_ENU.exe - SQL Express 2008 R2 SP with Advanced Services
Separate SSMS install:
SQLManagementStudio_x64_ENU.exe
What are the best practices in setting up a new instance of TFS 2008 Workgroup edition?
Specifically, the constraints are as follows:
Must install on an existing Windows Server 2008 64 bit
TFS application layer is 32 bit only
Should I install SQL Server 2008, Sharepoint and the app layer in a virtual instance of Windows Server 2008 or 2003(I am already running Hyper-V) or split the layers with a database on the host OS and the app layer in a virtual machine?
Edit: Apparently, splitting the layers is not recommended
This is my recipe for installing TFS 2008 SP1.
There is no domain controller in this scenario, we are only a couple of users. If I was to do it again, I would consider changing our environement to use a active directory domain.
Host Server running Windows Server 2008 with 8GB RAM and quad processor
Fresh install of Windows Server 2008 32bit in a VM under Hyper-V
Install Application Server role with IIS
Install SQL Server 2008 Standard edition
Use a user account for Reporting Services and Analysis Services
Create a slipstreamed image of TFS 2008 with SP1 and install TFS
Install VSTS 2008
Install Team System Explorer
Install VSTS 2008 SP1
Install TFS Web Access Power tool
After installing everything, reports were not generated. Found this forum post that helped resolve the problem.
Open p://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx
Run the webservice (see above link for details), it will take a little while, the tfsWarehouse will be rebuilt
It is very important to do things in order, download the installation guide and follow it to the letter. I forgot to install the Team System Explorer until after installing SP1 and ventured into all sorts of problems. Installing SP1 once more fixed that.
One critical thing you has to keep in mind about TFS, is that it likes to have the machine all to it self. So if you have to create a separate instance on Hyper-V do it using the proven Windows Server 2003 platform with SQL Server 2005.
I am sure Microsoft has done a great job getting it to work under Windows Server 2008 and SQL Server 2008, however you don't get any additional features with this newer install and it is currently unproven in the wild.
So my recommendation is to stick with what is known until the next release of TFS comes out.
Also splitting the layers is definitely not recommended, especially in the workgroup edition where you will only be allowed to have 5 licensed users. Those 5 users will never exceed the server's needs. Also my recommendation is to not update Sharepoint if you don't need to. In my environment, we don't really use Sharepoint all that much, so I left it alone. Sharepoint is usually, in my experience, where most of the problems come from with TFS.
I just upgraded our team to TFS 2008, from TFS 2005. The hardest part was upgrading SharePoint 2.0 to 3.0, so I would make sure to do that first, if you have not already installed TFS 2008. We had a couple of other difficulties, but they were all either related to the SharePoint upgrade, or to the fact that we were using an aftermarket Policy package - Scrum for TeamSystem. We are on SQL Server 2005, so I cannot address SQL Server 2008. As for splitting the layers, we did not do this either, as we are running on Windows Server 2003 and everything ran under the host OS.
Splitting the layers is only needed for more than 450 users.
I would also recommend having the Build Server on a completely seperate machine. Building is very file system intensive. SQL Server performs best when it has complete control of a file system - so having build and TFS on the same machine may create performance issues while builds are executing.
Perhaps this can be alleviated with proper tuning and seperate physical drives - but I'd think in the long run it would be a lot simpler to just either use some old hardware - or spin up a small virtual machine on a seperate host for your builds