Users may observe that for each database instance created in Strategy, the number of warehouse connections that can be simultaneously opened can be limited through the database instance job prioritization interface. The maximum number of simultaneous connections per database instance, per project, is the sum of the number of high, low and medium priority threads as shown below :
Users may wish to set similar limits for the maximum number of metadata connections. This may be true of in environments that have the metadata hosted on a shared database server where a common policy is to limit the number of allowed simultaneous connections a user / application can make to the database.
Currently, it is not possible, or supported, to modify the maximum number of metadata connections in Strategy 9.x and 10.x. The actual theoretical limit is dependent on the number of processing unit threads that are created by the Intelligence Server process to service the various components within the Intelligence Server. This is because every thread can potentially access the Object Server component, and by extension the metadata directly.
In practice, metadata operations are designed to complete very quickly, and so database connections are cached and re-used and only a few connections should be observed open under light load. Increased number of connections may be observed under high Intelligence Server load, or if a large number of metadata intensive search or other requests are being processed.
If the number of metadata connections is observed to be higher than normal over an extended range of times, users should contact Strategy Technical Support for assistance to identify potential unexpected causes.
