Note: There are multiple reason of above error and this blog shows just one of them. I am sure that this blog would give you guideline about what do to in case you see this error about install error.
[Note from Pinal]: This is a 133rd episode of Notes from the Field series. I know Mike for many years and Mike has always inspired me with his positive energy. I have always enjoyed spending time with him as I have always learned something new but along with it, I have also improved as a human. It is very critical that we often meet someone who is not only technically brilliant but gives us a different viewpoint of life. I really respect Mike and enjoy love talking to him. Today is going to a fun note from Mike about Free DBA Tools.
This is one of the most interesting stories written by my friend Syrovatchenko Sergey. He is an expert on SQL Server and works at Devart. Just like me he also shares his passion for Wait Stats and new features of the SQL Server. In this blog post he talks about one of the most interesting feature about Delayed Durability. I strongly encourage that you find sometime during your day to read this blog post and discover more about this topic.
If database changes are needed to be made at a column level, it’s essential that you perform impact assessment in order to determine which objects will be affected after the change. This means that SQL table column dependencies within a database need to be analyzed.
ApexSQL Clean is a tool that is used to analyze SQL server database dependencies and also to remove unwanted objects.
To analyze table column dependencies within a SQL database the first thing you need to do is to create a new project. That can be done by clicking the New button in the Home tab and choosing the desired server and the database.
I had recently received an email about InMemory OLTP Functionality in Email when I was having a vacation with my family in the Australia. Let us read the story about my vacation and SQL Server in this blog post.
It is surprising to see that lots of people do not know that SQL Server Fill Factor 0 (which is the default value when SQL Server is installed) is equal to value as 100.
I have seen a number of customers manage their SQL Server environments in an adhoc manner. These accidental DBA’s need to know what happened in the system in a chronological order or even worst need to know what led to the lead up to a particular problem. Many times when we troubleshoot a problem with high CPU, its asked that when it all started and do we have any historical data of CPU usage? Here is the one query which I have re-written to have more details. Let us see Query to Get CPU Usage History for SQL Server and Operating System.