Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Netvoid
Starting Member
2 Posts |
 Posted - 2006-11-29 : 21:32:22
|
| Looking for input/advise on a situation my business is having with an application that is posting mission critical financial data from hundreds of remote sites into a SQL Server database.The server side application that posts the received data from the clients into SQL Server does not have an error handler, but more an error logger. When deadlocks or many other errors occur data loss results. The application logs the error to a flat text log. The application does have a recovery method for the lost data but the process is time consuming and manual.This is not a custom appplication. The company that wrote this software is basically stating that it is common practice for an application like this to not incorporate deadlock detection or other common error handling routines to repost financial transactions.Thanks in advance for any input or experienced advice regarding this topic. |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-11-29 : 22:31:12
|
| I see two things that tell me that you are dealing with a vendor that doesn’t know what they are doing.First, if deadlocks are common enough that you are seeing them on a regular basis, it means that the database and application are poorly designed and implemented.Second, the fact that they have no plan for dealing with lost financial transactions tells me the same thing.Tell them that their next maintenance payment got deadlocked and lost. Start looking for a vendor that knows what they are doing.CODO ERGO SUM |
 |
|
|
Netvoid
Starting Member
2 Posts |
Posted - 2006-11-30 : 10:42:04
|
| Well they have been helpful when our internal DBA does all the work of pin-pointing which of the transactions are deadlocking and the ineffective index usage they do correct the code to reduce the errors.At one point our database log drive on a raid array had a problem and no transactions were being posting into the database. The system kept posting and deleting transactions as though no issue was in play. We lost days of information and it took quite a few days to recover. I'm really just trying to understand if the argument that "Systems that post this quantity of transactions typically do not have error handling.", another point of view they have stated is, "Academically you are correct applications should have error handlers but in the real world they are impractical.".Those quotes are straight from two of the leading development executives at the company we are working with. |
|
|
|
|
|
|
Error Handling SQL Application