Thanks for the feedback.
Upvotes: 13<=-=Nov 10 2009 2:43PM=-=>
There is already an existing item on that:
-Jens<=-=Sep 23 2011 1:40PM=-=>
Thanks for the feedback Chuck – Jens is correct in that this item is already being tracked via 381744.
+1 to John Martin
CMS (RegisteredServers) has been ported. It will be included in the next version of SMO and/or the next version of the SQL Powershell module.
Can we please get core dlls for CMS Registered Servers? it is one of our most popular commands since cms servers can easily be piped in to any command in the toolset
Yes, please! This is one of our most common requests. Here's what we currently support in dbatools, if there's some sort of priority needed.
Backup and Restore
Diagnostics and Performance
Export (Right click -> Export)
High Availability (Availability Groups and Mirroring)
Login and User Management
Mail and logging
Security and Encryption
Traces, Profiler and Extended Events
Writing to SQL Tables
Our most popular commands revolve around migrations and exports of:
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.
Since it looks like you’re in the same ballpark as SSMS we will focus on other items for now.
Looks like we were missing streaming and now got it down to 67 seconds, which is far more reasonable 👍 Would still like a command line version but not as pressing ;)
Got it! 10-15 seconds to load into SSMS 17.4 then 45 seconds to export.
So 60 seconds total. Our .NET export is still at quadruple that, 240 seconds.
Aw I didn't notice your comment! I'll ask Gianluca, he had the 1gb file.