Wanted: book recomendations C#, SQL, with Timestamps

[Robert Schuldenfrei]

Dear NG,

I have not heard from anyone about a good book that deals with the
concurrency issue in SQL Server using C#. I have PROMISED Nick I would not
use record locking and I have used an old row / new row approach. (see next
paragraph for my reply to Nick) I would like to use Timestamps and
Transactions to produce an iron-clad and efficient application in a
multi-user environment. Can anyone recommend such a book?

OK Nick, I promise NEVER to even CONSIDER locking. I have two new skills to
learn: 1/ Transactions and 2/ using timestamps. I had been using a
technique of old record / new record to determine if the record had been
changed on update or delete. Timestamps seem more elegant. Sadly, the book
I have been using for learning SQL is Petkovic, SQL Server 2000, A
Beginner's Guide. He mentions timestamps, but then goes forward to
explaining locking (and not to well I might add). Can you suggest a good
book that implements your suggested approach to concurrency that would cover
both the C# and the SQL issues?

Thank you,

Bob

Robert Schuldenfrei
(e-mail address removed)

 

[Joerg Jooss]

Dear NG,

I have not heard from anyone about a good book that deals with the
concurrency issue in SQL Server using C#. I have PROMISED Nick I
would not use record locking and I have used an old row / new row
approach. (see next paragraph for my reply to Nick) I would like to
use Timestamps and Transactions to produce an iron-clad and efficient
application in a multi-user environment. Can anyone recommend such a
book?

[...]

If you don't mind reading Java articles, I recommend looking up web
resources on "Optimistic Locking" -- I guess that's what you're referring
to.

Cheers,

 

[Scott Allen]

Robert:

Try in the microsoft.public.dotnet.framework.adonet newsgroup. William
Ryan should be able to give you a good book reference.

 

[Kevin Yu [MSFT]]

Hi Robert,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you need a reference book about
concurrency issues. If there is any misunderstanding, please feel free to
let me know.

In your last thread, Scott has given us a good article "Handling Data
Concurrency Using ADO.NET"
John Papa
http://msdn.microsoft.com/msdnmag/issues/04/09/DataPoints/default.aspx

There are many technical articles about ADO.NET concurrency on the web.
Here is one of them

http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/
en%2Ftranscripts%2Fwct050103.asp

Based on my research, there doesn't seem to be books dealing with
concurrency issues dedicatedly. However, some ADO.NET books have topic
about this. Here are some of them.

http://www.amazon.com/exec/obidos/tg/detail/-/0201758660/104-0087697-3274358
?v=glance
http://www.amazon.com/exec/obidos/tg/detail/-/0201745682/104-0087697-3274358
?v=glance

HTH.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[Robert Schuldenfrei]

Hi Kevin,

Thanks for the follow up. I have printed out the articles you and Scott
suggested. I have noted the two books below. I now face the classic issue
of students: Do I just read the articles and plow right into my application
OR do I get the book and learn ADO.NET cold? I am 61 years old and doing
this just for a hobby, so I think I will take the latter approach. I live
in suburban Boston and we have a great technical book store, SoftPro, in
Waltham. I will see if they have either one of the books you mention.

The John Papa article has an interesting slant that I picked up on by just
briefly looking over the paper. He talks about the old row / new row
technique, the TIMESTAMP, and placing his own DATETIME column in the record.
He says he prefers the TIMESTAMP, but then goes on to illustrate the
DATETIME method! I am currently using the old row / new row technique so I
was disappointed to see that he was not going to demonstrate the TIMESTAMP.
Ah well...

Thank you for taking the time to help me. In some ways my knowledge is very
deep. I programmed an IBM 7044 back in 1963. But in many respects my
command of the wonderful world of object orientated programming is indeed
shallow. My professional career was in the application of computer based
techniques and not in programming per se. It is only now in retirement that
I get a chance to program for fun.

Cheers,

Bob

Robert Schuldenfrei
(e-mail address removed)

 

[Kevin Yu [MSFT]]

Hi Robert,

Never too old to learn!

The technical articles only solves problem in certain aspect. If you need
to learn the whole ADO.NET architecture for better programming, I suggest
you read Bob's Essential ADO.NET (I have met Bob once. or David's
Microsoft ADO.NET (Core Reference). Here is a link for this book.

http://www.microsoft.com/mspress/books/5354.asp

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."