The struggle to renormalize data
You are given an export of a NoSQL database, in JSON, and asked to import it into a relational database. Sounds easy? It isn't and Phil Factor explain why.
What Mail Items Have Been Sent With Database Mail
Have you ever wondered how much database mail you have sent in the past day or week? What about those database mail items that were not successfully sent. In this tip, Greg Larsen shows you how to review the database mail items that have been processed by SQL Server.
The Control Poll
Do you use version control for your databases? For your application code? Is there a time when you think it's not needed? Steve Jones asks the question today.
Creatures of habit, snowflakes, and integration tax
Why are practices like version control, continuous integration and automated deployment being introduced to application development but left on the shelf when it comes to the database? In search...
Setup and Implement SQL Server 2016 Always On Distributed Availability Groups
SQL Server 2016 introduced a new feature called Distributed Availability Group. A Distributed Availability Group is a special type of Availability Group that spans two separate Availability Groups. Edwin Sarmiento explains.
The Shortcomings of Predictive Accuracy
In prediction, accuracy is key. But it's not all it's cracked up to be as we will explore.
Using Tools that Fit
Equipment can matter for IT professionals. Read a few thoughts from Andy Warren.
SQL Graph Objects in SQL Server 2017: the Good and the Bad
Graph databases are useful for certain types of database tasks that involve representing and traversing complex relationships between entities. These can be difficult to do in relational databases and even trickier to report on. Until now, we have had the choice of doing it awkwardly in SQL Server or having an ancillary database to tackle this type of task. SQL Server 2017 will be bringing graph capabilities to the product but will these features prove to be good enough to allow us to dispense with specialised Graph databases? Dennes Torres decided to find out.
Why don’t you unit test SQL Server code?
This post will show the benefits of test-driven development and including automated SQL Server unit testing within your release pipeline. Even if you have a large code base and no existing unit tests, you can start introducing tests now to make your database code more robust to change.
Blogs
How to Find Expensive Queries in Amazon Redshift
Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...
The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech
By gbargsley
If you've been here before, you know this blog is usually about SQL Server,...
Designing a Storage Load Test for SQL Server
I’ve been doing storage load tests for SQL Server for a long time, both...
Forums
How Long is a Long I/O?
Comments posted to this topic are about the item How Long is a Long...
T-SQL Trigonometric Functions in SQL Server
Comments posted to this topic are about the item T-SQL Trigonometric Functions in SQL...
Half of All Engineers
Comments posted to this topic are about the item Half of All Engineers
Question of the Day
How Long is a Long I/O?
In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?
See possible answers