|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 6:18 AM
Points: 129,
Visits: 205
|
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, July 29, 2010 8:07 AM
Points: 36,
Visits: 71
|
|
If only using SQL 2008 I would use Change Data Capture it does it all for you.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Monday, January 30, 2012 5:12 AM
Points: 40,
Visits: 143
|
|
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.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Yesterday @ 2:11 PM
Points: 1,409,
Visits: 4,506
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 6:18 AM
Points: 129,
Visits: 205
|
|
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.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 6:18 AM
Points: 129,
Visits: 205
|
|
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.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 6:18 AM
Points: 129,
Visits: 205
|
|
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.
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:43 AM
Points: 582,
Visits: 1,601
|
|
| It's early in the morning (pre-coffee) but where do you construct the xml?
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, July 29, 2010 8:07 AM
Points: 36,
Visits: 71
|
|
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 ?
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Thursday, July 29, 2010 8:07 AM
Points: 36,
Visits: 71
|
|
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 ?
|
|
|
|