DLM Dashboard doesn't display the changes I expected
Published 20 July 2015
I can't see all the changes I was expecting
- If you can't see all the changes you were expecting, this may be because they are ignored by DLM Dashboard's default options.
Ignored changes won't affect the status of a database on the dashboard (ie indicate update or drift), won't trigger an email notification, and won't appear on the review page. See Changes ignored by default.
- Restoring a backup that contains schema changes may bypass the DDL trigger, which alerts DLM Dashboard to changes. In this case, the restored changes appear with the next change to the database.
- If an ALTER INDEX change doesn't result in a schema change (eg after a REBUILD) then DLM Dashboard ignores it, and it won't appear on the review page.
- Statistic updates are now ignored by DLM Dashboard. They won't appear on the review page or trigger an email notification.
I can see changes that I wasn't expecting
- If two databases on the same server share a common name, but with different casing (eg WidgetDev and widgetdev) DLM Dashboard can't differentiate between the two. Changes to one database may be shown on the other, or may not appear at all.
- If you've used SQL Compare before, you may not expect to see column order changes in Dashboard because they're ignored in SQL Compare by default.
Some changes show No details available
- By default, encrypted objects in 2005 and 2008 databases are decrypted by DLM Dashboard. Without
sysadmin
permissions, DLM Dashboard will recognize change in encrypted objects, but show limited details about the object. For more information about user permissions, see Creating a login with the correct permissions. - If an ALTER INDEX change results in a schema change (eg the value of ALLOW_ROW_LOCKS changes), information about the user that made the changes, the application used, and the date won't be available.