When you are driving on a highway, you look forward to the sign boards give you guidance while you are busy driving. These sign boards tell you when your exit is approaching and how you should be dealing with the same. I consider such sign boards inside SQL Server as “Error Messages”. I rely on them so heavily to give me insider information to a possible solution. Not always are these messages super easy to understand. Take for instance the following message. While trying to create a database on my lab server, I got below error related to System.DBNull:
SQL SERVER – Script level upgrade for database master failed because upgrade step sqlagent100_msdb_upgrade.sql encountered error
Sometimes I feel that one error can be caused due to multiple reasons and there are different ways to solve it. I already have two blogs for the error message. As they say, there are is no silver bullet when it comes to solving some of the issues. SQL Server might through a generic message, but it all lead to the same problem related to master database:
SQL SERVER – Error Fix: Msg 13601 Working with JSON Structure
As you new versions of SQL Server come, the amount of capabilities just increases exponentially. It is tough to keep up in pace with the innovations and learning that one needs to go through. I have in the past written few articles around working with JSON over the blogs earlier. These games of playing with the new capabilities will show up tons of errors as we are not completely aware of what is possible. These experiments lead you from learning to another.
SQL SERVER – FCB::Open failed: Could not open file Path for file number 2. OS error: 5(Access is denied.)
I assume a number of times when the machine is booted up, I am most likely to hit the Management Studio to work on some script or the other. But sometimes strange things happen and I get all sorts of error. There might be tons of reasons why SQL Server is not able to start. This blog is a result of a quick consulting engagement with one of my clients where I faced OS error.
SQL SERVER – Fix Error – 948 A downgrade path is not supported. The database cannot be opened because it is version.
These past weeks the number of errors I have been getting when attaching a database has been far too many. But the best part of this learning experience is that I get to write about them one after another. There are no right or wrong answers sometimes, but am learning every time. Here is an error which is related to a downgrade path not supported. I received while I was trying to attach database using below command:
Pester the Tester: PowerShell Bugs, Beware! – Notes from the Field #129
[Note from Pinal]: In this episode of the Notes from the Field series database expert Robert Cain explains about Pester which is a bug testing framework for Powershell. I know Robert from last many years. Besides his amazing credentials of MVP, MCTS, Published Author and he is an amazing person to hang out with. I have seen him speaking at many prestigious events like PASS Summit, TechEd and every single time I learn something related to technology.
SQL SERVER – FIX – Linked Server Error 7416 – Access to the remote server is denied because no login-mapping exists
Last time I wrote a blog about linked server creation issue. As I said, these are one of the most common issues. But as soon as such blogs get released, I get a number of requests around them immediately. Here is the blog post which is discussing about the linked server error.