Post reply

Transaction and Locking

  • November 24, 2009 at 9:27 pm

    #96120

    I have a asp.net application which is used intranet by the client. The hospital patient turn over is 900 per day and at least 40 users use the application at one time. I have used transaction wherever there is multiple table insert involved as transactions lock the tables the application becomes a bit slow. Please advise.

  • November 25, 2009 at 8:38 am

    #1084100

    As Bru commented on your other post of the same topic, without more information it is hard to give you anything but simple best practices.

    • Keep transactions short
    • Make sure you have proper indexes and that your indexes are being used.
    • Make sure you are using the proper isolation level. By default this is READ COMMITTED. If you are using SERIALIZABLE then you will have more blocking issues.

    I also always like to remind people that locking and blocking are GOOD things in an RDBMS. You just need to make sure you are following the Best Practices above and that you have a good OLTP database design. A poor design will lead to concurrency issues.

    Jack Corbett
    Consultant - Straight Path Solutions
    Check out these links on how to get faster and more accurate answers:
    Forum Etiquette: How to post data/code on a forum to get the best help
    Need an Answer? Actually, No ... You Need a Question

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply