In my last post of this series, I shared the most popular SQL Server How-to posts from the Datavail blog. You gained a few extra skills, picked up a few tricks, and hopefully learned how to be more efficient at work.
Now let’s talk about troubleshooting in SQL Server. As a DBA, you spend much of your work life troubleshooting database issues – perhaps more time than you’d care to admit. Between issues with missing indexes, workload distribution, blocking, and replication issues you’ve got a laundry list of problems you’re constantly on the hook to solve.
Luckily, we’ve got a number of blog posts that review these exact challenges and provide advice, tricks, and even scripts to help you solve them. Read on to get our Top 9 Datavail blog posts on troubleshooting in SQL Server.
Solving SQL Server Issues: The Easy Pickings
In our experience, there’s a great deal of low-hanging fruit when it comes to figuring out what’s wrong with SQL Server Performance. We call these issues Easy Pickings because they’re easy to find and easy to fix. Let’s pick some of that fruit!
Solving SQL Server Issues: The Best Bang for the Buck
Some SQL Server configurations have measurable effects on performance. The adjustments we’ll review in this blog post result in a significant return on investment, providing stability and performance through simple tuning, and giving you the Best Bang for the Buck.
Solving SQL Server Issues: The Long Road – Datavail
You can easily resolve some issues related to SQL Server performance, but there are others that require more time and resources. There are four issues under this umbrella: file locations, virtual log files, tempdb files, and missing index DMVs.
Performance troubleshooting with SQL Server 2016 Live Query Statistics
Along with many new features in SQL Server 2016, one of the developer and DBA friendly features is Live Query Statistics. If you are a DBA or developer, there are situations where a query takes a long time to execute and the “actual” query plan can only be seen once execution is completed. There are multiple ways to approach this issue.
Finding non-default configuration settings in SQL Server
Checking non-default settings for the database is simple in Oracle, but not so easy in SQL Server. Here’s a good solution that hard codes known default values into a script that works for SQL Server 2008 and up.
Five Quick Fixes for Database Reporting Slowdowns
Databases are the cornerstone of any business, storing every important detail that keeps them operating. They behave as living things, growing in a way that seems very organic. And like living things, databases require maintenance and care in order to remain effective and functional..
3 Common Log Shipping Failure Errors a DBA Can Fix
Log shipping is a very old technology solution provided by the SQL Server product. Here are some potential errors you could receive, their explanations, and some suggested solutions.
Investigating Missing Indexes to Yield Improvements
If you’re trying to troubleshoot or take on some performance tuning for your SQL server database, one of the issues may result from missing indexes. So why not insure your database is fully indexed from the outset?
The “ORA-12154: TNS:could not resolve the connect identifier specified” Oracle error is a commonly seen message for database administrators.
Learn how to fix common Log Shipping Failure errors in SQL Server. Includes step-by-step instructions, screenshots, and software script.