A feature that would be handy for the backup script with regard to the @Databases parameter would be the ability to select databases based on recovery model. I could see three extra options and they would be (USER_DATABASES_SIMPLE, USER_DATABASES_FULL, USER_DATABASES_BULK). We could then do backups based on recovery model to different network locations. Sure, I could select the databases by name, but that is not dynamic and would require someone to remember to change the backup jobs if a new database were added. Anyway, it’s just something to consider. Thanks.
Could you elaborate on how you use these different network location further downstream in the recovery process? I'm curious to hear the benefits of separating especially the BULK and FULL recovery models.
A feature that would be handy for the backup script with regard to the @Databases parameter would be the ability to select databases based on recovery model. I could see three extra options and they would be (USER_DATABASES_SIMPLE, USER_DATABASES_FULL, USER_DATABASES_BULK). We could then do backups based on recovery model to different network locations. Sure, I could select the databases by name, but that is not dynamic and would require someone to remember to change the backup jobs if a new database were added. Anyway, it’s just something to consider. Thanks.