Logging Improvement - DbChanges.Log

Alex Needham

Hello all,

The DbChanges log is a great tool to have. It provides at a high-level what changed, by whom, at what time…but it's a bit TOO high-level. Currently, the log shows:

20230822 09:55:25Cubesadmin
20230822 09:55:25Cubesadmin
20230822 09:55:26Cubesadmin
20230822 09:55:26Cubesadmin
20230822 09:55:26Cubesadmin
20230822 10:10:18DataReaderadmin
20230822 10:11:34DataReaderadmin
20230822 10:12:31DataReaderadmin
20230822 10:12:40DataReaderadmin
20230822 10:12:44DataReaderadmin
20230822 10:14:15DataReaderadmin
20230822 10:15:15DataReaderadmin
20230822 10:16:45DataReaderadmin
20230822 10:18:08DataReaderadmin
20230822 10:19:28DataReaderadmin
20231109 11:25:36DataReaderadmin

So I can see that I've changed Cubes and Data Readers…but with no information about WHAT cubes or WHAT data readers. In this state, the log is largely not useful to me aside from as a checksum to ensure I moved all the cubes that I intended to move. This log would be much more usable if it was altered to:

20230822 09:55:25CubesV001Cube1admin
20230822 09:55:25CubesV002Cube2admin
20230822 09:55:26CubesV003Cube3admin
20230822 09:55:26CubesV004Cube4admin
20230822 09:55:26CubesV005Cube5admin
20230822 10:10:18DataReaderDR1admin
20230822 10:11:34DataReaderDR2admin
20230822 10:12:31DataReaderDR3admin
20230822 10:12:40DataReaderDR4admin
20230822 10:12:44DataReaderDR5admin
20230822 10:14:15DataReaderDR6admin
20230822 10:15:15DataReaderDR7admin
20230822 10:16:45DataReaderDR8admin
20230822 10:18:08DataReaderDR9admin
20230822 10:19:28DataReaderDR10admin
20231109 11:25:36DataReaderDR4admin

With this simple addition, it's then possible to look in and actually understand what changed.