“Copy-On-Write” (COW) is a resource management technique used in computer programming and operating systems. Its application in SQL Server, particularly in relation to snapshot technologies, is a fundamental concept behind the functioning of database snapshots and certain types of backups. Let’s delve into the detailed workings of Copy-On-Write in the context of SQL Server:
Category: Storage Engine
Speed, Efficiency, and VLDB Backups: Making the Right Moves
Today we will discuss VLDB backups. Handling VLDBs can be challenging for many administrators. Sometimes just completing a full backup in a reasonable amount of time is challenging, not to mention restoring a database to meet your organization’s service level agreements (SLA). There are many options to consider. Some options exist outside of the BACKUP DATABASE statement. They key to improving database backups is to adjust various configurations to increase throughput, increase concurrency, and reduce the amount of data to backup.
Implementing Row-Level Security in SQL Server
Row-level security (RLS) in SQL Server is a feature that allows database administrators to control access to rows in a database table based on the characteristics of the users accessing them. This can be particularly important in environments where data privacy and security are critical. In this blog post, we’ll explore how to implement RLS in SQL Server.
DBA to the Rescue: Mitigating the Impact of SQL Server Corruption
Let’s talk about the boogeyman of our database world – corruption. Not the kind that lands you in headlines, but the sort that can turn a perfectly tuned database into a digital wasteland overnight. It lurks in the shadow of failing hardware, creeps behind the veil of sudden power losses, and sometimes piggybacks on the most innocent-looking software bugs.
SQL Server Transaction Logs: Ensuring Consistency and Recovery
The SQL Server Transaction Log isn’t just a record of database changes; it’s the heart of SQL Server’s ability to recover from unexpected issues and failures. Each entry in the log is a testament to SQL Server’s commitment to data consistency, durability, and atomicity. This means that every action you take is not only recorded but is also designed to be reversible, allowing the system to maintain its state even under unforeseen circumstances.