Release Notes : SQL Server (05/12/20)
Welcome to the release notes for Live Optics for SQL Server and Optical Prime.
- May 12, 2020
- SQL Server config data collected during Optical Prime collection
- SQL Server associations to Optical Prime parent project (Release due June 2020)
- SQL Server performance metrics (Release due August 2020)
Known Issues / Expected Behavior
The following known limitations should be considered when using Live Optics to assess an SQL Server Instance;
- SQL Server can be discovered on the environment regardless if the SQL Service is RUNNING, NOT RUNNING, DISABLED or PAUSED status.
- User will not be notified upon creation of SQL Server projects spawned from Optical Prime parent projects. The user will only be notified if the SQL project is in an ERROR status or has failed to upload to the Live Optics Web Portal.
- SQL Server projects spawned from an Optical Prime parent project will not appear in the Live Optics Dashboard. SQL Server child projects are searchable through the Project Search option in the Live Optics Web Portal.
- If the SQL server instance has not been given a name, the instance will appear as MSSQLSERVER. This is the default instance name.
- The field FILESTREAM CONFIGIURED LEVEL appears blank for SQL SERVER versions 2008 and 2008 R2. This indicates that the feature is unsupported by these versions.
- Browser must be refreshed to see the project updates
- Once the project is uploaded to the Web Portal, and the user must refresh the page in order to see the updated project status.
- Internet connection is required
- To run a collection where the user chooses to upload the project to the online web portal, the collector must have access to the internet.
- If the user attempts to run a collection and upload it to the Live Optics Web Portal without an internet connection, the user will be presented with an error prompting them to run the collection once more and save their project as an SIOKIT. to upload later when the collector has internet access.
- The Live Optics Collector services must be allowed through the user firewall to run a successful collection.