One should be very careful while working with system objects in SQL Server. Below is one of the situation where some permissions were given on system objects which was causing SQL startup failure. I have written various blog on script upgrade mode of SQL Server.
SQL SERVER – FIX : Msg 35295, Level 16 – Log Backup For Database ‘DBName’ on a Secondary Replica Failed
Once, while doing a load testing with my client, I was shown below error while taking log backups on secondary replica.
Msg 35295, Level 16, State 1, Line 1
Log backup for database “MyAppDB” on a secondary replica failed because the last backup LSN (0x0016ff11:00032258:0001) from the primary database is greater than the current local redo LSN (0x0016ffec:0006ee28:0001). No log records need to be backed up at this time. Retry the log-backup operation later.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
SQL SERVER – Queries are in KILLED/ROLLBACK State with Wait PREEMPTIVE_OLEDB_RELEASE
There are many wait types in SQL Server and not all of them are documented. Long ago I wrote blog on PREEMPTIVE and Non-PREEMPTIVE waits. SQL SERVER – PREEMPTIVE and Non-PREEMPTIVE – Wait Type – Day 19 of 28. In this blog post we will take a look at how to solve wait PREEMPTIVE_OLEDB_RELEASE.
SQL SERVER – Installation Error – The Specified Driver is Invalid
In this blog post we are going to learn about Installation Error – The Specified Driver is Invalid.
SQL SERVER – How to Apply Patch in AlwaysOn Availability Group Configuration?
This is one of the common question which is asked via emails to me. “How to apply the patch in AlwaysOn Availability Group configuration?” OR “What are the steps we should do and things to take care while patching availability replica?”