Drop Table

Support Forum for database administrators and web based access to important newsgroups related to databases
Register on Database Support Forum Edit your profileCalendarFind other Database Support forum membersFrequently Asked QuestionsSearch this forum -> 
For Database admins: Free Database-related Magazines Now Free shipping to Texas


Post New Thread










Thread
Author

Moving Data for Audit - Best Practice
Here is the situation:

Tables:
Account
AccountDocument
AccountTest


Then we have the following "Activity" table refencing "Account" table
above:
Table: Activity
Columns:   ActivityID, AccountNo,...

when "Activity" with accountno is created, we'd like to able to take
snapshop or copy all Account related data records from tables: account,
accountdocument, accounttest
and store it somewhere.


This way even if account, accountdocument and accounttest tables change
later, then "Activity" accountno integrity in maintained.

Do we need to create or replicate similar  tables to store data for
audit?

or Which other ways can this be achieved?


Report this thread to moderator Post Follow-up to this message
Old Post
grichardomi@gmail.com
10-27-05 02:24 PM


Re: Moving Data for Audit - Best Practice
(grichardomi@gmail.com)  writes:
> Here is the situation:
>
> Tables:
> Account
> AccountDocument
> AccountTest
>
>
> Then we have the following "Activity" table refencing "Account" table
> above:
> Table: Activity
> Columns:   ActivityID, AccountNo,...
>
> when "Activity" with accountno is created, we'd like to able to take
> snapshop or copy all Account related data records from tables: account,
> accountdocument, accounttest
> and store it somewhere.
>
>
> This way even if account, accountdocument and accounttest tables change
> later, then "Activity" accountno integrity in maintained.
>
> Do we need to create or replicate similar  tables to store data for
> audit?
>
> or Which other ways can this be achieved?

Wait until Nov 7th when SQL 2005 launches. :-)

This is really easy to solve in SQL 2005, thanks to the native xml
data type. You can use an FOR XML query to capture the data into an
xml variable, and then stored that data into an untyped xml column.
Really neat.

In SQL 2000 you can still use FOR XML, but you need a co-operating
client that gets the output from FOR XML and sends it back into a
text document.

Without XML and with the requirement that even if the table changes,
and without a co-operating client, this sounds extremely painful.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp


Report this thread to moderator Post Follow-up to this message
Old Post
Erland Sommarskog
10-27-05 02:24 PM


Re: Moving Data for Audit - Best Practice
If this is for an audit, have you considered a third party tool that is
approved for SOX, et al?


Report this thread to moderator Post Follow-up to this message
Old Post
--CELKO--
10-27-05 02:24 PM


Re: Moving Data for Audit - Best Practice
Help me! Please indicate which 3rd party tools  are you suggesting.


Report this thread to moderator Post Follow-up to this message
Old Post
grichardomi@gmail.com
10-27-05 02:25 PM


Sponsored Links





Last Thread Next Thread
Post New Thread

Microsoft SQL Server forum archive

Show a Printable Version Email This Page to Someone! Receive updates to this thread
Microsoft SQL Server
Access database support
PostgreSQL Replication
SQL Server ODBC
FoxPro Support
PostgreSQL pgAdmin
SQL Server Clustering
MySQL ODBC
Web Applications with dBASE
SQL Server CE
MySQL++
Sybase Database Support
MS SQL Full Text Search
PostgreSQL Administration
SQL Anywhere support
DB2 UDB Database
Paradox Database Support
Filemaker Database
Berkley DB
SQL 2000/2000i database
ASE Database
Forum Jump:
All times are GMT. The time now is 03:24 PM.

 
Mobile devices forum | Database support forum archive




Copyrights DropTable.com Database Support Forum 2004 - 2006