In this post we will add some simple error handling in PowerShell to complete the Backup and Restore SSAS database script. In previous posts we looked into Backing up SSAS database with PowerShell and Restoring the SSAS database with PowerShell.
A Backup of SSAS database needs a Restore SSAS to work as a completed unit and, as they say, “a backup is only as good as your last restore”. Backup SSAS database In my post Backup SSAS with PowerShell we created
To Backup SSAS databases, one of the easiest and simplest ways to is to use PowerShell. Versioning our backups Firstly we want to timestamp each backup so we can version our backups and make it easy, human readable form,
Using SSIS we had a Excel Source to import regularly into a database. We constructed a simple project in SSDT and it ran successfully. We then deployed the project, started an SQL Agent job step with a step as an SQL
Now we have our AlwaysOn solution and the same SQL Agent jobs running on each availability replica and they reference the availability group listener. So we’re all set up and running with our Availability solution but our SQL Agent jobs are unaware
To find out which SQL Agent job is running your SSRS schedule simply use the query below substituting your ReportServer name and your ReportName. Many reports can run using the same shared schedule so use caution if running the job