Below is a table listing the pros and cons, showing why Foglight for SQL Server keeps using DMV tables.
Parameter | Remarks (DMV) | Product impact (DMV) | Remarks (XE) | Product Impact (XE) | Plus for... |
---|---|---|---|---|---|
Performance | fast, data retrieved from tables | Quering tables is fast | slower, data is parsed from physical files | parsing thousands/millions of lines is slow | DMV |
Table locks | Schema changes (table/index) lock the DMV tables | Product collections are halted | no locks, data is parsed directly from files | Data needed for the collections is always available from files | XE |
Implementation | No interaction fro user end is required | Automatic product deployment | The user is required to configure/set the env to work with xevents | Post installation steps are required from User end | DMV |
Instance & Host overhead | Query tables overhead is negligible | Almost no overhead on Insatnce | Each event is registered into file | Higher processing power and disk space is needed | DMV |
History | Tables holding momentarily information | Not all events are captured | Holds all of the events running in the instance | In case of difference of opinion if the product did well or not - xevents has an advantage | XE |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center