If you uninstall the standalone version of SQL Optimizer with Toad for SQL Server and SQL Optimizer installed, you can no longer launch SQL Optimizer by sending SQL statements from Toad for SQL Server to SQL Optimizer.

ST77615

When you launch SQL Optimizer from Windows 2000, you may get an error message, "Quest.Tuning.SQLSvr.Main has encountered a problem and needs to close."

Workaround:

Download and install MSXML 6.0 from http://www.microsoft.com/en-us/download/details.aspx?id=3988.

ST102569

If you upgrade to SQL Optimizer for SQL Server 10.0.1 from a previous version (and install versions side-by-side) and then uninstall a previous version, when you attempt to send SQL from Toad for SQL Server to SQL Optimizer, you will encounter an error. After closing the error message, the SQL may or may not be sent successfully.

Workaround:

• Uninstall SQL Optimizer 10.0 before installing version 10.0.1.
• Or use the Repair feature in the SQL Optimizer for SQL Server 10.0.1 .msi Installer to replace the missing files.

N/A

If you upgrade to SQL Optimizer for SQL Server 10.0.1 from a previous version and then uninstall SQL Optimizer 10.0.1, the Start menu shortcut and some installation files are not completely removed.

Workaround: After uninstalling SQL Optimizer 10.0.1, manually remove the SQL Optimizer 10.0.1 shortcut and remaining 10.0.1 installation files.

N/A

After installing SQL Optimizer for SQL Server 10.0.1, if you then install a previous version of SQL Optimizer side-by-side with 10.0.1, and then uninstall version 10.0.1, you cannot launch the previous version from the Start menu.

Workaround: Launch the previous version of SQL Optimizer using the executable in the installation directory.

N/A

ST89823

You are not provided with an option to upgrade when installing SQL Optimizer 7.1 if you have SQL Optimizer 7.0 installed with Toad for SQL Server.

Workaround:

Perform a side-by-side installation of SQL Optimizer 7.0.

ST83496

When you connect to SQL Server using Windows group, you cannot define a default schema.

Workarounds:

1. Connect to the SQL Server with a login who has permission to create a user, and use the following script to create a user login (replace domainname\username with your NT login). USE [yourdbname] GO CREATE USER [domainman\username] FOR LOGIN [domainname\username] WITH DEFAULT_SCHEMA=[dbo] GO. After the above is created, connect to the database using Windows Authentication to use SQL Optimizer.
2. Contact your Database Administrator to directly add your domainuser as a login.

ST84377

ST41386, ST98296

Optimizing SQL with DBO.Sys Objects results in a "Table does not exist" error because Sys Objects reside in the SYS schema and not the DBO schema. Since the DBO schema is only backwards compatible to SQL Server, SQL Optimizer is unable to access it.

Workaround:

Optimize SQL with Sys Objects with the SYS schema instead of the DBO schema.

ST75908

Executing SQL alternatives with an Option Clause using Query Hints for SELECT statements in CREATE VIEW causes an error because these statements are not supported by SQL Server.

Workaround:

Clear the checkbox for the SQL alternative with the Option Clause before using the Auto Optimize or Optimize function to generate alternatives without the Option Clause.

ST53842

When using Microsoft SQL Server 2005 SP1 and optimizing certain types of SQL statements, you might encounter an "Internal Query Processor" error.

See Microsoft support article 931329 for more information.

Workaround: Upgrade to SQL Server 2005 SP2.

N/A

N/A

If you are using dynamic port allocation and UDP port 1434 is disabled, SQL Optimizer may not be able to connect to SQL Server and you may receive an error message. This is a known Microsoft issue. See Microsoft Support Article ID 823938 for more information.

Workaround:Manually specify the SQL Server connection string as [Server]\[Named Instance],[Port] in SQL Optimizer.

N/A

512 MB of RAM minimum, 1 GB recommended

Note: The memory required may vary based on the following:

• Applications that are running on your system.
• Size and complexity of the database.
• Amount of database activity.
• Number of concurrent users accessing the database

70 MB of disk space to run SQL Optimizer

Note: This is the disk space required for a full installation, which includes 457 MB download of temporary setup files that can be removed at the completion of the installation.

Microsoft® .NET Framework 4.0

Note: The .NET Framework Client Profile is not supported.

SQL Server® 2005, 2008, 2012, 2014, 2016, 2017

• SQL Optimizer has been tested against SQL Server 2017 running on Windows or Linux.

SQL Server 2005 Express

SQL Server 2008 Express

Note: SQL Server Compact edition is NOT supported.

Microsoft Internet Explorer® 6.0 or later.

Adobe® Acrobat® Reader 7.0 or later (for viewing the Installation Guide).

SQL Server Management Objects (SMO); for more information about SMO, please visit http://msdn.microsoft.com/en-us/library/ms162189.aspx. You can also simply install Management Studio from SQL Server installation media.

SQL Optimizer has been tested with the following:

• Citrix® XenApp™ 5.0 on Windows Server 2003 (Service Pack 2) using the Citrix Presentation Server Clients 4.0
• Citrix XenApp 6.5 on Windows Server 2008 R2

Note: SQL Optimizer may work in virtualization environments other than the ones in which it was tested.