|
Home > Archive > Commerce Server General > July 2005 > Guidance on auditing all data changes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Guidance on auditing all data changes
|
|
| KGriffie 2005-06-23, 7:50 am |
| Our client has governmental requirements for maintaining a historical record
of all updates they make to their site (both catalog and marketing
information). Our client needs to be able to make updates to their
production environment several times a day. They will be making updates in a
staging area and then moving updates to production (probably using an
incremental export/import). Has anyone attempted to implement a historical
auditing system in CS and if so, what approach did you take? MSFT has
suggested making a backup of the CS database(s), but that does not seem like
a scalable option when updates are being made several times a day.
| |
| Vinayak Tadas[MSFT] 2005-07-27, 5:52 pm |
| The catalog system in Commerce Server does not provide inbuilt support for
auditing.
I am not sure of other customers who have implemented or required auditing.
One thing you might be able to do is implement auditing by seeting triggers
on catalog tables and push the changed data to audit tables
Thanks
Vinayak Tadas
Microsoft
http://blogs.msdn.com/vinayakt
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Get Secure! For more info visit http://www.microsoft.com/security. Please
reply to the newsgroups only
--------------------
Thread-Topic: Guidance on auditing all data changes
thread-index: AcV39SceuTneAJQVRD6ZmrPODYXuww==
X-WBNR-Posting-Host: 65.202.185.20
From: "=?Utf-8?B?S0dyaWZmaWU=?=" <KGriffie@discussions.microsoft.com>
Subject: Guidance on auditing all data changes
Date: Thu, 23 Jun 2005 06:12:05 -0700
Lines: 9
Message-ID: <196BC3BF-5C43-4845-A634-9180D02FC727@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.commerceserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.commerceserver.general:2923
X-Tomcat-NG: microsoft.public.commerceserver.general
Our client has governmental requirements for maintaining a historical
record
of all updates they make to their site (both catalog and marketing
information). Our client needs to be able to make updates to their
production environment several times a day. They will be making updates in
a
staging area and then moving updates to production (probably using an
incremental export/import). Has anyone attempted to implement a historical
auditing system in CS and if so, what approach did you take? MSFT has
suggested making a backup of the CS database(s), but that does not seem
like
a scalable option when updates are being made several times a day.
|
|
|
|
|