Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Design question on 3-tier application
Message
 
 
To
All
General information
Forum:
Microsoft SQL Server
Category:
Other
Title:
Design question on 3-tier application
Environment versions
SQL Server:
SQL Server 2005
Miscellaneous
Thread ID:
01315981
Message ID:
01315981
Views:
68
Good evening,

As I am converting my program from monolithic to a 3-tier I have across the following challenge.

I have a routine where user enters a lot of data and a couple of different modules have to be updated. Each module has several tables. For example, user enters a work orders and enters labor and materials. Therefore 3 modules have to be updated: work order, labor, and materials. Each one has business and data tier objects. And each one will use TRANSACTION when updating tables of the module, in order to be able to revert changes if anything fails. The issue is how to make sure that if one module update fails other modules can be reverted? or what to do? Following the example above, say user says SAVE. Program updates work order module (via work order object), then labor module (via labor object), and then materials module (via materials object). But materials update fails. How do you recommend graceful revert or some way of getting back on the work order and labor module tables?

Any suggestions would be greatly appreciated.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Next
Reply
Map
View

Click here to load this message in the networking platform