General

When restarting a SQL Server while working with the Navigation tree in Change Director Console, the Create Project operation no longer results in WinException. No support bundle was generated.

CR#0215322

Localization support

Change Director accepts a valid license key.

Description of Problem:

A valid license key is not accepted during first Quest Change Director for SQL Server launch (on machines with other than English language localization).

Compare Projects

An OutOfMemory exception error no longer occurs when trying to compare databases which contain 10,000 or more objects.

CR#0209580

A table's DDL script now displays the extended properties of the table.

CR#0200733

An incorrect synchronization script for creating UDT from CHAR has now been corrected for non-DBO schemas.

Description of Problem:

When creating UDT for a schema which is different from DBO, the length of CHAR data types is indicated as 0, therefore the Char(0) is used regardless of what is in the source database.

CR#0214984

It is no longer possible to create a view without table.

Description of Problem:

If you choose a view, both views and tables will be synchronized.

CR#0215690

For CLR User-Defined Datatypes, extended properties were displayed in the tree, but not in DDL script. These properties are now present in synchronization script.

CR#0215751

Synchronization of Extended Properties.

If you choose to synchronize a User-Defined Aggregate with non equal status, the aggregate function is no longer created twice.

CR#0215756

Synchronization of Extended Properties.

Extended properties for User-Defined Functions are now synchronized, including their display in the browser tree.

CR#0215763

Same tables are no longer being displayed as different when the "Ignore Constraint Names" option is selected.

Description of Problem:

If you set Change Director to ignore constraint names, equal keys are not compared and not equal keys are set as added and deleted. In this case, mapping for the keys is not used.

CR#0216112

The Dependent User-Defined Functions' for CHECK constraints are now included in synchronization scripts.

CR#0199908

The Extended properties for Tables are now synchronized, as well as being displayed in the tree.

CR#0213035

The Comparison script for CREATE TABLE, where one or more columns have a DEFAULT value, is generated correctly now.

Description of Problem:

The Comparison script for tables where one or more columns have a DEFAULT value is generated incorrectly.

ST#41028

Impact Analysis

The Impact Analysis report now includes information on the impact of CLR functions.

Description of Problem:

Functions used in CHECK constraints are not recognized when creating dependencies, therefore a CHECK function may be deleted prior to the CHECK constraint. (See CR#0214184)

CR#0212042

General

Change Tracker's monitoring is no longer limited to only monitoring user (non-system) databases.

CR#0217957

When installing Change Tracker Agent on a SQL Server using (localhost) as a server name, Change Tracker no longer registers 2 servers within the Console: (localhost) and a server with the real server name.

CR#0204875

The Call of the sp_addapprole stored procedure now appears in real-time alerts.

CR#0172561

[create APPLICATION ROLE] and [alter APPLICATION ROLE] now appear in real-time

alerts.

CR#0178249

Real-time alerts now display names of objects where they were incorrectly displaying the name of variables instead.

CR#0182400

It is now impossible to configure or re-configure the monitoring of SQL Server instances

which are registered within the Change Tracker window by IP address.

CR#0204898

ST#35548

Change Tracker Agent

Agent can be installed normally on 64-bit server and workstation.

Note: Vista 64-bit is not supported for remote agent deploy.

ST#33854

CR#0170598

Change Tracker Reports

The message  "Database is already open and can only have one user at time" now appears when monitoring has stopped while the database is not online.

CR#0171520

"Alter database restores xml_sch1" command now appeared in real-time alerts.

CR#0178002

ST#34616

More details are now provided for the Operation Type in Alert Reports. For example, the Create, Alter, or Drop operation is now displayed where it used to say "Unknown" operation type.

CR#0216140

General

Log Reader now supports 64-bit based SQL Servers.

CR#0206477

When reading big log files (more than 100GB), you will not no longer receive the OutOfMemory exception error message.

Log Reader issue with reading backups - resolved.

General  

It is not possible to preserve the license key when installing over the v1.x (1.2

and 1.5). A bug in the 1.x uninstaller removes licensing information. In addition,

you cannot see the existing key on the v1.x installation. You will need access to

the license key in order to run the v2.0.

SQL Server 2008 is not supported.

Register SQL Server: It is possible to add two identical servers. You can add a server using either its IP address or its hostname, therefore there may be duplication of registered servers when you mix these two options. It is possible to duplicate an already registered server by registering it using another type of identification.

CR#0175518

An exception error occurs when trying to view a database schema which contain 10,000 or more objects.

CR#0210616 (ST#34977)

Sometimes the error message, "A required privilege is not held by the client. Please contact your system administrator" displays when you try to create a Scheduled Deployment task on Windows 2000.

Workaround:

1. From the Start menu, run Control Panel.

2. Choose Administrative Tools.

3. Run Local Security Policy.

4. In the navigation pane, expand the Local Policies node and select User Rights Assignment.

5. Double-click the Act as part of the operating system policy in the Policy list.

6. In the Properties window, click Add User or group, add your system account, and click OK.

7. Exit from the Local Security Policy tool.

8. Log off from the system and log in again.

ST#34470

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

You cannot save the Options for the logging level when running on Windows Vista.

Workaround:

Run the regedit.exe tool and change the registry value:

[HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Quest Change Director for SQL Server\Console]

"Log"=dword:00000003

ST#41620

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, or Windows 2000 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

A Windows task becomes invalid after it is renamed.

Workaround:

1. After renaming, open the task.

2. Edit anything in the task.

3. Click OK.

4. Enter credentials for the task to use.

ST#33856

Compare Projects

Sometimes for triggers, stored procedures, or functions when there is a difference between the two objects being compare, Change Director displays the scripts as equal.

CR#0214451 (ST#35075)

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)

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)

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 middle tier is installed.

ST#41928

The error message, "Unable to resolve column level collations" may occurred 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

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)

Snapshot Viewer

Sometimes an exception occurs when closing Snapshot Viewer. The error may be caused by diagram drawing.

CR#0210890 (ST#34980)

Middle Tier

Middle tier configuration

The Middle tier is starting under Local System account by default.

If one of the source, target, or repository connections is using Windows authentication and the tasks are starting across the middle tier, then the connections to source, target, and repository are created under Windows account which was used to start the Change Director Middle tier (Local System by default).

Workaround:

The account can be changed in Windows snap-in Services.

Middle tier uninstall

Middle tier can only be un-installed manually.

Middle tier use

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

Description:

When the Middle tier 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 Middle tier to Vista is not supported

ST#41987

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.

Online Help

Scripting Command Line Interface Commands

The command in the description of the schedule Change Director CLI script procedure is incorrect. To schedule a script execution in the Run field of the scheduled task properties, enter the following command:

"%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe"  -PSConsoleFile ChangeDirectorSnapIn.psc1 -Command ". script.ps1"

where:

• %SystemRoot% is an environment variable with the path to your system root directory (usually, C:\WINDOWS)

• ChangeDirectorSnapIn.psc1 is a full path to a previously saved PowerShell console configuration file

• script.ps1 is the full path to a script file.