Validating your server setup is an integral component of your duties as a SQL Server DBA. When performing those validations, it is possible to run into an intriguing difference in reported port values.
The trick here is to find a way to search thousands of files quickly and filter easily the bad from the good. Sounds like an opportunity for an automation or script.
One tries to climb the ladder of success but at the cost of being an approachable human being. Nice people don’t need to finish last.
In this article, I share one easy script that could help eliminate one database feature as a culprit to an anomalous data masking suddenly getting enabled.
When looking for an easy method to audit Index changes, one of the first technologies to try really should be Extended Events (xevents).
This article shows a method to audit for index changes. The weak link in a solution such as this really boils down to the requirement that the solution needs to be in place before the index change occurs.
This article shows a quick script to help determine indexes that were created recently. This script will help you out of rough spot and help reduce the chance of rework.
This article takes a look at an error that may occur depending on your use of linked servers and the use of openrowset.
So you come along one day to validate some service configurations for the SQL Server services and instead of the SQL Server Configuration Manager opening as expected, you are greeted with the following error message.
Cannot connect to WMI provider. You do not have permission or the server is unreachable.
Explore how to avoid unwanted results that oft occur due to lack of attention to detail, use of internet examples, misunderstanding of the requirements; and always from granting way too much access.