Attempted an upgrade of Identity Broker from v5.2 to v5.3, the upgrade process failed running the following SQL Commands
ALTER DATABASE [Unify.IdentityBroker_DEVAP610] SET RECOVERY SIMPLE;
ALTER DATABASE [Unify.IdentityBroker_DEVAP610] MODIFY FILE (NAME=[Unify.IdentityBroker_DEVAP610], FILEGROWTH=100MB);
ALTER DATABASE [Unify.IdentityBroker_DEVAP610] MODIFY FILE (NAME=[Unify.IdentityBroker_DEVAP610_log], FILEGROWTH=100MB);
The installer did not revert to the previous version of Identity Broker, instead it removed the service from the Services window.
I located the commands above in the Windows application log and attempted to run the command in SQL directly, it did not work as the files were named differently than names in the SQL Configuration.
In this case I renamed the SQL files as it is non-production and was able to run the installer successfully. I recall this issue with v5.2 and run through the DB manual upgrade process. I think this needs to be fixed for users that are not as familiar with installation options.
I am also not sure the settings should be made in the installer, if the SQL instance is clustered it will not support simple logging, also in large implementations I normally make the database file group by 1GB.
Customer support service by UserEcho