Part 1: How to solve the transactional issues of isolation levels
Transaction Isolation levels are described in terms of which concurrency side-effects, such as dirty reads or phantom reads, are allowed.
2013-05-01
10,035 reads
at yazdani
Re-compilation and Its effects on Performance
How recompilation does significantly affect on the execution time of SQL query and plummet or degrade the performance?
2012-06-07
10,896 reads
Blogs
The Book of Redgate: Do Your Best Work
By Steve Jones
One of our mission statements in the Book of Redgate says: attempt to do...
A Conversation That Refused to End: What We Learned from Our First Event in Zurich
On May 8, 2025, we hosted our first official event in Switzerland at Prime...
A DevOps Workshop Tomorrow in Atlanta
By Steve Jones
Tomorrow is the Redgate DevOps Day in Atlanta. You can still sign up, so...
Forums
CAST(VARCHAR(n)) resolved performance issue?
Hi, I would love to hear if anyone can tell me why a CAST...
isnull, coalesce overhead
hi, one of our sister division's erp extract view is going thru at least...
is there an elegant way for agent notification to show failure if any step fails
hi our corp dw load sqlagent job goes to the next step on the...
Question of the Day
The Internals of Writing a Page
In SQL Server, when the buffer manager write pages to disk, page protection is added to the pages. There are two types of protection: torn page protection and checksum page protection. What happens with regards to concurrency with page protection during writes?
See possible answers