Backup to URL worked, but a maintenance plan failed with Msg 3225: WITH CREDENTIAL is not valid for credentials with a Shared Access Signature. Here is the fix.
SQL SERVER – Always On Availability Group Error 35250: The Connection to the Primary Replica is Not Active
Joining a database to an availability group can fail with Availability Group Error 35250. Here is why it shows up in the wizard and how I fix it.
SQL SERVER – Fix the Error – Accessing this Server via SQL Management Objects (SMO) or Distributed Management Objects is Currently Not Permitted
After applying STIG to SQL Server 2016, SSMS said accessing this server via SQL Management Objects (SMO) is not permitted. Here is the cause and the fix.
SQL SERVER – Unable to Launch SSMS Error – Cannot Find One or More Components. Please Reinstall the Application
I had SSMS 17.1 installed on the machine and it was working fine. I don’t remember what I installed, but I started facing an SSMS error.
SQL SERVER – Msg 3743: The Database is Enabled for Database Mirroring. Database Mirroring Must be Removed Before you Drop the Database
Msg 3743 says the database is enabled for database mirroring, and mirroring must be removed before you drop it. Here is how my client got past it.
SQL SERVER – Backup to URL error: Operating system error 50(The request is not supported.)
Backing up a database to Azure gave me a backup to URL error: Operating system error 50, the request is not supported. Here is the cause and the fix.
SQL SERVER – Execution Failed. See the Maintenance Plan and SQL Server Agent Job History Logs for Details
My client ran a new Maintenance plan for full and log backups and it failed at once. The reason was two subplans in one plan. Here is how to run them.