Reputation
488
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 4 16
Impact
~29k people reached

  • 0 posts edited
  • 0 helpful flags
  • 80 votes cast
Jun
12
revised SQL Server varbinary column modifying inserted data
added 453 characters in body
Jun
12
answered SQL Server varbinary column modifying inserted data
Jun
12
accepted Slow Performance Inserting Few Rows Into Huge Table
Jun
12
awarded  Famous Question
Jan
19
accepted Why are timestamps not always increasing with concurrent inserts?
Jan
19
awarded  Popular Question
Dec
8
awarded  Popular Question
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