Midnight at 1 AM, I received a call from my customer where I have earlier worked on performance tuning project. As soon as I picked up the phone call the first statement from my friend was about TempDB and it was as follows:
“We should have followed your advice, the TempDB is full, now help us fix it.”
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:
It is about a few weeks back that I wrote about how InMemory OLTP Hash Collisions can happen and how it can affect performance. Here is a recap of that post for your reference and do check the same before proceeding reading this blog post.
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.
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.
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.
The other day, I received an email from a user, who had dropped master database in their system. I told him directly that he should have not dropped master database as that is a very important system database. It is really strange that after so many years quite a few of the people do not know what is a master database in SQL Server.