Support for SQL Server 2005 with Enterprise Vault (EV) products.

Article:TECH45819  |  Created: 2006-01-04  |  Updated: 2011-09-06  |  Article URL http://www.symantec.com/docs/TECH45819
Article Type
Technical Solution

Product(s)

Environment

Issue



Support for SQL Server 2005 with Enterprise Vault (EV) products.


Solution



Symantec is pleased to announce the support of Microsoft SQL Server 2005 with EV products.

EV products will run with databases stored on Microsoft SQL Server 2005 for the following versions:
 
  • EV for Microsoft Exchange 6.0 SP1 or later SP, 7.0 (all versions), 2007 (all versions), and 8.0 (all versions)
  • EV File System Archiving 6.0 SP1 or later SP, 7.0 (all versions), 2007 (all versions), and 8.0 (all versions)
  • EV for Microsoft Sharepoint 6.0 SP1 or later SP, 7.0 (all versions), 2007 (all versions), and 8.0 (all versions)
  • EV SMTP Archiving 6.0 SP1 or later SP, 7.0 (all versions), 2007 (all versions), and 8.0 (all versions)
  • EV for Lotus Domino 6.0 SP1 or later SP, 7.0 (all versions), 2007 (all versions), and 8.0 (all versions)
  • EV Compliance Accelerator 6.0 SP1 or later SP, 7.0 (all versions), and 2007 (all versions)
  • EV Discovery Accelerator 6.0 SP1 or later SP, 7.0 (all versions), and 2007 (all versions)

EV products requiring Microsoft SQL Server 2005  SP2 or later installed (both x86 and x64 editions of SQL Server 2005 SP3 or greater are supported):
NOTE: For Compliance and Discovery Accelerator products, it is recommeneded to install SQL Server 2005 SP3 to resolve issues when printing reports
  • EV for Microsoft Exchange 9.0 (all versions)
  • EV for File System Archiving 9.0 (all versions)
  • EV for Microsoft SharePoint 9.0 (all versions)
  • EV SMTP Archiving 9.0 (all versions)
  • EV for Lotus Domino 9.0 (all versions)
  • EV Compliance Accelerator 8.0 (all versions), 9.0 (all versions) and 10.0 (all versions)
  • EV Discovery Accelerator 8.0 (all versions), 9.0 (all versions) and 10.0 (all versiions)


EV products requiring Microsoft SQL Server 2005  SP3 or later installed (both x86 and x64 editions of SQL Server 2005 SP3 or greater are supported): 

  • EV for Microsoft Exchange 10.0 (all versions)
  • EV for File System Archiving 10.0 (all versions)
  • EV for Microsoft SharePoint 10.0 (all versions)
  • EV SMTP Archiving 10.0 (all versions)
  • EV for Lotus Domino 10.0 (all versions)

For a listing of all supported SQL Server versions that can be used with Enterprise Vault, please refer to the Compatibility Listing under the Related Arcticles at the end of this document

Symantec has identified the following issues when running Microsoft SQL 2005:
 

Issue #1

Customers upgrading from SQL 2000 to SQL 2005 are likely to observe an increase in CPU usage on the SQL Server when EV is running. In extreme cases, this CPU usage will severely impact the performance of that SQL server, and therefore the overall performance of EV.

Symantec recommends running the following two SQL commands against ALL EV, Compliance and Discovery databases, once the SQL version is upgraded to SQL 2005:

1. Rebuild all indexes once after migrating to 2005. Command:
 
Exec sp_MSForEachtable 'ALTER INDEX ALL ON ? REBUILD;'
 
GO
 

2. Run UPDATE STATISTICS with full scan to eliminate out of date statistics. Command:

 
Exec sp_MSForEachtable 'UPDATE STATISTICS ? WITH FULLSCAN'
 
GO
 

These commands are documented in the section "Best Practices for Managing Statistics" in the following Microsoft Knowledge Base article:  http://www.microsoft.com/technet/prodtechnol/sql/2005/qrystats.mspx


Note: For large databases, this command can take some time to complete. On a Vault Store database with 50 million archived items, rebuilding indexes can take in excess of two hours on an average enterprise-size server (two processors, 4 Gb memory).


Issue #2 

The 2nd issue affects ONLY customers who are using the database maintenance plan in SQL Server 2005 WHO HAVE NOT INSTALLED SQL SERVER 2005 SP1 to rebuild indexes::
 
The Index Rebuild maintenance task, if included, has an option called Change free space per page percentage to. If this is set, the percentage figure is wrongly interpreted as the Fill Factor.
 
For example: A Change free space per page percentage to figure of 10% should set the Fill Factor to 90%; however, it actually sets it to 10%. This is equivalent to setting the free space per page to 90%. This will increase the size of the database and may lead to disk space problems.
 
The T-SQL script generated for the rebuild index task shows the fill factor as 10% instead of 90%. It is advisable to check the SQL generated by the maintenance task by editing and clicking in the View T_SQL button. Inspect the Fill Factor to see whether it has the required value. Alternatively verify by querying the sys.indexes table after the rebuild index job has run.
 
In order to resolve this issue, customers are recommended to upgrade SQL 2005 to Service Pack 1.



Legacy ID



281261


Article URL http://www.symantec.com/docs/TECH45819


Terms of use for this information are found in Legal Notices