↓ Skip to Main Content
Vedran Kesegic Blog

Vedran Kesegic Blog

Main Navigation

  • Home
  • sp_xdetails
  • Performance Logging

Category: Data Engine

READ COMMITTED sucks!

By Vedran Posted on 2013-09-25 Posted in Data Engine, TSQL and SQL Client Code 3 Comments

Are you still using READ COMMITTED transaction isolation level? Default transaction isolation level on all SQL Server versions (2000-2014) has serious inconsistency problems, by design. Not many people are familiar how and why is it happening. I am writing this …

READ COMMITTED sucks! Read more »

Posts pagination

Previous 1 2

Our Mission

Our Mission

Databases should be fast and simple to use. We make them so. Do not let your customers wait for a slow database response - hire a top professional! We are passionate about creating highly-tuned SQL Server systems. Do you want yours to become one? Simply call us or send email, and we will take care of the rest.

Vedran Kesegić, M.Sc.
SQL Server Database Consultant
Email: [email protected]

A Random Thought

Keep your transaction log backups at least to second full backup. Even if the latest full backup is corrupt, you can recover without any data loss. E.g. if you take full backup weekly, diff backup daily, and transaction log backup hourly, keep your transaction log backup at least for 2 weeks, so it reaches the second full backup.

Categories

  • Backup and Recovery
    • Transaction Log
  • BI
  • Conferences
  • Data Engine
  • Performance
  • Security and encryption
  • Storage
  • TSQL and SQL Client Code
  • Uncategorized

Recent posts

  • Database recovery IMPORTANT rule
  • SUSPECT database
  • How to partition a really big table?
  • How to pass arrays to SQL? TVP – The Ultimate Guide
  • SQL for beginners
Copyright © 2025 Vedran Kesegic Blog | Powered by Responsive Theme
Visit Us On TwitterVisit Us On FacebookCheck Our FeedVisit Us On LinkedinVisit Us On Youtube