This leads to problems when installing BAM – in particular the SSIS packages.
Background: SSIS does not install on instances – meaning it is installed at the root of the SQL Server servername structure. Therefore, if you install the BizTalk databases on its own SQL instance (servername\biztalk for example), you won’t see the BAM SSIS packages.
The problem is that SSIS doesn’t recognize instances, so you get an error much like below if you try:
The BizTalk 2009 installer doesn’t give you the option to configure the locations for these, so there's no way to fix this up front.
The packages DO get installed to SQL Server, but to the folder structure of the database instance rather than the root servername. If you log onto Integration Services using your root servername, you will get in, BUT you won’t see the SSIS packages.
The solution is to manually(!) migrate the packages to the proper (folder) instance – the root servername (not the instance), as shown below:
You may need to verify/validate the connection strings of the packages – I don’t think there were any changes, but you may want to do this to be safe.
