One of the most important features of the SQL Server 2016's new Query Store is the reporting. With these features, it is now possible to get a wealth of information on how your query workload is performing, either aggregated for the entire query workload or for a single query. With this information, you can see the effects of 'forcing' an execution plan for specific queries and get feedback of the consequences.
Learn about some Visual Studio features that help with automation, and use them to create an Asymmetric Key and Login.
Siddharth Mehta walks through how to automatically migrate reports from MS Access to SQL Server Reporting Services (SSRS) without having to rebuild anything from scratch.
Microsoft has changed their engineering to do amazing things in the cloud, especially with SQL Server. We could all learn from this.
Greg Larson looks at how to hide the value of sensitive data by applying Dynamic Data Masking.
In this new chapter we will show how to verify the accuracy of the mining models.
IDEs are wonderful, but tend to lull you out of the good habits of thinking up front about how the code you write will be monitored and tested. So argues Phil Factor.
How we implement algorithms can change the way the world works with our software. Steve Jones wonders if we should be disclosing the algorithms themselves.
Redgate is in an early research phase of a tool that helps provision production-like databases for dev and test in a way that saves both time and storage. The team involved are looking for volunteers to provide feedback on the product as it's developed. If you think you'd be interested in trying out the tool, sign up for the beta program now.
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers