Results 1 to 2 of 2

Thread: For Reporting Purposes

  1. Feb 24th, 2009, 06:47 AM #1
    jsc0624
    jsc0624 is offline

    Thread Starter
    Addicted Member
    Join Date
    Mar 2007
    Posts
    240

    For Reporting Purposes

    Hi Guys,

    I have a database and I need to generate a report every month. Is it a good practice to copy the transaction tables to a new table just for reporting purposes and audit trail. And also for the purpose of viewing the prior year reports.
    Last edited by jsc0624; Feb 24th, 2009 at 07:00 AM.
    Reply With Quote Reply With Quote
  2. Feb 26th, 2009, 09:44 PM #2
    rasinc
    rasinc is offline
    Hyperactive Member
    Join Date
    Jul 2007
    Posts
    479

    Re: For Reporting Purposes

    I'm going to go out on a limb here because I am not going to suggest I am an expert or anything but doesn't that go against the normalization rules of database design? I assume you are referring to holding this information for long term not temporarily.

    Better to design the database to prevent the capabilities of editing previous records and forcing reversal entries of originals if necessary in order to edit them for audit trail purposes.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules


Click Here to Expand Forum to Full Width