We use this to determine when data in a row has changed so we can load it into our SQL Server data warehouse for analytics and reporting. I knew there would be some overhead, and we tested it in QA and it seemed to be fine. Now I have some people complaining of slowness and they are blaming this change. How can I determine how much overhead this is causing? This is on Windows Server so not sure how I can capture this information, if it is even possible. Any thoughts?
DW_LASTTIME TIMESTAMP NOT NULL GENERATED BY DEFAULT FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP
Do more with