Upgrades and migrations -- which first?

Hi all,

Our installation is currently at 9.2.7, on a single-server installation of Windows 2008 R2 with SQL Server 2008 R2. After the first of the year I’ll start upgrading to get us on 9.5.4, and more modern versions of Windows and SQL Server. The DB team wants to split the SQL Server to a side-by-side installation, so that will happen as well.

The question is… in what order can we do this without going insane? I’m inclined to:

  1. Move the SQL to a side-by-side installation, with the new SQL server on the desired version.
  2. Update BigFix to 9.5.4 in place on Windows 2008 R2.
  3. Move BigFix to Windows (newer) on a new/replacement server.

Thoughts or ideas?


I agree with this approach.

Ideally when you move the BigFix application to a new OS / Server, it will have never had SQL on it ever.

1 Like

once you have a remote database, you can no longer perform BigFix updates through the automated fixlets, you have to perform them manually. with that in mind, I think I would reverse #1 and #2 on your plan. I think it could be done in any order either way.


Good insight @Entaille, thanks.

1 Like