SQL Server maintenance is just as important as creating backups of your databases.
Unfortunately, there are many companies out there that install a SQL Server database or more without setting up first their maintenance plans.
Everything is perfect as usually at the beginning there is no problem, that is until a problem appears.
SQL Server maintenance
Generally, the database doesn’t completely fail, but there are drastic drops in terms of performance as servers run out of disk space, or extremely rarely do databases become corrupt.
This is why it’s important that besides backup plans for your database, you have set up maintenance plans.
Most of the time you have a simple operation that you want to be part of your maintenance or backup plan. These general tasks are already available in SQL Server and can be set up through the Maintenance Plan options available.
But let’s say that you are not the creator of the maintenance plan and you have just recently joined the DBA team and have to continue with their plan.
And let’s assume that their plan involves either running a Windows batch file (.bat) or a custom-written SQL script.
You’ve seen that SqlBak simplifies most tasks and you still want to have the ability to stick to the maintenance plan that is in place, but don’t want to give up simplicity.
Well, we have great news! SqlBak gives you the chance to run either custom Windows batch scripts
or even custom-written SQL scripts
SqlBak offers flexibility in terms of options in order to cope even with the more complex maintenance plans.
You can run your custom Windows batch scripts and your SQL scripts before and after the backup process have finished and also after different types of backup operations have been completed.