Information Centric Analytics

 View Only

Information Centric Analytics Best Practices - Post Configuration Tasks 

Aug 27, 2019 03:27 PM

After installing Symantec Information Centric Analytics, there are several configuration settings that should be set to allow the product to perform optimally. Follow the best practices below just after you install the platform, and before you begin configuring integrations, to ensure you get the most out of Information Centric Analytics.

Analysis Services Database Configuration

There are some additional SQL Server Analysis Services setting that may help improve the performance of ICA.  Below are recommended configuration modifications:

1. Log in to Microsoft SQL Server Management Studio and connect to the Analysis Services database and ensure the following settings are configured within the General Settings properties (make sure that the Show Advanced option is selected in order to see all options listed below):

Settings

Requirement

ExternalCommandTimeout

360000

ExternalConnectionTimeout

360000

Memory\TotalMemoryLimit

In a shared environment with Microsoft SQL Server and Microsoft SSAS on same server: 45

NOTE: This should be set in conjunction with setting the SQL Server Relational Engine memory configuration to 50% of available server memory.

 

In shared environment with Microsoft SSAS on a standalone server: 75

ServerTimeout

360000

ThreadPool\Process\MaxThreads

150

ThreadPool\Process\MinThreads

1

ThreadPool\Query\MaxThreads

48

ThreadPool\Query\MinThreads

1

 

 

SQL Server Settings

There are some additional SQL Server settings that may help improve the performance of ICA.  Below are recommended configuration modifications:

 

Remote Server Connections

1. Open SQL Management Studio

2. Connect to the ICA database server using SQL Management Studio

3. Right-click on the SQL server on SQL Management Studio and select Properties

4. Select the Connections page

 

5. Check Allow remote connections to this server and set the Remote query timeout value to 0 (no timeout)

 

6. Click OK to save changes

 

Server Memory Options

The minimum and maximum server memory is used to configure the amount of memory, in megabytes to establish upper and lower limits of memory used by the buffer pool on the Microsoft SQL Server. SQL Server Engine starts with only the memory required to initialize. As the workload increases, it keeps acquiring the memory required to support the workload, and never acquires more than the level specified in max server memory. The default setting for min server memory is 0, and the default setting for max server memory is 2147483647 MB.  A general rule of thumb is to leave the operating system 20% of the memory. 

1. Open SQL Management Studio

2. Connect to the ICA database server using SQL Management Studio

3. Right-click on the SQL server on SQL Management Studio and select Properties

4. Select the Memory page

 

5. Enter the appropriate memory size under Maximum server memory (in MB)

6. Click OK to save changes

 

Increasing SQL Server Agent Job History Retention

By Default, the history retention for the SQL Server Agent Jobs is only a few days or the last few runs of ALL SQL Server Jobs on the SQL Server.  Depending on server setup, there could be multiple jobs setup.  Each job will be “fighting” for a part of the job history log.  The SQL Agent Job History retention settings are for the SQL Server instance and not specific to any one job. By default, SQL Server Agent Job History is setup to purge all SQL Agent History records once the history log reaches a certain number of rows. Use the following steps to disable the size limit specified by the SQL Server Agent Properties.

 

1. Open an instance of SQL Server Management Studio (SSMS)

2. Connect to the ICA database server

3. In Object Explorer, expand the database server

4. Right Click on the SQL Server Agent and click on Properties

 

 

5. In the SQL Server Agent Properties window, select History

 

 

You have the following options:

1. (Not recommended) Limit size of job history log:

  • Maximum job history rows per job: specifies how my rows are retained for each job
  • Maximum job history log size (in rows): specifies how many rows are retained in the history log

2. (Recommended) Remove Agent History, Older than: specifies a cap on how long the SQL Server Agent Job History is retained.

 

For more best practice articles on Symantec Information Centric Analytics see the following posts:

Statistics
0 Favorited
12 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.