Sample Chapters

External Article

Developing Modifications that Survive Concurrency

  • Article

You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex Kuznetsov explains why it happens, and how you can avoid such problems.

2010-07-09

3,657 reads

Blogs

Au Revoir for now

By

No, I’m not quitting or retiring. Just going on vacation, but I leave tonight...

Goodbye, Microsoft

By

A few years ago I took a new job at Microsoft, working as a...

The SUM of Nothing: #SQLNewBlogger

By

I caught this interesting item over on Pinal Dave’s blog: Eleven Interview Questions that...

Read the latest Blogs

Forums

Building a SQL Server Fleet Audit That Leadership Actually Reads

By Mayank Sethi

Comments posted to this topic are about the item Building a SQL Server Fleet...

Smart AI Agents and Data Security

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Smart AI Agents and Data...

RegEx Functions IV

By Steve Jones - SSC Editor

Comments posted to this topic are about the item RegEx Functions IV

Visit the forum

Question of the Day

RegEx Functions IV

I have this data in a table in a SQL Server 2025 database:

EmailAddressID EmailAddress
7              dylan0@ADVENTURE-WORKS.COM
8              Diane1@ADVENTURE-WORKS.COM
If I run this query, which row(s) are returned?
SELECT top 10
 *
 FROM person.EmailAddress
 WHERE REGEXP_LIKE(EmailAddress, '^D', 'i')
 AND BusinessEntityID IN (7,8)

See possible answers