They noticed that application jobs are failing with the below error message about running a new system task. Let us learn more about this.
SQL SERVER – Msg 32055 – sp_refresh_log_shipping_monitor – There Was an Error Configuring the Remote Monitor Server
Since I started consulting, I never had “Monday Blues” because I don’t get any weekends. I am always ready to help without time boundaries. Consulting gives me exposure to the real customer issue, learn more and blog more. This also helps me to see what customers are implementing rather than what Microsoft has provided as features. This blog is an outcome of a consulting where everything was deployed successfully, but project sign-off was pending due to an issue with log-shipping monitoring. In this blog we would learn about fixing error There was an error configuring the remote monitor server.
SQL SERVER – Fix: Error – VS Shell Installation Has Failed with Exit Code 1638
Recently I got called in by a regular customer for my On Demand (50 minutes) service. Every single day I keep two hours available to help DBAs who need urgent help with SQL Server. When I connected with a customer, I was expecting to solve their SQL Server performance tuning problem. However, I quickly realized that the issue was not SQL Server Performance but was rather with SQL Server 2017 installation. Let us see how we can fix the error users are receiving related to VS Shell.
SQL SERVER – Too many dumps generated. CPerIndexMetaQS::ErrorAbort – Index Corruption
I always try to share my knowledge and learning from a client engagement. This helps me in remembering the steps I took to reach to the solution. It also helps my blog readers to follow the same steps and fix their problem rather than waiting for some expert to fix it. So you see, this is a WIN-WIN situation for both of us. Let us learn in this blog post how to fix index corruption.
SQL SERVER – Fix Error – Restore Operation Failed for Database Due to Insufficient Memory in the Resource Pool ‘Default’
SQL SERVER – Fix Error – Restore Operation Failed for Database Due to Insufficient Memory in the Resource Pool ‘Default’
SQL SERVER – Login Failed. The Login is From an Untrusted Domain and Cannot be Used with Windows Authentication
Many people ask me how is the life as a freelancer, as a consultant? My answer is “life is good, but to get the complete picture, you have to experience it”. There are enough challenges which are thrown at a consultant everyday and resolving them at a rapid pace is the key. Every day is like a closed door where I can’t see what’s going to happen. But trust me… it’s FUN! This blog is an outcome of such “challenge” which was thrown while performing final checks after deployment for a client. We ran into an issue where the SQL cluster was not able to failover to another node. Let us learn about how to fix the error login failed.
SQL SERVER – Always On Availability Group Failover Generating Dump. Error: 17066: SQL Server Assertion: HadrFstrVnnUtils.cpp:479
One of my clients was using Always On availability group. They were having 3 nodes Always On AG setup. For simplicity, let’s call them Node1, Node2 and Node3. The first two nodes were in one subnet and node3 was in separate subnet. Let us learn about availability group failover.