Tips for catching changes in table data over time interval for export to Data Warehouse
The simplest way to handle this may be a bit field like IsDirty that is updated with a trigger, and set to 0 for the whole table when you run your ETL.

If this is set to 1 for every row that is updated, and you give it a default value of 1, then you can make export views for your ETL that filter on IsDirty = 1 so you only interact with new rows.

If you need to know when data was changed and/or have multiple ETL processes hitting the same data, then you will need to have a datetime field and store export dates and times in your config table.