More and more data is being captured and analyzed all the time. At the same time, there are varying expectations of privacy that aren't always shared between the subjects of data and the collectors. Steve has a few thoughts on how this will play out for data professionals.
This week, Brent is demoing SQL Server 2019 features that he's really excited about, and they all center around a theme we all know and love: parameter sniffing.
Louis Davidson reveals some useful Prompt features for refactoring individual code blocks or modules during development, which will improve code quality, reduce tedium, make testing simpler, or sometimes all three.
Kathi Kellenberger introduces the new Estate monitoring pages in SQL Monitor 9, and explains how they will help DBAs monitor and safeguard the security, stability and availability of all servers in their care.
Steve is putting on a new contest for you with some fun prizes. Put on your creative hat and submit an entry. Contest ends April 21, 2019.
Last year I started to get alerts from Microsoft Repos that someone had put a piece of security information in their code that pertained to one of my Azure services. At first I was worried, but then I realized this was the public version of AdventureWorks we maintain in Azure. We've published the login so […]
Kendra Little shows how to get the WideWorldImporters database into version control, using SQL Source Control, and then set up an automated database build process, using Azure DevOps with SQL Change Automation.
Template-based provisioning simplifies deployment and promotes principles of DevOps and Infrastructure as Code, making it the recommended method for implementing cloud-based services. However, its benefits extend beyond initial implementation, since you can apply it to configuring and maintaining existing Azure SQL Database instances. In this article, you explore an example of this approach.
A monitoring tool must provide us with an understanding of the often-complex performance patterns that databases exhibit when under load, so that we can predict how they will cope with expansion or increase in scale. It must also helps us spot the symptoms of stress and act before they become problems that affect the service, and understand better what was happening within a database when an intermittent problem started.
Most of us work with the time in a variety of ways in our applications. Temporal tables use the time on the server,but Steve notes today that we might want to capture other types of time.
By gbargsley
It's 2 AM. Your phone is going off. Users can't connect to the application,...
By Steve Jones
I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...
By Arun Sirpal
After a year away getting to grips with AI and its application across the...
Comments posted to this topic are about the item Local Agents
Comments posted to this topic are about the item Detecting Deadlocks
Comments posted to this topic are about the item Introducing the Relational Embedding Retrieval...
By default, how often is the SQL Server Database Engine checking for deadlocks?
See possible answers