The adoption of Continuous Delivery often leads to the discovery of suboptimal practices within an organisation, and the Release Testing antipattern is a common example. Steve Smith explores the questions: what is Release Testing, and why is it an example of Risk Management Theatre?
SQL Saturday is a full-day technical conference and training event with international speakers. With over 20 sessions on SQL Server and a separate pre-con, the event is aimed at all those interested in SQL Server - from pros to beginners. This event will be on February 28, 2015, so register while space is available.
This article is about how a view works when it is created on a table with clustered columnstore index on it.
Today we have a guest editorial from Andy Warren with a few hints on how you can continue to be proactive as a DBA.
After discussion the main concepts and basic API calls for Azure Storage Queues in parts 1 and 2 of this series, Roman Schacherl turns his focus to two topics that no one likes to implement but everybody needs: security and performance.
A fundamental way that SQL Server determines whether a principal has the permissions necessary to execute code is with its execution context rules. It’s all complicated by the possibility that a principal has permission to execute code but doesn’t have permission on the underlying objects accessed by the code, such as the data in a table. This stairway level will explore SQL Server’s execution context, ownership chains, and impersonation, as well as show you how you can control access to data via T-SQL code.
SQL Server Data Collector, together with Management Data Warehouse, is a fine and useful component for gathering information centrally about how SQL Server instances are being used, and thereby keeping an eye out for problems. It comes into its own when you have figured out how to configure it to run on maybe hundreds of instances using Central Management Server. Dennes describes how to tame the system so that it scales.
This metric can help if you want to monitor the number of indexes per database that haven't been used for the last month. Indexes that aren't in use should be removed because they can degrade INSERT, UPDATE and DELETE performance, and they use storage space.
As data professional I have played with Analytics and found I'm better suited to development and administration, and that's ok.
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
When mirroring was first released for Azure SQL Database, it used Change Data Capture...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
Comments posted to this topic are about the item Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers