Octopus 3.0 on SQL Server - DB Sizing

I like that 3.0 is on SQL Server, since I am a SQL Server DBA. I worry about capacity management and licensing, so have some questions. Since SQL Express is limited to 10GB max DB size and 1GB of RAM (yes you read that right - Microsoft wants your money and there free edition is very restrictive - see https://msdn.microsoft.com/en-us/library/cc645993(v=SQL.105).aspx), how can we estimate what the size will be and what the growth will be like over time?

Are there db archiving steps to reduce the size of the db? Since you are storing more in the db, I expect it to balloon in size, but I would think we wouldn’t want to store everything forever.

Hi There,

Thanks for getting in touch. We are using a new forum dedicated entirely to Octopus 3.0 questions where you can get in touch with the developers that are working on that version on a daily basis. http://community.octopusdeploy.com

A thread for that specific question has already been created, so feel free to jump into the conversation on this link http://community.octopusdeploy.com/t/whats-needed-for-sql-server-install/202