We are working with SMSQL and noticed something that could be a major issue. When we create a backup job, we select the databases to be backed up at the server level, which automatically selects all the user databases below. Once the job is actually created, whether through the SQL agent or a scheduled task, the command actually specifies the DB’s to be backed up. When databases are dropped or added (by the developers), it seems that SMSQL will have to be run again to cover the appropriate databases. Is it possible to setup the jobs to just cover all the User databases without actually selecting the databases through the wizard each time a database is removed or added?