424 reputation
414
bio website profdata.com
location Temple, TX
age 42
visits member for 3 years
seen Oct 15 at 13:44

I've been programming for about 20 years now (eek!). My first job was in COBOL, but mainframes and I do not mix. I coded several years in Java back in the JDK 1.0.2 days. Did some C++ and COM. Worked on Java + WFC from Microsoft. Been writing C# code for 6 years.

Married with two kids. Kids do not compute. Wife is wonderful, understanding, and sympathetic, but she=g=d=+++----CARRIER LOST


Oct
15
awarded  Popular Question
Sep
8
awarded  Notable Question
Jul
2
awarded  Curious
Nov
25
comment Why are timestamps not always increasing with concurrent inserts?
@MaxVernon - Actually, this could be a problem for us even in READ COMMITTED isolation. If the second transaction finishes before the first with its higher timestamp values, then our cache will retrieve it. Unfortunately, since its maximum known timestamp is now higher than all of the first transaction's records, our caching code will never retrieve any of them.
Nov
25
comment Why are timestamps not always increasing with concurrent inserts?
@Kin - Martin Smith is correct, the function is essentially a tally table.
Nov
25
revised Why are timestamps not always increasing with concurrent inserts?
included code for function dbo.fn_GenerateNumbers
Nov
25
comment Why are timestamps not always increasing with concurrent inserts?
@MaxVernon - The concern stems from an issue I found in our own software. One of our queries that deals with caching data was doing a dirty read. If this read happened to read a higher timestamp from a second thread, the cache would never synchronize with the rest of the records from the first thread. While this was a problem in our software, it made me question why the database timestamps would behave this way.
Nov
25
comment Why are timestamps not always increasing with concurrent inserts?
+1 Your observations about IDENTITY columns sound reasonable to me. I'm curious if anyone can answer the timestamp question.
Nov
25
revised Why are timestamps not always increasing with concurrent inserts?
added 8 characters in body
Nov
23
asked Why are timestamps not always increasing with concurrent inserts?
Oct
3
awarded  Yearling
Aug
29
revised PAGELOCK Conversion Deadlock From Update to Intent Exclusive
added 226 characters in body
Aug
7
revised PAGELOCK Conversion Deadlock From Update to Intent Exclusive
added 91 characters in body
Aug
7
comment PAGELOCK Conversion Deadlock From Update to Intent Exclusive
@MarkStorey-Smith Good point about the SP1. Recommended to the customer to try SP4.
Aug
6
asked PAGELOCK Conversion Deadlock From Update to Intent Exclusive
Jul
16
awarded  Popular Question
May
10
revised LATCH_EX Waits on Resource METADATA_SEQUENCE_GENERATOR
added results of MS support call
May
10
comment LATCH_EX Waits on Resource METADATA_SEQUENCE_GENERATOR
The SQL Server engineer agreed it was probably the IDENTITY column. We took it off of the already wide clustered index and removed the column entirely. It was not necessary. Afterwards, these LATCH_EX waits went away. We could not duplicate the waits on SQL 2008 R2. The issue happened only on SQL Server 2012.
May
10
accepted LATCH_EX Waits on Resource METADATA_SEQUENCE_GENERATOR
Apr
23
revised LATCH_EX Waits on Resource METADATA_SEQUENCE_GENERATOR
noted MS case opened