Tracking Changed Data In Standard Edition

Mickey Stuewe wants to track changed data, but has to use Standard Edition:

I use a pattern that includes four fields on all transactional tables. This (absolutely) includes lookup tables too. The two table types that are an exception to this pattern are audit tables and error tables. I’ll cover why later in this article.

Four fields include CreatedOn, CreatedBy, UpdatedOn, and UpdatedBy. The dates should be DateTime2. CreatedOn is the easiest to populate. You can create a default on the field to be populated with GetDate().

This is a common pattern and works pretty well.  The trick is making sure that you keep that metadata up to date.

Related Posts

Initial Thoughts On dbachecks

Jess Pomfret has an initial use case for dbachecks: Each check has one unique tag which basically names the check and then a number of other tags that can also be used to call a collection of checks. For this example we are going to use several checks to ensure that we meet the following […]

Read More

Introducing dbachecks

Chrissy LeMaire announces that the dbatools team is onto something big: dbachecks is a framework created by and for SQL Server pros who need to validate their environments. Basically, we all share similar checklists and mostly just the server names and RPO/RTO/etc change. This module allows us to crowdsource our checklists using Pester tests. Such checks include: […]

Read More

Categories

January 2016
MTWTFSS
« Dec Feb »
 123
45678910
11121314151617
18192021222324
25262728293031