BizTalk 2013 R2 database migration from SQL 2012 to 2014

On my Virtual PC which had BizTalk 2013 R2 configured with SQL 2012 as database server I thought of installing SQL 2014 and try using the new features of Column Store and see how it can help run the Integrations faster.
In this post I will show you how I migrated my existing BizTalk databases from SQL 2012 to 2014 which is installed on the machine.

•  Take Backup of all BizTalk databases from SQL 2012 and Restore it on to SQL 2014.
  

•  Create Scripts of all BizTalk SQL Jobs from SQL 2012 and execute it on to SQL 2014.
  

•  Create Scripts of all BizTalk SQL Logins from SQL 2012 and execute it on to SQL 2014.
  

•  Update the SampleUpdateInfo.xml file found in the following location with info of the current and the new SQL Server. For me current SQL 2012 was on KIWI server and the New SQL 2014 Server is on KIWI\SQL14.
  C:\Program Files (x86)\Microsoft BizTalk Server 2010\Bins32\Schema\Restore
  

•  Run the UpdateDatabase.vbs file which is found in the same folder which updates the Server references in the tables on the new SQL Server.
  

•  Run the UpdateRegistry.vbs file which is found in the same folder which updates the System Registry key references on the Server.
  

•  Finally I went into BizTalk Admin Console to check if the references were updated successfully and yes it did update everything.
  

Finally I would give credit to the following old Microsoft document which still holds true for  the new versions of BizTalk\SQL Server ;).
How to Restore Your Databases

Upgrading bug: BizTalk 2010 to BizTalk 2013 R2

Hi,
Upgrading has been made easy with newer versions of BizTalk. I recently upgraded the BizTalk software from 2010 version to 2013 R2.
Here are few screenshots....Important is the last screenshot.. :)

Here it talks about Pre-Actions required.
Stop WorldWide Web Publishing Service.
Start Enterprise SIngle SignOn Service.

Since I had selected to install Developer Tools also...it gives me an Error with missing prerequisites.
I installed Visual Studio 2013 and then continued on.

"Buckle your seatbelts....there are no Airbags to save you in this crash ride".
Microsoft will not rollback the databases if the Upgrade fails.
I did ensure that I had a backup of all the databases.

Forgot to stop RuleEngine Update Service.

And Finally the surprise...........

Seems Microsoft forgot to rename the Folder from "BizTalk Server 2010" in Program Files to "BizTalk Server 2013 R2" but product got upgraded successfully.

Hope they will fix this soon ;).