Creating an Error table

sujaoschin · Post by **sujaoschin** » Wed Aug 27, 2008 7:23 pm

I have 3 different lookups and these 3 lookups have rejections and exceptions. Which is the best method to design the error table? Either to have separate error table for each lookup with the key field, error no,error code, and error description or to have a common error table so that it can be referred ?

ray.wurlod · Post by **ray.wurlod** » Wed Aug 27, 2008 8:44 pm

Whatever is right for your business. Who is going to look at this error table/these error tables? What do THEY need?

tkbharani · Post by **tkbharani** » Wed Aug 27, 2008 10:12 pm

It depends on the way you are going to use it again. Mostly error tables are checked rarely. You are inserting with error number,error code. So why seperate table, store it in single table.

Bury all errors in single table.

sujaoschin · Post by **sujaoschin** » Thu Aug 28, 2008 1:39 am

The purpose is for the business wants to see the rejected records and to know the reason why it got rejected and for the reconcilation purpose.

ray.wurlod · Post by **ray.wurlod** » Thu Aug 28, 2008 1:47 am

And does "the business" want to look at one table or lots of tables?

My personal preference is for a single table - but my personal preference ought not to influence your business users' requirements.