Discover how to configure Change Data Capture (CDC) in SQL Server to be High Availability (HADR) aware. This guide covers step-by-step instructions to ensure continuous data capture and system resilience across failovers, minimizing manual intervention and maximizing uptime.
Category: Data Integrity
Understanding the Implications of the TRUSTWORTHY Database Setting in SQL Server
As a SQL Server DBA, understanding the nuances of database settings is necessary for maintaining security and integrity. One such setting that often becomes a topic of discussion due to its significant impact on security is the TRUSTWORTHY database setting. The TRUSTWORTHY database setting in SQL Server is a configuration option that affects the security of certain database operations, particularly those involving code execution contexts. It plays a critical role in the security context of modules that use WITH EXECUTE AS, as well as CLR (Common Language Runtime) assemblies marked as EXTERNAL_ACCESS or UNSAFE.
Understanding the Intricacies of SQL Server Virtual Log Files
We as SQL Server DBAs often overlook the importance of the transaction log. It plays a pivotal role in ensuring data integrity and recoverability. To manage this effectively, SQL Server employs a system of segmentation known as Virtual Log Files, or VLFs. The intricacies of VLFs and their management are fundamental to the seamless performance of SQL Server databases.
The Power of Snapshots: Exploring Copy-On-Write in SQL Server
“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:
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.