We are extending our deployment process to include backing up the database(s) first. This will form part of a Powershell script, and just looking at the best machine to effectively run this on. Using Powershell means having access to the SMO feature, which typically is not installed on deployment web servers, but can/is on the octopus deploy server, and the actual SQL server itself. Should we install a tentacle on the octopus deploy server as well, then when setting the process, have it only run on that machine for the specific environment, or install tentacle on the SQL server and run it there?
Thanks for getting in touch! We would recommend doing this on the SQL server itself.
Do you have any specific concerns about installing it there?
Not at all. Can you still bind a process step to a machine role/environment if it doesn’t exist in a lifecycle? It’s not really an environment in the concept of a promoted environment, it’s just an environment in the process of another environment if that makes sense.
Yeah that makes sense. It doesn’t have to have it’s own Environment though. Do you have different SQL servers depending on logical or physical environments?
Such as Prod, Dev etc - It’s just another machine to add to those, and they would already exist in your Lifecycle, they would just have unique roles.
There are no set rules, if its easier to understand and manage it doesn’t have to be on the SQL server.