According to the your installation Guide’s, SQL Requirements section, Octopus server supports one of the following:
Supported versions:
SQL Server 2008
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016
Supported editions:
Express (free)
Web
Datacenter
Standard
Enterprise
Microsoft Azure SQL Database
My question is: Is localDB also supported? I don’t want SQL Server Express to be always running in the background…
if it is supported, will LocalDB impact the performance taking into consideration that it will only start up when required, and so delay automations?
Thanks for getting in touch! localDB is not currently one of our supported Databases and is not something we are looking to support any time soon. Octopus expects SQL to be running at all times, this may cause some issues unknown to us. Octopus service does a lot more than just deployments, it performs a lot of background tasks and orchestration which is not suitable for localDB
The only advice we received from a developer was that you should ensure that your Octopus Server service run under a user account and not a system account.
We can’t see any specific reasons why it may not work, and you are able to try on a test instance, but supporting a large Octopus instance would not be recommended in a production situation.