Spotlight Developer v6.5
The key features added in this release
- SQL Server Discovery.
- Scanning SQL Server instances can very useful especially in large and dynamic environment. The scan engine can be filtered by constraining IP address range and/or selecting one or more network domains. Each scan result can be kept and used to compare previous scan results. Thus able to determine new instances and retired instances. I will go deeper into this feature in a follow up blog (stay tuned).
- Configurable Port Numbers.
- As you are aware Spotlight Developer is multi-tiered. The “client” installed into SSMS, the Diagnostic Server on your network and Spotlight Essentials’ Cloud services. The communication between these use http(s) which means tcp/ip ports are required. The default installation uses ports 443, 60000, 59883. Sometimes customer have installed other vendor software using these one or both port(s) (i.e. 60000, 59883). Thus customers had to find another machine to install. In previous releases these ports where hard coded! Now we have configurable files for both the SSMS component and the Diagnostic Server. Please contact Spotlight Developer support (SpotlightDeveloper@quest.com) to apply non default ports.
- Fixed an issue when the installer cannot connect to a SoSSE 11.x DS.
- Some Customer reported difficulty configuring to connect to a Spotlight on SQL Server Diagnostic Server during the install process. The workaround was to install a local Diagnostic Server, then launch Spotlight Developer to change to the desired SQL Server Diagnostic Server via the Settings.
- Change the support email to spotlightdeveloper@quest.com.
- Spotlight Developer now has its own support email address (previously shared with Spotlight Cloud services). For you the customer this change has little impact.