Monitoring should be able to happen no matter where you are located. This year organizations around the globe had to adapt to many new challenges including a distributed workforce and managing their estate when they can’t be in the office. This blog outlines the reasons and benefits of adopting remote monitoring.
In Part 1 of this article we looked at a specific use case (probably exaggerated) that gave us an idea about how CPU and IO performance might be affected by a bad page split. We continue this analysis looking at what really happens to the data on the leaf pages of a clustered index with […]
SQL Monitor 10.1 now gives you a comprehensive overview of your SQL Server licensing, so you know which licenses are in use, and which versions are on which servers. This simplifies license auditing and lets you unearth misconfigurations that could potentially cost you money. The new version also integrates with Microsoft Teams and Splunk, and supports complex Active Directory environments.
Because of its many roles, tempdb is the source of performance issues in SQL Server, and there are recommended configuration changes to mitigate this. In this article, Fabiano Amorim demonstrates another issue with tempdb performance that you probably didn’t know about.
The results of a survey on software developers has some interesting insights.
Throughout this series, we’ve consistently dealt with delimited text files; comma and tab, for instance. We’ve used the U-SQL built-in extractors to process these files. But what if we need to deal with different types of file, like JSON, XML or fixed width? That’s where custom extractors come in. U-SQL provides us with the ability […]
Data breaches are becoming too common place with some accounts reporting more than 1000 breaches per year with close to 50 million records exposed yearly in the financial, business, education, government and healthcare industries. Learn about how DbDefence performs SQL Server Data Masking as a portion of a three pronged approach to protect your data.
It is widely acknowledged within the SQL Server community that baselines represent valuable information that DBAs should capture. Unfortunately, very few companies manage to log and report on this information, and DBAs are then forced to troubleshoot from the hip and scramble to find evidence to prove that the database is not the problem. This article will make a compelling argument for why DBAs must start capturing baseline information, and will create a roadmap for subsequent posts.
If you have not been capturing baselines on your production servers, then today is the day you can start. This article provides scripts, valid for SQL Server 2005 and higher, which anyone can use to capture basic information about a SQL Server instance.
By Steve Jones
on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...
By DataOnWheels
I have been active in the data community throughout my career. I have met...
By Vinay Thakur
Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
hi, in an ssis for each loop over an object variable called MyListVariable, i...
SQL Server is typically viewed as a transactional or analytical database engine. However, it...
On SQL Server 2025, when I run this, what is returned?
SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL') See possible answers