Session settings
Updated: 2009-04-16
The session settings specify limitations on how clients interact with a Planning Server. Any changes that you make to the session settings will not affect existing sessions unless these sessions are closed, or expire and are then reopened. All new sessions will automatically use the new session settings. A session is essentially a connection; many of the session settings affect the length of connection time, the number of connections each user can have, as well as the number of connections that can be made simultaneously. Use the following procedures to specify session settings for the server that is running Planning Server and to which you are connected.
To set session preferences
In the Session timeout box, type the number of minutes that a Planning Server session will remain active before timing out.
In the Maximum sessions per user box, type the maximum number of simultaneous Planning Server sessions each user can have.
In the Maximum total sessions box, type the maximum number of total sessions that all users who are logged on to Planning Server at the same time can have. Members of the Global Administrator role can still connect to Planning Server after the number of maximum total sessions is reached.
In the Chunking size box, type the number of rows of data, per chunk, to load to the computer that is running Planning Server. Data is loaded into Planning Server applications by chunks and this setting can improve processing time when you have large amounts of data. For example, when a fact table that has ten million rows must be loaded to a Planning Server application database, the rows are chunked into smaller pieces to prevent the server from being overloaded. If the chunk size is ten thousand rows, the load is handled in 1,000 chunks (10,000,000/10,000).
In the Maximum number of query results box, type the maximum number of records (rows) to return from the server. This setting limits the number of records that are returned by the Planning Server to client applications. For example, when a user queries for all product dimension members, the value that is specified in this box indicates the number of records to return.
In the SQL Server timeout box, type the number of seconds before Planning Server will time out when it requests data from Microsoft SQL Server. The default setting is 1,200 seconds, or 20 minutes, and is, in most cases sufficient. If you know you are requesting large amounts of data from the Microsoft SQL Server you can increase the timeout setting accordingly.
In the Planning Server MDX command timeout box, type the number of seconds before MDX queries will time out. The MDX queries are from clients that are requesting data from the Planning Process Service or Planning Web Service.
Click Submit.
To reset session preferences to default settings
To reset session preferences to the default settings, click Reset Defaults. The following table describes the default settings.
Field Name Default Setting Session timeout (minutes)
60
Maximum sessions per user (counts)
128
Maximum total sessions (counts)
134,217,728
Chunking size (rows)
100,000
Maximum number of query results
1,000
SQL Server timeout (seconds)
1,200
Planning Server MDX command timeout (seconds)
1,800
Click Submit.
Note
If you receive a Web service error stating that the Microsoft Office Excel file you are trying to submit contains too much data you need to edit the Web.config file. The Web.config file is deployed to the server installation folder; by default this file is located at:
C:\PerformancePointTemp\3.0\WebService.You can increase the size of the maxRequestLength value found in the Web.config configuration: <httpRuntime maxRequestLength=”desired size”/> (by default the maxRequestLength value is set to 500,000KB (500MB). Increase this value and then resubmit the Excel file. For more information see this Microsoft MSDN article.