Video Screencast Help

CCS Data Collection & SQL 2008 R2 Possible?

Created: 06 Apr 2011 | 11 comments
mchalemja's picture


I am wondering if despite the requirements in the documentation if anyone has used or if it is now supported for the Information Server Database to use SQL 2008 R2.  I also know that SQL 2005 Express comes with the product and is free and is all that is needed, but some customers don't want SQL Express and in client lab setups when all CCS components are on one server it would be nice to use SQL 2008 R2 since that is the latest and the other CCS databases support it.  Thanks.

Comments 11 CommentsJump to latest comment

C Scott Harris's picture

Version 10.5 of Reporting and Analytics, RMS data collector and the ESM (v10) data collector all support Windows 2008, 2008 SP2 and 2008 R2 (32-bit and 64-bit). SQL Server 2008 R2 standard/enterprise/express is supported for RMS.

mchalemja's picture

Thank you Scott.  Is this in documentation somewhere that I missed?

C Scott Harris's picture

See Page 20 of the CCS Installation Guide and the RMS release notes.

mchalemja's picture

On page 20 it states:

Microsoft SQL Server 2008

with Microsoft SQL Server

2005 Backward Compatibility



It does not specifically say SQL 2008 R2 like it does on page 15 for the requirements for the production database server.  This leads me to think that SQL 2008 R2 is not supported for the Information Server.  Is there documentation that specifically states that it is supported or if I call support will they support cases if I tell them that the Information Server is using a local installation of SQL 2008 R2? with 2005 backwards compatibility?  Thanks.

Kevin_K's picture

Correct me if I'm wrong but the SQL server has to be on the same box that RMS is installed on correct?

Scott - if thats the case any possible way they might change that to the same structure that CCS uses?

Kevin_K's picture

Here are some other options for the RMS storage on SQL. Scott would this allow us to use a SQL server on another server for storage of the query results?

Scott would this allow the BVIS to use a SQLserver other than one installed locally or with sql express?

kevin_stultz's picture

The BVIS does require a local database to store configuration information such as ad-hoc query definitions etc.  The query results can be stored on another SQL server as noted in the KB.

ahumphries's picture

We are using MS SQL Server 2008 R2 with CCS v10.0.  Haven't had any problems running bv-Control for Windows (RMS Console) and Reporting and Analytics. 

However, just a few minutes ago I tried to configure the bv-Control for Microsoft SQL Server (MS SQL database auditing feature) for the first time and running "Configure an Audit Data Repository" using the SQL Server 2008 R2 to hold the audit data, I get a message "This feature is supported for SQL Server 2000 and 2005." 

At least for v10.0 for us, BVIS works fine but only for bv-Control for Windows.  Can't use a SQL Server 2008 R2 database server for the bv-Control for Microsoft SQL Server piece.  Will have to look into this more next week.  I had already scheduled a meeting for this coming Monday with the DBA managers to discuss beginning to audit our MS SQL and Oracle databases. 


mchalemja's picture

The following is from a Symantec case I opened to see if they would support SQL 2008 R2 for the local Information Server database, they DO NOT support SQL 2008 R2.

That is correct, as we do not support SQL 2008 R2 for now, may be in the future

nra's picture

In a test environment where all CCS RA and RMS components are installed in one box, can the SQL2005Express co-exist with an SQL2008?

cmccoy2's picture

The SQL instance for the CCS RMS Data Collection components has to be local to the box using the "Default" instance of SQL.    If SQL 2008 is on the box, then you should be able to use it without having to install the SQL2005 Express or SQL 2008 Express as long as it is configured as the "default" instance and not a named instance.  If you already have a named instance of SQL 2008 on the machine, then you would either have to setup the Default instance or reconfigure that named instance to be the default instance for RMS to recognize it.  

Hope that helps.