General  

If you installed the SQL Server you want to monitor, the Change Director Console and the Change Tracker agent locally, on the computer running Windows Vista (or Windows 7) with enabled UAC, you must run the Change Director Console as Administrator.

ST#44838

If a SQL server is registered in the tree several times, Change Director does not work correctly with these registrations.

ST#43823

Some domain configurations use IP address only to connect to the server, that can cause a network-related or instance-specific error when registering a SQL Server within Change Director.

Workaround:

1. Run the following command on the server:

select SERVERPROPERTY('InstanceName')

2. Copy results.

3. On the computer where Change Director is installed, open C:\WINDOWS\system32\drivers\etc\hosts in Notepad and add a new line with IP address and instance name:

#       [IP address]     [instance name]

ST#43867

If you drop a user-defined function that uses a trigger, the trigger and its table are also dropped.

ST#35086

Deployment fails if a target database contains DDL triggers.

Workaround:

Disable DDL triggers manually before deployment.

ST#35093

The Console does not work on Vista 64-bit if the SQL Server Management Studio is started and connected to the same server.

Workaround:

Close the SQL Server Management Studio connection and then start the Change Director console.

ST#41429

Change Director does not support databases with compatibility level less than 8.0.

Installer

An error appears if there is no free disk space available.

CR#0174359

Windows Tasks

By default, Windows tasks on remote Vista computers cannot be managed from Windows Server 2003 Windows XP computers.

Workaround:

1. Add your account to the Administrators group on the remote Windows Vista computer.

2. If Windows Firewall is enabled:

1. From the Start menu, select Control Panel.

2. Click Switch to Classic View.

3. Double-click Windows Firewall.

4. On the Exceptions tab, select File and Printer Sharing.

3. To enable the "Remote Registry" service, open a Command Prompt and run the following command:

net start "Remote Registry"

ST#34442

Compare Projects

Roles with different owners are identified as equal. The script generated by Change Director does not take into account the role's owners.

CR#0200887 (ST#34888)

Database role owners are not compared if SQL Server 2000 objects are selected as target.

ST#43858

Different types of Roles are not identified.

CR#0200889 (ST#34889)

Stored procedures with the FOR REPLICATION option are deployed incorrectly.

CR#0191048 (ST#34820)

An incorrect script is generated for a table with a computed column with the PERSISTED and NOT NULL options.

Description:

For SQL Server 2005, Change Director does not read the PERSISTED and NULL/NOT NULL Computed Columns options. These options are, therefore, not synchronized.

CR#0214053 (ST#35064)

After synchronization of equal databases, DDL Triggers may have different Ansi Nulls and Quoted Identifier options.

CR#0214317 (ST#35073)

Assemblies created from similar DDLs are recognized as different if they have different names.

CR#0217155 (ST#35124)

The 'The MUST_CHANGE option is not supported by this version of Microsoft Windows' error occurs on the target machine running Windows XP (SP3), when you try to deploy a project with option "Generate empty logins ...".

ST#44279

Schedule deploy step: Currently, the Console user credentials are used to create scheduled deployment windows task. The User must have rights to create a Windows task on the server where the middleware is installed.

ST#41928

The error message, "Unable to resolve column level collations" may occur during BCP backup.

Description:

The BCP error occurs if the operating system code page or the code page that is specified in the BCP statement is not one of the following: 437, 850, 874, 932, 934, 936, 949, 950, 1250-1258.

The explanation and workaround are described here:

http://support.microsoft.com/kb/867677/en-us

ST#41798

Deployment fails with the error message, "Windows NT user or group <UserName> not found. Check the name again" if the Windows user (objects’ owner on source server) does not exist on target server.

ST#41977

A Support Bundle exception error occurs when a Primary Key in a source database has the same name as a Unique Key in a target database.

ST#35546

Change Director connects to the first server in tree when the New Project dialog is opened. The first server should be accessible and run.

ST#42768

Exception can occur during multi-deploy in the Custom Script project, if the object that is to be created already exists in the primary database.

Workaround:

Click Ignore.

ST#42795

Fill factor values 0 and 100 are recognized as equal. For more information, see

http://msdn.microsoft.com/en-us/library/ms177459.aspx

ST#43541

Change Director considers a USER and APPLICATION ROLE with the same name to be the same objects and replaces one with another during deployment.

ST#43464

Change Director shows FOR triggers as AFTER triggers, because SQL Server considers FOR and AFTER DML triggers in OBJECTPROPERTY function to be AFTER triggers.

ST#43224

Rollback

An incorrect rollback script is generated for tables with dependent functions.

Description:

Change Director does not check CHECK constraints text for dependent  objects.

CR#0214184 (ST#35375)

An Incorrect rollback script is generated when there is CHECK function.

Description:

Functions used in CHECK constraints are not recognized when creating dependencies, therefore a CHECK function may be deleted prior to the CHECK constraint.

CR#0214184 (ST#35375)

Impact Analysis

An incorrect message is displayed for syntax error on the DROP TRIGGER operation.

Description:

When using a single-part name in a DROP Trigger statement, a syntax error is detected in the Impact Analysis report.

CR#0214209 (ST#35070)

Middleware

Middleware startup account

The middleware starts under the startup account  specified during the Middleware installation.

It is recommended that this account is a Windows domain user account that can connect to the Repository, Source and Target servers and can log on as a Service (Start | Control Panel | Administrative Tools | Services).

Middleware use

Compare Changes: Exception errors occur when the connection to the middleware is lost.

Description:

When the Middleware is restarted while a comparison project is opened, an exception error may occur in the Console.

ST#42131

Remote Installation

The remote installation of the Middleware to Vista is not supported.

ST#41987

The Middleware installation wizard is not cluster-aware. The middleware service and the notification engine do not work on a cluster computer.

Notification engine

Notification engine uninstall

You have to remove the remaining QuestChangeTrackerNotificationService Windows task manually.

ST#43801

Change Director command-line interface

Differences in comparison with default options

When using the command line interface to generate a synchronization script to compare databases, the "Script NOT NULL with constraint" option is cleared. In Change Director console, this option is selected be default.

The Remote Agent Installation may fail to install Change Tracker agent.

Workaround:

1. Copy the ChangeTracker.msi from the Change Director installation directory to the remote host where you want to install the agent.

2. Run the installation package and follow the prompts.

CR#0215285

Manual Agent installation: When installing a Change Tracker agent on a host where two or more SQL Server instances reside, you may receive the following error if some of the instances use the same port:

10/23/06 19:37:05 Initialize: Start

10/23/06 19:37:05 Initialize: End

10/23/06 19:37:05 Install to instances: Start

10/23/06 19:37:05 'Add' mode

10/23/06 19:37:05 Install to instance [instance_name]: Start

10/23/06 19:37:05 Load database scripts

10/23/06 19:37:06 SQL Server 2000 utilities found

10/23/06 19:37:06 Check database Change Tracker

10/23/06 19:37:15 Check of database failed

10/23/06 19:37:15 Execution of isql failed with exit code: 1. Error: . Output: DB-Library: Unable to connect: SQL Server is unavailable or does not exist.  Unable to connect: SQL Server does not exist or network access denied.

Net-Library error 2: ConnectionOpen (Connect()).

10/23/06 19:37:15 Install to instance [instance_name]: Failed

10/23/06 19:37:15 Install to instances: Failed

Workaround:

Configure SQL Server instances to use different ports and reinstall the Change Tracker agent.

Detected cluster nodes are shown as standby nodes during remote agent installation to SQL Server 2000 Cluster. After installation agent status doesn't show nodes list. However the agent is installed correctly and started on active node automatically.

The Change Tracker agent cannot be deployed remotely on Windows Vista machine due to Vista security restrictions.

Workaround:

Install Change Tracker agent manually. See Change Tracker Agent Installation on Clustered Servers.pdf.

ST#33851

Change Tracker Agent

Log file growth

When installed, the Change Tracker agent writes information on Change Tracker Trace starts/stops to the SQL log and Windows event log. This may result in a large number of messages being sent to the log files. To prevent this situation, disable the 19030 and 19031 sys messages. To disable sys messages in SQL Server 2005, follow the steps below.

Workaround for SQL Server 2005:

1. Install Hotfix Q922578 (b2153) from the Microsoft web site.

Note: You will need to restart the computer if:

• SQL Server 2005 Analysis Services are running as a named instance and you stopped the SQL Server Browser service before applying this hotfix.

• You exited all Analysis Services tools and all client applications before applying this hotfix.

• You exited Microsoft Internet Information Services (IIS) before applying this hotfix.

2. After the hotfix installation, stop SQL Server and restart it with new flag: /T3688

For example:  net start "SQL Server (INSTANCE1)" /T3688

3. Ensure that the SQL Server was started with the correct flags:

DBCC TRACESTATUS (3688)

go

Check that Status and Global equals 1.

Trace start/stop messages will not be logged in the SQL Server error log or the Windows Event log.

SC 485813-1

Changes in server parameters applied through the master..xp_instance_regwrite stored procedure do not appear in real-time alerts.

For example: Login audit level, log & data files path

CR#0172259

Sometimes the [application] does not appear in real-time alerts.

CR#0178088

An exception error occurs if virtual memory is very low.

CR#0176835

The Change Tracker agent may stop work normally if monitored server or repository server have insufficient resources.

ST#42081

Backup is missing as an individual option and as a filter parameter (Object Type). Server Databases (that includes Backup as a sub option) is used instead.

The Change Tracker agent does not stop when SQL Server stops.

CR#0192319

Change Tracker Window

Error "RPC server is unavailable" occurs, if native names are forbidden to use when connecting to cluster instances.

ST#44427

When the monitored database is renamed, Change Tracker will continue to monitor it, but the results will be not be visible at the Console and therefore the monitoring for this database cannot not be stopped at the Console.

Workaround:

There are two workarounds:

1) Run the following script on the Change Director repository:

declare @Server nvarchar(255)

declare @OldDBName nvarchar(255)

declare @NewDBName nvarchar(255)

set @Server = '<Server>'      -- Server name with renamed database

set @OldDBName = '<Old_DB_Name>'          -- Old database name

set @NewDBName = '<New_DB_Name>'        -- New database name

UPDATE

[<RepositoryName>].dbo.SW_SQLDatabase

SET

SW_SQLDatabase.DatabaseName = @NewDBName

FROM [<RepositoryName>].dbo.SW_SQLDatabase db

inner join [<RepositoryName>].dbo.SW_Servers srv ON srv.ServerId = db.serverID

WHERE

db.DataBaseName=@OldDBName

AND srv.InstanceName = @Server

where <RepositoryName> is the name of Change Director repository database

or

2) Change name of monitored database directly at the Change Director repository at table SW_SQLDatabase using any SQL query tool.

ST#34745,

ST#41666

Failed operations and rolled-back transactions are displayed in reports.

CR#0170115

Once you have started the installation or uninstall of the Change Tracker Agent using the Console, you cannot stop the process. If you click Cancel when installing or uninstalling Change Tracker Agent using the Console, Change Tracker closes the dialog window, but continues the operation.

CR#0194895

There is no script for encrypted functions or stored procedures in real-time alerts.

Note: This is done for security reasons.

CR#0178100

After refreshing the work area on an instance level node, Change Tracker always displays the Overview tab regardless of which tab was chosen before refreshing.

CR#0191823

In NetSend notifications on Failed Logins, international characters are displayed incorrectly.

CR#0195809

Sometimes, the agent stop responding and you will find 'COM exceptions' in the logs.

Note: Agents have an auto recovery capability that allows then to get back to work normally after COM objects failure.

ST#41988

Change Tracker doesn't take into account Daylight Saving Time, only the native GMT time is shown.

ST#34798

The collation for the SQL Server Instance and the Repository and must be the same.

ST#44548,

ST#44564

The number of alerts on the overview graph may differ from the number of alerts in the server and databases boxes.

Workaround:

In the Change Tracker window, put cursor anywhere in the Server tree and hit F5 to refresh statistics.

ST#44713

The Change Tracker window displays incorrectly on 64-bit machine after resizing of the main Change Director window.

ST#33860

Log files list is empty on Windows Vista and Windows 7 with enabled UAC.

ST#44805

Group-wide monitoring settings are not applied to new servers and groups added after you set group monitoring.

ST#44731

General

When using the Find feature, Log Reader only searches through record values.

CR#0208685

Log Reader does not support Find feature for BLOB values.

CR#0208686

Server Components installation

Sometimes when installing the Log Reader Server Components to a remote host, a "Write to file failed" error occurs.

Workaround:

1. Locate xp_QuestLogReader.dll on the host where the application is installed.

2. Copy xp_QuestLogReader.dll to the \BIN folder of the SQL Server instance where you want to install the Log Reader Server Components

Tip: You can use the EXEC xp_instance_regread N'HKEY_LOCAL_MACHINE', N'SOFTWARE\Microsoft\MSSQLServer\Setup', N'SQLPath' command to define your server location.

3. Run the following commands on the SQL Server instance:

EXEC sp_addextendedproc 'xp_qlr_version', 'xp_QuestLogReader.dll'

EXEC sp_addextendedproc 'xp_qlr_logfile', 'xp_QuestLogReader.dll'

EXEC sp_addextendedproc 'xp_qlr_loginfo', 'xp_QuestLogReader.dll'

EXEC sp_addextendedproc 'xp_qlr_logread', 'xp_QuestLogReader.dll'

CR#0216499

Script Generation

CONTENT option for XML columns is not supported.

CR#0202184

FILEGROUP and TEXTIMAGE_ON options are not supported (the script is not generated for the FILEGROUP and TEXTIMAGE_ON).

For SQL Server 2005, the partition scheme is also not supported.

CR#0202183

INSERT, UPDATE, or DROP commands for columns with BLOB values of 8000 bytes or more are detected, but a script is not generated.

CR#0202363

When you use the "check log file changes" option, the Log Reader may reconstruct newly read log records incorrectly.

Workaround:

Click Refresh on the toolbar or use the Read Log wizard.

CR#0208688

Windows Tasks

Job Manager creates a new task when you close the New Task dialogue window.

ST#43672

General

Under certain circumstances, Job Management does not display existing appointments.

Description:

Job Management does not display existing appointments if you are viewing the List tab on the Job Management window and doing the following:

1. Adding a server to view scheduled tasks and jobs.

2. Choosing a highlighted date (a date when there are scheduled tasks or jobs) on the Calendar tool.

3. Choosing the Calendar tab on the Job Management window.

Workaround:

Switch to the Calendar tab on the Job Management window before adding a server.

ST#36277