Let me answer the first question first – There is no way to backup and restore SQL Server 2017 to SQL Server 2005 with the help of any tools. In this blog post, we will learn about how we can generate scripts to achieve this task.
SQL SERVER – Monitor Estimated Completion Times for Backup, Restore and DBCC Commands
Earlier this week, we were fortunate to receive an amazing script to overview HADR / AlwaysOn Local Replicate server from SQL Server Expert Dominic Wirth. You can read the amazing script here: Scripts to Overview HADR / AlwaysOn Local Replica Server. As a follow up to the previous conversation today I received another extremely helpful script from Dominic Wirth which I will be using with my customers every single day. In this blog post, we will see the script which will Monitor Estimated Completion Times for Backup, Restore and DBCC Commands.
SQL SERVER – Msg 3292: A Failure Occurred While Attempting to Execute Backup or Restore With a URL Device Specified
In my recent project with a customer, they wanted to configure SQL backups to Azure Blob Storage. When we were trying to take a backup, we were facing error. In this blog we would learn how to fix error message 3292 – A failure occurred while attempting to execute Backup or Restore with a URL device specified.
SQL SERVER – Backup to Microsoft Azure Tool – ERROR: Account Verification Failed
I have been seeing many customers moving their SQL Server to Cloud. Few of them have chosen Microsoft Azure platform to host their production server and few others have selected other cloud platforms like AWS. When they host SQL in Azure, they can choose various backup methods. In this blog, we would learn about fixing an interesting error “Account Verification Failed” while using Microsoft SQL Server Backup to Microsoft Azure Tool.
SQL SERVER – Restore Database Wizard in SSMS is Very Slow to Open
Recently I was hired for my On Demand (55 minutes) Service by an organization and they had a very interesting situation. To be very honest, I was initially lost for few moments when they described this situation to me and wanted me to solve their error. They were facing a very unique situation where their SSMS was working just fine but when they try to restore any database, SSMS Restore Database Wizard will take forever to open.
SQL SERVER – AlwaysOn Automatic Seeding Failure – Failure_code 15 and Failure_message: VDI Client Failed
Recently I wrote a blog explaining a situation where taking log backup can break automatic seeding and synchronization would not work. Below is the blog reference. SQL SERVER – AlwaysOn Automatic Seeding – Database Stuck in Restoring State
SQL SERVER – AlwaysOn Automatic Seeding – Database Stuck in Restoring State
As a part of my consulting, I observed that there is a lot of interest in using AlwaysOn availability group. I have deployed many AlwaysOn solutions from start-to-finish. Recently I encountered an issue and in this blog, we would discuss reason of an availability database to stay in restoring mode even after using automatic seeding.