I often get emails from my blog readers asking various types of clarifications about my own blog. Here is one of the interesting questions from a reader about message Cannot shrink file in the database to xxxx pages as it only contains yyyy pages which he encountered after following my below blog.
SQL SERVER – Error 21028 : Replication Components are not Installed on This Server
One of my clients, for whom I installed SQL Server and configured AlwaysOn came back to me with an error message. While trying to configure replication they were getting an error message. In this blog, we would learn how to fix error “Microsoft SQL Server Management Studio is unable to access replication components because replication is not installed on this instance of SQL Server”
How to Create an Empty Table and Fool Optimizer to Believe It Contains Data? – Interview Question of the Week #204
Question: How to Create an Empty Table and Fool Optimizer to Believe It Contains Data?
Answer: Before I answer this question, I must acknowledge that I have never heard this question in my 20 years career before and I must ask you back, where do you come up with these kinds of questions.
SQL SERVER – FIX: Msg 15190 – There are still remote logins or linked logins for the server
One of the most successful offerings from me has been Comprehensive Database Performance Health Check. Sometimes during my assistance, some random issues appear which I try to solve as well. In a recent engagement, one of their developers asked a question about an error which he was receiving while running sp_dropserver. In this blog, we would see how to fix error 15190 – There are still remote logins or linked logins for the server.
SQL SERVER – Fix : Error Msg 1813, Level 16, State 2, Line 1 Could not open new database databasename. CREATE DATABASE is aborted
It is indeed a pleasure when we write a timeless article for SQL Server and DBAs read it after many years. In the year 2007, I wrote an article about an error related to Could not open a new database. It has been one of the top viewed blog posts all the time. Recently SQL Server Expert Jeremy Roe has sent me an updated script for a recent version of SQL Server for the same error.
SQL SERVER – Error: Parameter ‘ProbePort’ does not exist on the cluster object. Unable to set Probe Port for Azure Load Balancer
Azure is gaining popularity and I am getting clients who want to create Always On availability group as their high availability solution in Azure Virtual machine. To keep myself up to date, I also try creating the customer’s scenario in my lab. In this blog, we would how to fix error Parameter ‘ProbePort’ does not exist on the cluster object while configuring probe port.
Detect and Diagnose SQL Server Performance Issues with Spotlight Cloud
The number one challenge for any DBA with their SQL Server is the performance. Every user wants their applications to run faster. When DBAs and Developers start building an application, it usually runs faster as there is no real workload running over it. Often DBAs and Developers do stress testing with the third party tools or by simulating the workload. However, honestly, when an application goes live, the entire scenario is very much different. It is near impossible to predict the usage pattern and workload distribution in any application once it starts to grow. Today we will discuss how we can detect and diagnose SQL Server Performance Issues with Spotlight Cloud.
Is your SQL Server running slow and you want to speed it up without sharing server credentials? In my Comprehensive Database Performance Health Check, we can work together remotely and resolve your biggest performance troublemakers in less than 4 hours.
Once you learn my business secrets, you will fix the majority of problems in the future.
Have you ever opened any PowerPoint deck when you face SQL Server Performance Tuning emergencies? SQL Server Performance Tuning Practical Workshop is my MOST popular training with no PowerPoint presentations and 100% practical demonstrations.
Essentially I share my business secrets to optimize SQL Server performance.