Received an email “Need your urgent help On Demand, our MSDB Database has grown too big and we need help to check our MSDB.” I have been an independent consultant for a while and one of the services I provide is “On Demand (50 minutes)” service. This service is very helpful for organizations who are in need immediate help with their performance tuning issue. Though, I have set working ours for my regular clients, every single day, I keep two hours available for this particular offering. This way, I can make sure that anyone who urgently needs my help, can avail the same. Click here to read more about it.
SQL SERVER – Msg 3168, Level 16 – The Backup of the System Database on the Device Cannot be Restored Because it was Created by a Different Version of the Server
In the recent past, I have written a blog about Ransomware. Here is the link. SQL SERVER – How to Protect Your Database from Ransomware?. In this blog post we are going to discuss about system database.
There are some weird situations which I see in SQL Server. This is also a one of the surprising situation. One of my client reported via below screen shot. Let us see the issue of Master Database in Single User Mode.
In the recent few days, I have found many clients having various script upgrade failures while applying service packs or cumulative updates. Here are few of them. Let us learn about Script Upgrade Failure.
SQL SERVER – FIX: Error: 913, Severity: 16 – Could Not Find Database ID 3. Database May Not be Activated Yet or May be in Transition – SQL Service
This blog is a result of a Skype conversation with one of my clients. The issue, for which they contacted me, was that they were not able to stat SQL Service due to database may not be activated.
SQL SERVER – Error 17113, Severity: 16 – Error Occurred While Opening File ‘master.mdf’ to Obtain Configuration Information at Startup
While playing with my SQL Server startup parameter, I made some mistakes and came to a situation where SQL Server was not getting started. In this blog post, let us learn about error 17113.
SQL SERVER – Script level upgrade for database master failed – Error: 4860, Severity: 16, State: 1 – Cannot bulk load. SqlTraceCollect.dtsx does not exist
Of late, I have been contacted by few clients who have been facing issues with SQL startup failure after applying patch to SQL Server instance. This blog is an outcome of one such assistance provided. Here is a blog post where I discuss script level upgrade for database master fails.