External Article

Close these Loopholes - Reproduce Database Errors

This is the final part of Alex's ground-breaking series on unit-testing Transact-SQL code. Here, he shows how you can test the way that your application handles database-related errors such as constraint-violations or deadlocks. With a properly-constructed test-harness you can ensure that the end-user need never see the apparent gobbledegook of database system error messages, and that they are properly and robustly handled by the application.

External Article

Security Overview for Database Administrators

SQL Server 2008 is secure by design, default, and deployment. Microsoft is committed to communicating information about threats, countermeasures, and security enhancements as necessary to keep your data as secure as possible. This paper covers some of the most important security features in SQL Server 2008. It tells you how, as an administrator, you can install SQL Server securely and keep it that way, even as applications and users make use of the data stored within.

Blogs

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

Read the latest Blogs

Forums

Increase Deadlock Detection

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Increase Deadlock Detection

A Tool is Better than a Script

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Tool is Better than...

Understanding Deadlock Victim Selection in SQL Server

By john.martin

Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers