Hi, thanx for the feedback.
As Ben points out, if you know which fields on the Database object you need, you can use Server.SetDefaultInitFields to make sure the collection is initialized with all those fields in the first query.
Is there a particular scenario, using the latest SMO NuGet, where use of SetDefaultInitFields isn’t sufficient to speed up the query noticeably?
If you have an Intellitrace or XEvents trace I could use for reference it’d be a great help.
This feature is in private preview and will be available to all users in coming months.
We are actively improving our monitoring experience. Currently we have ‘DWU Used’ in the portal which is a blend between CPU and IO to indicate data warehouse utilization. We also have future improvements on our road map such as Query Data Store and integrating with Azure Monitor for near real time troubleshooting in the Azure portal. If anyone has any other feedback, please elaborate on your scenario on this thread. Thank you for your continued support!
We are actively exploring ways to enable event-driven backups. Currently this scenario can be addressed by User Defined Restore Points which is on our road map for this calendar year. Stay tuned and thank you for your patience.John Q Martin shared this idea ·