June 25, 2009 at 11:15 am
Comments posted to this topic are about the item The New Reality of an Audit Trail
July 8, 2009 at 8:36 am
If only using SQL 2008 I would use Change Data Capture it does it all for you.
July 8, 2009 at 9:37 am
Michael Whiteley (7/8/2009)
If only using SQL 2008 I would use Change Data Capture it does it all for you.
Unfortunately, Change data capture is available only on the Enterprise, Developer, and Evaluation editions of SQL Server. E.g. if company has 4-5 production servers with 4 processors each the price between Standard and Enterprise edition is prohibit to use this feature.
July 8, 2009 at 1:00 pm
how is this different than the standard audit tables that record changes?
July 8, 2009 at 3:58 pm
SQL Noob (7/8/2009)
how is this different than the standard audit tables that record changes?
a) it is allowed to gather additional data via XML
b) it is extended to the way that you can record only row changes instead of complete changes (may be for differential load)
c) It shows you not only the audit but how translate audit into something useful, for example to find which products are changed for differential load while you don't need to know exact changes.
At least those points in addition to my previous article where one of the point is the use of ROW_ID instead of complex primary key values.
July 8, 2009 at 3:58 pm
SQL Noob (7/8/2009)
how is this different than the standard audit tables that record changes?
a) it is allowed to gather additional data via XML
b) it is extended to the way that you can record only row changes instead of complete changes (may be for differential load)
c) It shows you not only the audit but how translate audit into something useful, for example to find which products are changed for differential load while you don't need to know exact changes.
At least those points in addition to my previous article where one of the point is the use of ROW_ID instead of complex primary key values.
July 8, 2009 at 3:59 pm
SQL Noob (7/8/2009)
how is this different than the standard audit tables that record changes?
a) it is allowed to gather additional data via XML
b) it is extended to the way that you can record only row changes instead of complete changes (may be for differential load)
c) It shows you not only the audit but how translate audit into something useful, for example to find which products are changed for differential load while you don't need to know exact changes.
At least those points in addition to my previous article where one of the point is the use of ROW_ID instead of complex primary key values.
July 9, 2009 at 12:17 am
It's early in the morning (pre-coffee) but where do you construct the xml?
July 9, 2009 at 1:46 am
Sorry didn't realise they had made that an enterprise only solution...
I just can't understand Microsoft's reasoning behind doing things like this.
Why spend loads of time developing really good features that soo few customers could use (by paying for enterprise) , and then even fewer actually use.
Had this conversation with Microsoft technical people in the past (who don't make these decisions) but there are of the same opinion - why ?
July 9, 2009 at 1:47 am
Sorry didn't realise they had make the an enterprise only solution...
I just can't understand Microsoft reasoning behind doing things like this.
Why spend loads of time developing really good features that soo few customers could use (by paying for enterprise) , and then even fewer actually use.
Had this conversation with Microsoft technical people in the past (who don't make these decisions) but there are of the same opinion - why ?
July 9, 2009 at 6:31 am
David McKinney (7/9/2009)
It's early in the morning (pre-coffee) but where do you construct the xml?
XML is constructed in application framework. Our application architects made object's property as auditable and, if checked, XML constracted by application and passed as parameter to a stored procedure. It guaranteed that each XML is in required standard.
July 9, 2009 at 7:01 am
everyone does this to some extent in their products
they make a list of features that they think companies will pay extra for and slap an Enterprise Edition label on it. In MS Exchange they did this by limiting the database on the standard edition to 16GB.
it's kind of like our progressive tax system
July 9, 2009 at 7:02 am
everyone does this to some extent in their products
they make a list of features that they think companies will pay extra for and slap an Enterprise Edition label on it. In MS Exchange they did this by limiting the database on the standard edition to 16GB.
it's kind of like our progressive tax system
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply