Every now and then, experienced SQL Server DBAs as well as the SQL Server rookies find themselves in the unpleasant situation when some important data has been changed or lost with the monumental task to solve this in the most efficient way. Regardless of the change source – was it an internal or external user, the intent behind it – unintended mistake or a malicious change, or even the exact nature of the change – update, delete, drop or something else, database administrators are faced with the task to recover the lost data and enable users to continue using the database as if the recovery was never required by providing the data recovery. Let us learn about how to recover lost data using the transaction log files.
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:
SQL SERVER – SQL Profiler vs Extended Events
To tell you the truth, I didn’t know how to start this article about SQL Profiler vs Extended Events. After all, I decided to take mind off things and to watch a movie. The movie was Iron Man 2. In addition to the brilliant performance of Robert Downie Jr., one phrase stuck in my mind and immediately inspired my writing.
“Don’t get so attached to things, learn to let go.”
~ Iron Man 2 (Robert Downie Jr)
What is better the old reliable SQL Profiler or something new? My personal choice is Extended Events. Why? To deal with Extended Events, we should go back to SQL Profiler and comprehend its work. First, a new trace is created, and information to be traced is noted.
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.
SQL SERVER – Event ID 7000 – The service did not start due to a logon failure
Many times I feel that I have so many blogs that I must have covered all common possible error related to usage of SQL Server. But there are few easy ones which I missed. And thanks to those who take time in sending them to me that it makes a great reminder to what I have missed till date. This blog is from one of such logon failure errors that came from a DBA from one of my consulting engagements. Since the error was simple enough, I thought to respond over mail to solve the problem.
SQL SERVER – Installation Error – The wrong diskette is in the drive. Insert (Volume Serial Number: ) into drive.
The world of working with errors always gets the better of me. It is a wonderful way to understand why SQL Server behaves in a certain way and most importantly, it helps me solve some of the problems people face on a day-to-day basis. As you might know that along with performance consultancy, I also reply to any personal email asking for help. This blog is a result of one such interaction where the client was facing an error while installing Service Pack 4 for SQL Server 2008 in a clustered environment. Let us learn about Installation Error.