If you are looking for some of the most common SQL Server issues and our solutions for them, the team at WARDY IT Solutions have curated those articles here.
Here are some of the most popular articles we have published addressing common SQL Server problems. From performance problems to updates and end of life considerations, we have covered it all:
1. 5 most common causes of SQL Server performance problems
We asked our Data Platform consultants to share their opinions on the most common causes of performance problems and of course, how to avoid them. Start by checking your wait stats. This isn’t the cause, but a good place to start. SQL Server continuously tracks why execution threads have to wait. This information is vital when you’re trying to pinpoint the root cause of your performance problems.
The good news is finding the cause of your performance problem is easy, the bad news is interpreting the information and fixing the issue is often complicated and time-consuming but this will point you in the right direction. If your environment is anything like most, the chances are wait stats will point you in one of these five directions:
READ BLOG POST
2. Remove Non-Printable Characters from a String
We often provide script instructions demonstrating how to resolve common issues with SQL. The SQL Script in this blog post can be used to remove non-printable characters from a string such as CRLF etc. Originally published in 2005, this resource is still relevant and sought after by people using SQL for their business:
READ BLOG POST
3. Understanding Virtual Log Files (VLFs)
Unmanaged Virtual Log Files (VLF) are one of the most frequent issues found in client environments. Since there are a lot of misconceptions on this topic, in this post we hope to explain what VLFs are, why they get created, simulate a VLF count growth, demonstrate how we can monitor it and more importantly, fix it.
For the sake of practicality and readability, we have attempted to make this complex SQL engine internal mechanism as simple and straight-forward as possible.
Every time a log file grows, new VLFs are created, therefore the log file autogrowth setting, and how busy your database is will dictate the growth rate of active VLFs in your log file.
When investigating the reasons for high VLF counts, 9 out of 10 times it’s a combination of 2 factors outlined in our blog post:
READ BLOG POST
4. The ins and outs of SQL Server Stretch Database
“Cold Data” management is definitely not a new topic, but Stretch DB presents a solution to this problem with a higher level of simplicity and efficiency.
Normally you would have to do at least one (if not all) of the steps outlined in our blog to manage your organisation’s cold data growth.
With SQL 2016, Microsoft introduced Stretch Database which gives full flexibility to host data that meet specific criteria in Azure and keep it online and accessible without the need for code changes.
READ BLOG POST
5. SQL Server Health Check: How to Identify and Solve SQL Server Performance Issues
Here at WARDY IT Solutions we live and breathe SQL Server every single day.
With years of experience in the Microsoft Data Platform, we’ve found that performance issues in SQL Server typically manifest as a bottleneck in one of three broad areas:
- CPU
- I/O, and\or
- Memory.
A.k.a. the Performance Triangle.
Here are our top troubleshooting tips to release your bottleneck and give your server the SQL Healthcheck it needs.
The first step in resolving any SQL Server performance issue is to pin-point exactly where in the Performance Triangle the problem is coming from. When we’re performing a SQL Server Healthcheck for our customers we always start with Wait Statistics.
READ BLOG POST
6. SQL Server Security Auditing: Checking Who Has Access to What
IT professionals are typically in agreement when it comes to the need to secure systems to ensure data is not accessed by those who are not authorised. The security of a SQL Server is usually implemented during the initial setup and deployment to adhere to company policy, and more often than not, left as is and unreviewed.
Recurring periodic security audits for SQL Server environments should be adopted as changes to access rights and permissions can occur frequently. For example, a contractor may have required access for a project. After the contractor leaves it is easy to forget about removing their access and so their account may still exist, potentially giving them full admin rights to your SQL Server.
Likewise, when people leave an organisation it is common that their accounts are disabled or removed but their login details may still exist on the SQL Server and they may still own objects in SQL Server databases that they created or altered (e.g. SQL jobs, tables or even databases). You’ll need to follow the necessary steps outlined in our blog post:
READ BLOG POST
7. The remote name could not be resolved (Microsoft.SqlServer.Management.UI.RSClient)
This popular blog post from 2006 still receives a lot of traffic year after year because it answers a common user experience that a lot of SQL users are searching for online.
When connecting to Reporting Services through SQL Server Management Studio (SSMS) you may receive the error:
The remote name could not be resolved: xxx (Microsoft.SqlServer.Management.UI.RSClient).
This error may be caused as a result of modifying the machine name.
READ BLOG POST
8. Encrypting SQL Server in Azure
Securing your SQL Servers has never been more important when looking at hosting your databases in the cloud. No longer is your data sitting safely on a server in the company’s data centre – now it is in the cloud, on the internet and more open and vulnerable than ever before.
Of course, we can and should implement constructs like firewalls, network security groups, access control lists, multi-factor authentication, Active Directory integration and good old password security. But what about protecting the actual SQL Server database?
READ BLOG POST
9. SQL Server End of Life Considerations
SQL Server End of Life (EOL) indicates that a particular version is at the end of its useful life, and Microsoft stops selling and developing it.
While the Microsoft Lifecycle Policy offers 10 years of support (5 years for Mainstream Support and 5 years for Extended Support) for SQL Server, once the Extended Support ends, there will be no support or security updates available to you.
In the Microsoft world, SQL Server End of Support (EOS) means you will no longer be able to contact Microsoft for product or troubleshooting help, and there will be no more patches or security updates to that particular SQL Server version.
If you no longer receive security updates, your system defences are down. By continuing to use an out of support version, this makes your system vulnerable to threats. You may find it nearly impossible to protect your data against cyberattacks.
READ BLOG POST
We hope you find these resources helpful. If you are still encountering issues with SQL Server, consider carrying out a SQL Server licensing review? Here’s how.
Contact WARDY IT Solutions to find out how you can ensure your SQL licensing is up to scratch and working as efficiently as it could for your business.
