Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: Enterprise
Expertise: Advanced
Jun 11, 1999

Determine Transaction Isolation Levels

When architecting a client-server or n-tier application, you should decide on a particular locking technique and accordingly the transaction isolation level and concurrency control strategy for database transactions. This decision becomes critical as not making it in initial phase might introduce significant changes later on when the application is in the development phase. Also, not choosing the appropriate transaction isolation level and concurrency control might result in data inconsistency, poor performance in a multiuser scenario, and frequent deadlocks. So, the key to avoid these problems is to understand these features completely for the target platform and apply them according to the need of the application being developed.
KulBhushan Sharma
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date