Frequently asked questions about the SQL Server PI repository release.
Q: What are the sizing requirements?
A: Sizing details are available in KB 313850.
Q: What type of training is available?
A: KB 313191 details how to migrate database agents to a SQL Server repository from an Infobright PI repository. Please contact Quest for additional training information.
Q: What versions of SQL Server are required?
A: The customer will require either SQL Server 2016 or higher (Standard or Enterprise) for the MSSQL PI repository running on Windows 2016. A database must be created and available prior to the installation or conversion process. Currently we do not have a licensing arrangement to use SQL Server on behalf of the customers.
Q: Can a SQL Server instance on Linux be used for the SQL Server PI repository?
A: No, the SQL Server instance used for the SQL Server PI repository must be on Windows 2016 or higher.
Q: What general release cartridge versions includes the new SQL Server PI repository functionality?
A: The 184.108.40.206 SQL Server and Oracle cartridges include the SQL Server PI repository as a replacement to the Infobright component.
Q: Is the Visual C++ 2010 redistributable still required
A: Visual C++ was used for the installation of the Infobright software. This software is no longer used since the PI agents make a direct connection to a SQL Server instance.
Q: Are different versions of the DLP executables required for mixed environments?
A: The brighthouse/Infobright components are not used in design. Mixed environment issues for Linux/Windows for the DLP processor are not applicable.
Q: Is port 5029 still required to connect between the SQL PI repository and the FMS/FglAM?
A: The SQL PI repository will use a SQL Server based repository. The port requirements will depend on the configured SQL Server port.
Q: Are VM CPU and memory reservations required?
A: Internal testing has determined the VM CPU and memory reservations are not a requirement, but memory reservations are highly recommended for SQL Server by Microsoft. The CPU reservations for Infobright SQL PI were largely required due to PostgreSQL requirements.
Q: Are antivirus exclusions still required?
A: General Foglight FMS and Foglight antivirus exclusions are still required. Antivirus exclusions applicable to SQL Server as per Microsoft recommendations are suggested.
Q: Can a Windows domain account be used to connect to a MSSQL PI instance?
A: Both a SQL Server account and a Windows (Active Directory) account is supported.
Q: Are specific full control or 744 permissions required on the PI repository server for the SQL Server PI to collect more than four hours of data when a named service account is used?
A: This was a specific issue with the Infobright installation. These additional permissions are no longer necessary.
Q: Can Oracle, SSAS, and SQL Server agents be monitored using the same FMS if the agents refer to different FglAMs and different PI repositories (either Infobright or SQL) Server depending on the agent type?
A: SQL Server, Oracle, and SSAS agents are supported using the same SQL Server PI repository instance.
Q: Will Quest include a SQL Server license as part of the SQL Server PI repository installation?
A: Currently we do not have a licensing arrangement to use SQL Server on behalf of the customers.
Q: Does a SSAS agent require a matching SQL Server agent on the same FMS/PI repository?
A: No, the SSAS agent is independent of the SQL Server agent.
Q: Why was SQL Server chosen as the MSSQL PI repository?
A: Several reasons have been discussed
Q: Can existing SQL PI licenses be used with MSSQL PI?
A: Existing customer licenses for SQL PI can be used with the SQL Server repository installation. Foglight licenses are based on the cartridge name. The SQL PI cartridges (SPIRepository) and agent type names are not changing in the new design.
Q: Will historical PI data from Infobright be available to the new MSSQL PI?
A: Beginning with the 220.127.116.11 cartridges, a migration utility for data from Infobright to SQL Server is available in KB 313133.
Q: What type of authentication is supported for connections to the SQL Server based PI repository?
A: Both SQL Server and Windows (AD) authentication are supported for the connection the SQL Server PI repository.
Q: Can Oracle and SQL Server agents share the same SQL PI repository database?
A: SQL Server, Oracle, and SSAS agents cannot store data in the same SQL Server PI Repository database. Each type of agent must use their own unique database. There can only be one database in each SQL Server instance (repository) for each type of agent (MSSQL, Oracle, or SSAS).
Q: How many database agents can be monitored by a SQL Server instance?
A: There is a limit of 300 monitored agents per SQL Server instance. .. it could be 100 SQL Server host, 100 Oracle hosts, 100 SSAS hosts for example.
Q: Can multiple SQL Server instances (each for a different SQL Server PI repository) be installed on the same server?
A: Server Level Consolidation in which the customer can has 2 PI repository instances on the same machine is supported, but we recommend that they use different physical storage, and also need to set Maximum SQL Server Memory according to the PI Sizing Guide for each instance.
Q: Is there a limit to the number of FglAMs connecting to a SQL Server PI repository?
A: The FglAM limitation has been removed (3 FglAM to one PI repository). One large customer is already using local monitoring, about 100 Fglams to one PI repository. We also do not don't have the repository limitation in the FMS.
Q: As there is a limit of 300 instances for a single MSSQL Server SQL PI Repository, even though it would need to be an incredibly beefy host, could you have two SQL PI Repositories on the same host?
A: Yes, multiple SQL Server instances can be installed on the same server with each instance handling up to 300 database agents (Oracle, SQL Server, and/or SSAS).
Q: Can't a user just add more CPU and RAM at a single instance and that single instance be able to handle a higher number of agents or why they couldn't have multiple SQL PI Repositories (multiple databases) within the same SQL Server instance?
A: Quest R&D has done extensive testing with 300 agents over many months both with performance and the number of connections handled. Going beyond 300 instances would be an untested scenario. In regards to potential bottlenecks, this could be a combination of CPU and memory. Each SQL Server instance has dedicated access to it's own memory, so having a single repository on separate instances, gives each repository it's own dedicated access to a block of memory. If there were two databases on the same instance, each database would have to compete for the same memory space.
Q: Will using multiple SQL Server instances require separate licenses for each instance?
A: SQL Server itself is licensed per core, so multiple instances on the same host would not affect their licensing with Microsoft.
Q: Can multiple PI repositories be used with a single FglAM?
A: Each FglAM can only connect to a single PI repository. The SPI-Repository, DBSS-SPIRepository, DBO-SPIRepository, and SSAS-SPIRepository agents on each FglAM include ASP (agent status properties) specific with connection information to a single SQL Server Instance (and databases).
Q: Can multiple FglAMs connect to a single SQL Server PI repository?
A: Multiple FglAMs can connect to a single SQL Server PI repository. We currently recommend up to three (3) FglAMs reporting to a single PI repository for connection management reasons.
Q: Can a single SQL Server PI repository be shared between different FMS environments.
A: A SQL Server PI repository cannot be shared between different FMS environments because the PI data would be rolled up multiple times causing the data to become inaccurate.
Q: A FMS has multiple Infobright SQL PI repositories, each of which have less than 100 instances. The user wants to retain the data and minimize the number of SQL Server instances. Is it possible to migrate the history from three Infobright PI repositories into a single SQL Server PI repository?
Could the migration utility be run three times and point to the same SQL Server PI repository each time?
A: Migrating the contents from multiple Infobright PI repository into one SQL Server PI repository is not supported. Each Infobright PI repository uses the same instance key (i.e. 1-100). When migrating the Infobright data to a SQL Server repository, Foglight has to manage the instance mapping, otherwise the data will be merged by the instance key.
Q: After upgrading to the 18.104.22.168 (or higher) cartridge, will Infobright continue to run as an extension to the SQL Server and Oracle database agents already configured?
A: The upgrade wizard will automatically disable the Infobright PI extension for existing database agents that were upgrade from cartridge versions below 22.214.171.124. The following steps will be done by the upgrade wizard when upgrading.
Q: How is the data migration handled in situations where there are already more than 300 database agents using an Infobright SQL PI repository and it will be necessary to split the data set among two SQL Server PI repositories?
A: The PI migration utility includes a dialog box to select among the database agent instances in the source database to choose those agents whose data will be migrated. Please refer to KB 313133 for details on using the SQL Server PI repository migration tool.
© 2020 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz