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
Take a look at a sample chapter and see who won copies of this book from our Question of the Day Contest.
2007-09-13
2,759 reads
Longtime author here, Michael Coles, has written a new book on SQL Server 2005 Programming and has sent us a sample chapter on SQLCLR programming. Download the chapter and source code and grab this great book from your favorite bookseller.
2007-05-03
4,271 reads
Apress is giving away some copies of this book on SQLServerCentral.com by sponsoring our Question of the Day. A sample chapter is also available online now!
2005-12-15
4,637 reads
Cryptography and encryption are coming to many systems, including databases. Check out a sample chapter from this upcoming book.
2005-11-07
3,830 reads
By gbargsley
Recently, I was in a technical interview where the topic of running PowerShell at...
By alevyinroc
I don’t recall where this came up (probably in SQLSlack), but I had a...
By Steve Jones
One of the parts of getting older that really sucks is I seem to...
Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation
Hi, we put together an extract that runs every 15 minutes against what i...
Comments posted to this topic are about the item Parameter Sensitive Plan Optimization in...
A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?
See possible answers