Collect Data

Deadlock problem

If you ran several collect data jobs at the same time, the following error occurred: "Transaction was deadlocked on lock resources with another process and has been chosen as the deadlock victim".

ST#42089

Vista Support

Licensing

If you updated the default license (30 days) with a new license by selecting Help | Registration from the Console menu, Capacity Manager updated the license for the user running the Console only. For other users, the default license was used.

ST#33316

Relocate Objects Wizard

Relocate Objects failed if you relocated a clustered index with FOREIGN KEY references. Now, the Relocate Objects Wizard supports relocation of objects with FOREIGN KEY references

CR#0176674 / ST#34006

Performance Capacity

Data collection

Performance data is no longer collected by the Collect Data job because Performance Capacity charts are based on Spotlight repository historical data if the Spotlight repository is configured.

Status calculation

Performance data is no longer used for the status calculation.

Forecast algorithm

For Performance Capacity charts only, the "Time Series" forecast algorithm is used.

Upgrade

Upgrade from 2.5 beta to 2.5.1

After upgrading from the 2.5 beta to Capacity Manager 2.5.1, you should recreate the usp_questcapacitymanager stored procedure on all monitored instances to avoid deadlock problems.

Instructions:

1. Open the Collect Data Wizard

2. Clear all check-boxes in the Capacity Data step.

3. Complete the wizard.

4. Open the Collect Data Wizard again.

5. Select the objects you want to monitor.

Old Collect Data jobs

After upgrade, collect data jobs of v2.0 are not deleted. You have to delete them manually.

ST#41938

ST#42132

Capacity Planner

Time Series in Consolidation Summary report

If there are a lot of databases that are consolidated and Time Series is used as a forecast algorithm, the Consolidation Summary report may take a long time to load.

ST#41911

Forecasting

Time Series algorithm

If you use the Time Series forecast algorithm but there are a few collected data, forecasting charts may show invalid forecasts.

ST#41991

64-bit Platforms Support

Creation of a collect data job fails for x64 SQL Server instances

If the repository is installed on a x32 SQL Server 2000 instance, the creation of a collect data job fails for x64 SQL Server instances with the following exception message: "OLE DB provider 'SQLOLEDB' reported an error.

[OLE/DB provider returned message: Unspecified error] [OLE/DB provider returned message: The stored procedure required to complete this operation could not be found on the server (they were supplied with the ODBC setup disk for the SQL Server driver).  Please contact your system administrator.] OLE DB error trace [OLE/DB Provider 'SQLOLEDB' IDBSchemaRowset::GetRowset returned 0x80004005"

Workaround:

1. Download the instcat.sql script from the Microsoft support site.

2. Execute this script on the SQL Server instance where the repository resides.

SC#516198-1

Limited support of SQL Server Aliases

When you define a SQL Server for the Capacity Manager Repository with the Create/Select Repository Wizard, you can use either the name of the SQL Server or its alias. If you use an alias, you must also configure all monitored instances to use the same alias for the SQL Server instance where the repository resides.

Otherwise, the Collect Data wizard fails with an error that the SQL Server does not exist or access was denied.

Log file growth when upgrading the repository

During the repository update, Capacity Manager intensively changes the repository structure, which may result in considerable growth of the log file. (In some cases the size of the log file may exceed five times the size of the repository database.)

Workaround:

• Truncate and shrink the repository database log file.

• Prepare a full database and log backup.

• Launch Capacity Manager and start the repository upgrade.

Non-standard port configuration

Capacity Manager does not use the default TCP/IP port, which is configured for a monitored SQL Server instance in the Microsoft Network Utility.

Workaround:

When registering a SQL Server instance in the Console, click Advanced on the Connect to SQL Server dialog to set a custom TCP port to use.

ST#41024

SQL Server Agent stop is not detected

Capacity Manager cannot detect when a SQL Server Agent stops if the Agent XPs option for the SQL Server 2005 is disabled.

Workaround:

To enable the Agent XPs option, run the following SQL script:

sp_configure 'show advanced options', 1;

GO

RECONFIGURE;

GO

sp_configure 'Agent XPs', 1;

GO

RECONFIGURE

GO

See the Microsoft documentation at:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2e1c6c64-5ce7-4357-98c7-ac7763a9f9de.htm for details.

ST#32092

Status Calculation

Capacity Manager calculates statuses from capacity, fragmentation, and performance data on monitored instances and databases. If you collect capacity information for databases only and do not collect capacity information on instances, Capacity Manager does not take into account capacity threshold settings when calculating statuses. You need to collect capacity information at the instance level to include capacity thresholds settings in the status calculation process.

Job Schedule

Job schedule is an object in SQL Server. It has the Enabled property. The console does not check or change the Enabled status for the Job schedule. If it is disabled manually in Management Studio, the Collect Data job does not execute.

Collations

There are different collations on monitored instances and the repository instance. There are some problems with a SQL Server OPENDATASOURCE connection from SQL Server 2000 with European collations to SQL Server 2005 with Asian and Arabian collations (i.e., Azeri_Latin_90_CI_AS, Chinese_Hong_Kong_Stroke_90_CS_AS).

The error is:

The OLE DB provider 'SQLOLEDB' provided invalid collation. LCID = 0x2c040000, Compflags= 0x01000300, SortId = 0x0.

OLE DB error trace [Non-interface error: OLE DB provider provided invalid collation:LCID =0x2c040000, Compflags = 0x01000300, SortId = 0x0, fLuxor = TRUE.]

Workaround:

Use two SQL Server 2005 servers in this case. This error occurs only when you connect from SQL Server 2000 to SQL Server 2005.

Permissions

To view Database reports, you must have at least db_owner rights. But to view information about a particular object in the database, you may have just db_reader rights. To view Instance reports, you must have 'sa' rights.

Migrate Data from Legacy Repository Wizard

Capacity Manager cannot migrate data collection plans for objects.

If data collection is configured at the object level only and there are no data collection plans at the database or server level for these objects, Capacity Manager does not migrate the data collection plans for the objects.

Relocate Objects Wizard

You need sa rights on the server to run the Relocate Objects wizard.

Relocation of LOB data is not supported.

Forecasting with QPredictor

Forecasting with QPredictor is not supported when the snapshot time delta (time period between snapshots) is less than one minute.

Offline operation mode

In Offline mode, the console does not support local servers registered with short names like: <local\inst1> or <.\inst1>.

CR#0190886

Empty databases without objects could have different used log size

DBCC SQLPERF (LOGSPACE) is used in the collect data process. DBCC SQLPERF (LOGSPACE) for empty databases returns different values for the used log size. There is no information available from Microsoft regarding this issue.

Send Report

Collaboration Data Objects for the Windows 2000 (CDOSYS) message component is required for sending email.

Read more about CDO object

CDOSYS was first available in the Windows 2000 Server. As of December 2003, CDOSYS is an integral part of the Windows 2000, Windows XP, and Windows 2003 operating systems.

• SendReport does not support local servers registered with short names like: <local\inst1> or <.\inst1>.

• The Time Series forecasting algorithm is not supported for Send Report. The Linear algorithm is used instead.

• If you do not have reports to send (excluding the Server Group Report) and you follow a user who has object reports in the Report Schedule Options list, you get all the reports selected for the previous user.
   

Workaround:

Add any object report to your account or put your name in the Recipients List in Report Schedule Options.

CR#0180890

Send Report

Capacity Manager does not update the qcm_SendReportTask Windows task automatically. You need to delete and re-create the task manually using the Report Schedule tool (Tools | Report Schedule, Schedule tab)

ROI Calculator

If the database size is decreasing, the forecast for the next 6 months can be equal or less than zero.

If the forecasted database size is less than the current database space used size, the recommended size is set to the current database space used value of +10%.

Object Search

Capacity Manager does not display imported instances in the Search Criteria window of the Find Objects tool.

ST#40904

Database Mail

Database Mail notification is not supported for the following wizards:

• Create Partitioned Table

• Create Partitioned Index

• Alter Partitioned Table

• Alter Partitioned Index

• Make Table Unpartitioned

• Make Index Unpartitioned

ST#33722, 33640

Manage Capacity

Database Capacity | Database Overview box

Growth values are always calculated by the Minimum Squares rule using all snapshots loaded into the console. The calculation does not depend on Option settings.

Server Capacity | Instance Overview and Databases Capacity

Growth values are always calculated by the Minimum Squares rule using all snapshots loaded into the console. The calculation does not depend on Option settings.

Shrink Databases Wizard

Not all the instances' databases are in the list. The reason is that the DBCC SQLPERF (LOGSPACE) command does not return data about empty databases (without data).

CR#0176924

Database Profiles

Capacity Manager cannot view a database profile if the database contains objects with identical names but different owners.

ST#40828

Manage Fragmentation

Database Map: Scan Density and Fragmentation Maps

Database Map does not support the correct representation for objects with the same name located in different schemas.

Empty Database Fragmentation

Fragmentation charts for an empty database (without user objects) are always empty and fragmentation snapshots display a Fail state. This is a result of executing the DBCC SHOWCONTIG command.

Fragmentation snapshots are not collected for empty (without data) Indexes and Tables.

At the Console, an error stating that all fragmentation charts for those objects are empty and you need at least 2 snapshots displays if indexes and tables do not contain data.

CR#0164687

Intelligent Defragmentation

Capacity Manager uses the instances and databases which you select for automatic defragmentation to limit the number of objects you can select manually.

Capacity Manager analyzes and reorganizes only those objects for which there are snapshots in the repository.

Manage Partitions

Create Partitioned Index wizard

When you select a column with an improper type for the partition key, the Next button is disabled but no message displays.

Create Partitioned Index wizard

Only unpartitioned objects display in the tree on the Alignment step.

Sliding Windows Scenario and Switch Partition wizards

If a table contains a column with 'character' in its name and you create a new table, an error message displays after script generation and you cannot proceed through the wizard.

Non-partitioned tables

A switch operation from a non-partitioned to a partitioned table is not supported.

SQL Server 2005 - partition non-partitioned tables

In SQL Server 2005, any non-partitioned table is considered a partitioned table with a single partition. Capacity Manager collects information for this single partition. If you split the table, SQL Server 2005 considers new partitions unrelated to the initial partitions. Capacity Manager considers one of the new partitions as an initial partition. Partition Disk Capacity and Partition Fragmentation reports for one of the new partitions display information for the initial partition.

Workaround:

Create a new snapshot of the partitioned table to update information in the repository. Manage Partitions displays the correct reports for the new partitions.

ST#31860

SQL Server 2005 - re-partition a table

If data collection appears before and after re-partitioning of a table, information in Partitions Disk Capacity and Partitions Fragmentation reports refers to the previous partitions. For example, if you collect data about a partitioned table, unpartition the table and create new partitions, Manage Partitions considers the new partitions to be similar to the original partitions.

Workaround:

Create a new snapshot of the partitioned table to update information in the repository. Manage Partitions displays the correct reports for the new partitions.

ST#34476

Manage SharePoint Capacity

Delete SharePoint registration

Deleting the SharePoint registration from the tree view does not delete data about SharePoint from the repository.

ST#37688

Monitored Server

Change servers computer name

When you change the computer name, you also have to rename the instance.

If you are running SQL Server 7.0, after renaming the SQL Server machine, the SQL Server service fails to start with the following error message "Your installation was corrupted or has been tampered with.

Workaround:

Re-run the SQL Server set up. After upgrading, the necessary SQL Server registry entries are reset with the new computer name and you can start the SQL Server. After restarting, use Toad or Query Analyzer to run the following commands:

EXEC sp_dropserver 'Your_OLD_Computer_Name'

GO

EXEC sp_addserver 'Your_NEW_Computer_Name', 'local'

GO

Restart your SQL Server service. Connect using Toad or Query Analyzer and run the following command (it should output the new server name):

SELECT @@SERVERNAME

GO

If you are running SQL Server 2000, the new name is recognized the next time SQL Server service starts. You do not have to re-run the setup. However, you have to run the sp_dropserver and sp_addserver stored procedure as shown above.

Manage Jobs

The Console stops responding if you try to load an old job with a large job history.

For example, the Console stops responding if you try to view the jobs for an instance when one of the jobs was created more than a year ago and is executed on an hourly basis.

ST#40926

Jobs

Jobs fail to start

SQL Server Agent jobs have an owner field. If the owner account does not have rights to log into SQL Server, all jobs created by the owner fail to start.

Possible use case:

The system administrator with account DOMAIN1\User1 was created to run collect data jobs at several monitored SQL Server instances. After some period of time, the owner left the company and the system administrator disabled the DOMAIN1\User1 account. After the first restart of SQL Server instances, all jobs created by the that administrator fail to start. In this case, the jobs owner account should be changed to another account which has access to SQL Server.