Knowledge Base
      Back to home
      1. Help Center
      2. DC Project Suite
      3. Knowledge Base

      Eliminating the 4GB StringStore Limit When Processing the Reporting Database

      When processing the Reporting Database in Discovery Center fails, the scheduler log may contain the error message below:

      Error during process reporting database [File system error: A string store or binary store with a compatibility level of '1050' is at the maximum file size of 4 gigabytes. To store additional strings, you can change the StringStoresCompatibilityLevel property of the associated dimension or distinct count measure to '1100' and reprocess.

      This error occurs if the amount of data being processed for a dimension exceeds the limit of a string store inherent in SQL Server Analysis Services versions prior to SQL Server 2012.

      Note: This fix is for Discovery Center release 4.4.1 onward.

      Resolution

      If you are running SQL Server 2008 R2 or earlier, aside from upgrading, the only resolution is to reduce the amount of data being passed to the reporting database.

      In order to eliminate the StringStore limit all together you need to upgrade to at least SQL Server 2012, and follow the steps below:

       

      1. Ensure you know the usernames/passwords used for the Discovery Center Scheduler service and application pool.
      2. Note the Discovery Center SQL Server database name.
      3. Delete the existing Discovery Center reporting database in SQL Server Analysis Services. This has the same name as your Discovery Center SQL database.
      4. Open the attached XMLA file, and search and replace occurrences of ACTIVENAVIGATIONDATABASENAME with your current Discovery Center SQL database name.
      5. If the Analysis Services instance is not co-located with the SQL Server instance, Replace the occurrence of LOCALHOST to match your SQL Server hostname.
      6. If your SQL Server uses a named instance for the Discovery Center Database, replace the occurrence of LOCALHOST from step #5 to match your SQL Server setup: i.e SQLServerHostname\NamedInstance.
      7. If your SQL server uses a fixed port for the Discovery Center Database's instance, include the port into the string from step #4&5. i.e Hostname\InstanceName,12345.
      8. Run SQL Server Management Studio and connect to Analysis Services server, then right-click on the SSAS server in Object Explorer and select 'New Query' -> XMLA.
      9. Paste the updated XMLA text from steps #4-7 into the query window
      10. Execute the query which will create a new database.
      11. Refresh the databases node in Object Explorer to check if it is present.
      12. Expand the database node in Object Explorer to locate the 'Roles' section, where you will find an ANProcessors role.
      13. Add the Discovery Center scheduler service account and the Discovery Center application pool account names into the ANProcessors role.
      14. Open the Data Sources section to locate the ActiveNav4 data source and open the properties dialog.
      15. Find the Impersonation Info setting under Security Settings and set this to use a specific user account. Enter the details for the Discovery Center Scheduler service account.
      16. Process the database using Discovery Center. 

      Once the above steps have been followed you should have a reporting database with 4Gb string store limitations removed, if you have any concerns then please contact Active Navigation support. 

       

      Download