Toadฎ for SQL Server
Version 4.0.0
Release Notes
September 3, 2008
Toad for SQL Server is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, and instant access to SQL Server expertise.
Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.
All of this comes with
the backing of Quest Software, a healthy and growing corporate entity
that can provide the necessary training, support, and superior customer
service demanded by IT management.
Review the following sections for updates in this release and new features:
The
Existing Customers: To view the new look and
feel, do not migrate settings from the previous installed version or read
How do you Toad?
Setting up the New Toad for SQL Server 4.0 UI
document.
You can now generate a report of assigned keyboard shortcuts. This is useful for keeping up with any customized shortcuts you create.
You can now share notes about objects, lookup tables, and hidden column settings with other users by specifying a network share location under Object Annotation Cache in Tools | Options | Database | Cache.
Toad now supports opening Excel 2007 (.xlsx) files. You can also export data to an Excel 2007 instance, but cannot export to an Excel 2007 file or import data from an Excel 2007 file.
The Object Palette has been renamed to Object Explorer and automatically opens to a tree view when you connect to a database.
The Database Browser has been renamed to Database Explorer, and is now hidden by default to avoid confusion with the Object Explorer.
You can now use shortcut keys to perform the following tasks:
|
DELETE |
Opens a Drop object window. |
|
F2 |
Renames an object without opening a Rename object window. |
When creating, altering, or dropping an object, the default is to execute the script without having to preview it first. To enable the preview script mode again, select the Always preview script in object editors checkbox in Tools | Options | Database | General.
When using the Generate SQL right-click menu from the Object Explorer or Database Explorer, you can now set an option to format the generated SQL (disabled by default). To format the SQL, select the Automatically format generated SQL checkbox in Tools | Options | Explorer | General.
When you right-click a stored procedure and select Run in the Object Explorer or Database Explorer, you enter parameter values, and then Toad for SQL Server sends the T-SQL to an editor and runs it. You can then provide different values or change the script in the editor itself. Previously, you had to right-click the stored procedure, select Run, and enter values to re-run the script.
Schema, Server, and Data Compare now print a report rather than a screenshot of the compare.
You can now create and manage SQL Server 2005 maintenance plans from Toad.
Toad for SQL Server now supports the following objects:
|
|
|
|
|
|
|
|
You can now specify whether to generate a SELECT, INSERT, UPDATE, DELETE, or CREATE statement from the toolbar.
You can now manually edit a query in the Query tab of the Query Builder. Any differences between the SQL in the Query tab and Diagram tab are highlighted. Toad for SQL Server also supports full editor functionality in the tab, including code completion and snippets.
Queries executed in the Query Builder are now saved to SQL Recall so you can re-use them.
You can now reverse engineer queries from the Editor or Query Builder.
For more information, see Reverse Engineering Queries in the help.
You can now press CTRL+N to open a new editor window. Also, an editor window opens by default on startup
Group execution is now integrated in the editor so you can execute SQL across multiple instances.
Execution of scripts and statements has been combined into the Execute Script toolbar button (Keyboard: F5). If you do not select a statement in the editor, the default is to execute the entire script.
Toad automatically saves a backup copy of open editor files that have been modified at five minute intervals (default). It also saves a backup copy anytime you execute the SQL. If the application does not terminate normally, the next time you open Toad for SQL Server the backup copies automatically open in the editor so you can either save changes to your regular file or discard them.
You can specify the backup interval in Tools | Options | Environment | General.
Code Snippets and SQL Recall now open automatically when you open an editor:
Code Snippets include the following enhancements:
The Code Snippets Favorites folder shortcut key has changed to CTRL+Q.
A shortcut key has been added to invoke the "Surround With" Code Snippets. To use this functionality, select the text you want the template to surround and press CTRL+SHIFT+SPACE to select a comment or procedure.
Toad Insight (Intellisense) has been redesigned and renamed to Code Completion. Additional code completion enhancements include:
Additional statement types are supported including update, delete, insert, call, and truncate table.
Comments, object data types, and parameters display, if available.
Functions that return a table type now display.
Complete join statements are now generated.
Local variables now display when you enter the @ symbol. To display global variables, enter the @@ symbol.
Code completion options are located in Tools | Options | Editor | Code Completion.
Embedded SQL has been renamed to Application Code. In addition, you can now select the template to use to add or remove application code from a statement in the toolbar.
Explain Plan functionality has been renamed to Execution Plan to match SQL Server terminology.
(SQL Server 2005 only) You can now debug any script that has been saved to disk. The script does not have to include a stored procedure or function.
For a list of updates or features in this release, see the SQL Optimizer release notes.
You can now export data to an Excel 2007 instance, but cannot export to an Excel 2007 file.
Export data into an existing spreadsheet, including an existing worksheet or a new one. You can also specify the column and row where you want to begin adding data. This allows you to build charts and graphs from an existing spreadsheet and refresh the report by updating the data worksheet.
Save export settings as a template that you can use for scheduled automation scripts.
Import data into a new table you create on-the-fly or into an existing table.
Save import settings as a template that you can use for scheduled automation scripts.
Currently, you cannot import data from an Excel 2007 file.
You can now compare result sets from the current editor or a different editor in the
editor's Result Sets or a Data tab in the Object Explorer Viewer pane without having to save one of the sets to a file.
You can also save a result set and later use it for comparison. This is useful
if the data changes over time, and you want to compare it against the saved
version of the data.
You can now right-click a data grid and select Show | option to customize the look and feel of the grid without having to open an options page.
The data grid in the Editor and the Data tab are now read-only by default. A red circle in the lower-left corner of the data grid indicates that the data is read-only. To edit the data, right-click the red circle and select Read-only. The circle changes to green, and you can now edit the data.
If the table does not contain a primary key, you can click the red circle to define a temporary key so that you can edit the data.
You can quickly find and replace data by pressing CTRL+F in any data grid.
You can now make minor changes to the underlying query in a Toad pivot grid. To edit the query, right-click in the data area of the pivot grid and select Edit Underlying Query. If you add or remove a column, a dialog warns you that you should create a new query.
You can specify an integer format that is separate from the number format in Tools | Options | Environment | Grid.
Support for new automation activities:
|
Select to File |
Execute an existing SQL script or Query Builder query and export the results to an Excel, HTML, or CSV file. You can then use additional activities to add the exported result file to a zip file, attach the file to an email, or copy the file. Note: Bind variables are not supported for this activity. If bind variables are detected, a message alerts you during the test run of the automation script. |
|
Execute SQL |
Execute an existing SQL script or Query Builder query. Note: Bind variables are not supported for this activity. If bind variables are detected, a message alerts you during the test run of the automation script. |
|
Select to Editor with Results |
Execute an existing SQL script or Query Builder query and save it and any results sets in a Toad for SQL Server editor file (.tef). This file format is useful for building scripts that have large result sets that you do not want to continue executing or for saving results when you have not finished building a script. |
|
Export Wizard |
Export data from databases, tables, views, or query into a CSV, Excel, or other file. You can save the export settings as a template that you can use for scheduled automation scripts. |
|
Import Wizard |
Import data from a CSV, Excel, or other file into a new table or append to an existing table. You can save the import settings as a template that you can use for scheduled automation scripts. |
|
Toad for SQL Server Pivot Grid |
Refresh an existing Toad for SQL Server pivot grid and export results to a report. You can then use additional activities to add the pivot grid to a zip file, attach it to an email, or copy it. |
|
Delete File |
Delete one or more files from a specified location. |
You can now click an activity to automatically add it to the Design pane.
Toad automatically adds a connection to the current database anytime you add an activity that requires a connection.
Improved exception handling lets you set exception handling and error logging by double-clicking the Script Settings activity that displays by default in the Design pane. Once you specify these settings, they are used by all subsequent automation scripts.
Automation "snippets" have been renamed to "templates" to avoid confusion with Code Snippets.
You can now save properties for any activity as a template for future use.
Toad for SQL Server now supports the Team Foundation Server (TFS) version control provider. In order to use TFS, you must install the Visual Studio Team Foundation Server MSSCCI Provider on the same computer as Toad for SQL Server.
Note: This is not the same client that you install with Visual Studio. You can download the MSSCCI Provider from one of the following locations:
2005 MSSCCI Provider: http://www.microsoft.com/downloads
/details.aspx?FamilyID=87e1ffbd-a484-4c3a-8776-d560ab1e6198&DisplayLang=en
2008 MSSCCI Provider: http://www.microsoft.com/downloads/
details.aspx?familyid=FAEB7636-644E-451A-90D4-7947217DA0E7&displaylang=en
For more information about configuring TFS, see Configuration Prerequisites and in the help.
The following is a list of issues addressed and enhancements implemented in this release of Toad for SQL Server.
|
Feature |
Resolved Issue |
Defect |
|
Connections |
If you are connecting to a local database, using "(local), <port #>" in the Server name field no longer results in an error. |
CR#218603 ST#42237 |
|
In rare instances, after logging into a database, an error occurred and the server could not connect. This issue was related to using SQL-DMO, which has been removed in this release. |
ST#43625 | |
|
When viewing properties for a server connection (right-click a server in the Connection Manager and select Properties), the following missing entries were added:
|
CR#222200 ST#42450 | |
|
Automation |
Reports that require bind variable inputs are now supported. |
CR#218790 ST#42253 |
|
Data Compare |
Data Compare has been redesigned to support very large data sets. You no longer need to limit a compare to 100,000 records for each table. |
CR#158211 ST#41609 |
|
Data Grid |
You can now right-click a column header and select Fit to Header to size the width of all data columns to the width of the column header text. |
CR#154172 ST#41602 |
|
When creating a custom data filter for a column, the Custom AutoFilter window now includes "Like" and "Not Like" operators. |
ST#42514 | |
|
Debugger |
In some environments, the result set returned by a stored procedure called by another stored procedure is inserted into a table; however the table definition has varchar columns that are not long enough. This no longer results in an error message stating, "String or binary data would be truncated" and data is not inserted into the temporary table. |
CR#211704 |
|
Entering Null as the value in the Debug Start Parameters window no longer applies the value as a string 'NULL'. You can also press CTRL+DELETE to set a null value. |
ST#43590 | |
|
Debugging and then executing a user-defined function that contains a scalar function when invoked from the Editor now generates the correct SQL statement. |
CR#227747 ST#42812 | |
|
When debugging some scripts, a parser syntax error no longer displays. |
ST#49836 | |
|
An invalid topic named Debug Scripts was removed from the help. See the Debug Code topic in the help for correct information. |
ST#43277 | |
|
Editor |
Code completion now filters out object types that do not apply to the current context. |
CR#223790 ST#42539 |
|
When altering a script in the Editor, clicking Format SQL no longer inserts extra lines before comments in the script. |
ST#47600 | |
|
Export Wizard/ One Click Export |
Exporting more than 65,536 rows to an Excel 2007 instance no longer causes an error. |
CR#211832 ST#42006 |
|
You can now successfully export data from a query with parameters. |
CR#229814 ST#43093 | |
|
After executing a query against one database, and then executing the same query in the same editor against a different database, Toad now correctly exports the correct results from the second query. |
ST#44823 | |
|
An error no longer occurs when exporting data that contains an XML column to Excel. |
ST#43213 | |
|
Import Wizard |
You can now select multiple worksheets in an Excel file to import. |
CR#215343 ST#42114 |
|
When importing an xml file into a database, an "Input array is longer than the number of columns in this table" error no longer occurs. |
ST#47515 | |
|
Master Detail Browser |
You can now select a checkbox beside each column you want to view in the Master Detail Browser. |
CR#229305 ST#43015 |
|
Object Explorer/ Database Browser
|
When altering tables, views, stored procedures, and functions, the object editors now use an alter script. |
ST#41723 |
|
You can now select Automatically format generated SQL in Tools | Options | Explorer | General to either preserve your custom formatting or use the database formatting when you right-click an object and select Generate SQL. The default is to use the database format by . |
ST#46427 ST#49645 | |
|
When dragging a table from the Object Explorer to the editor, extra lines are no longer added. |
ST#49409 | |
|
The Creation Date in Property tabs now sorts in chronological order. |
ST#46324 | |
|
Tables:
|
CR#227920 ST#42836 CR#194771 ST#41870 ST#41852 CR#225422 ST#42608
| |
|
Databases:
|
CR#216490 ST#42148 ST#46834 CR#213716 ST#42062 CR#227745 ST#42811
| |
|
Functions: When altering a function that returns a table, adding a new column no longer results in an error. |
ST#52029 | |
|
Jobs: Updating the order of a job step when altering a job no longer results in an error. |
ST#50454 | |
|
Linked Servers: Toad now supports linked servers. |
ST#42370 | |
|
Stored Procedures: (SQL Server 2005 only) Attempting to view the Script tab for a system stored procedure in a database other than the master database no longer results in an error. |
CR#225049 ST#42583 | |
|
Views: You can now right-click a view to rename it, or can press F2 to rename it. |
ST#41778 | |
|
Reports |
Reports Manager:
|
ST#49310 ST#43399 ST#43398 |
|
|
Schema Reports:
|
CR#223188 ST#42506 CR#220737 ST#42364 |
|
Schema Compare
|
Default constraints, check constraints, foreign keys, case differences, and permissions no longer display in schema compares if you ignore them on the Compare Options page (Tools | Options | Schema Compare | SQL Server | Compare). |
CR#215192 CR#212297 CR#212301 ST#46991 |
|
If a generated synchronization script contains an Alter Column statement for a ROWGUIDCOL column, the statement is removed from the script before execution because the statement is not valid. |
ST#49012 | |
|
Version Control |
Using the http or https protocol to configure subversion in Toad no longer results in an error. |
ST#44067 |
|
The help file now provides more detailed information about prerequisites needed to configure Subversion to work with Toad. For more information, see Version Control Objects and Files in the help. |
ST#43596 | |
|
Web Browser |
When selecting the address field in the Web Browser, the entire URL is now highlighted. |
ST#41939 |
The following is a list of issues known to exist at the time of Toad for SQL Server release.
|
Feature |
Known Issue |
Defect |
|
Installation/ Upgrade |
Customized options selected in the Configuration wizard are not applied if you are running Toad as a Restricted user. Workaround: |
CR#216699 ST#42154 |
|
Startup |
(Windows Vista on Toad client only) If you initially start Toad when logged in as a standard user and enter a license key, the license key should be saved to: C:\Program Files\Quest Software\Toad for SQL Server 4.0 However, a standard user does not have write privileges in Vista to C:\Program Files so the key is saved to the following directory instead: C:\Users\username\AppData\Local\VirtualStore\Program Files\Quest Software\Toad for SQL Server 4.0 If you later start Toad as an administrator, you are prompted to enter the key again because it is not in the C:\Program Files directory. |
N/A |
|
Connection |
If you migrate settings from a previous version, the Run script on new connection option in Tools | Options | Database | SQL Server may point to the path from the previous version. If you later delete the Application Data Directory for the previous version, which contains the script, attempting to connect to any database results in a path not found error. You can click OK and continue working. Workaround: Select Tools | Options | Database | SQL Server and navigate to the location of the latest connection script in the Application Data Directory. By default, this script is located in: C:\Documents and Settings\user\Local Settings\Application Data\Quest Software\Toad for SQL Server 4.0\Templates\Scripts\InitialSqlServer.Sql |
ST#42899 |
|
Data Grid |
When adding data to a column that has an Identity Increment value, Toad cannot determine the increment value on the client side and an error occurs if you do not enter a value for the column. Workaround: |
CR#117786 ST#41467 |
|
Data Reports |
Currently, you cannot create a Label Report in the Toad Data Report wizard. |
CR#215945 ST#42133 |
|
Debugger |
You cannot debug stored procedures with the following input parameters in this release:
|
CR#133602 CR#133634 CR#133636 |
|
Editor |
The following object types are not found when using the View Object at Cursor (F4) feature:
|
CR#164917 ST#41627 |
|
Commas used in variables and column names do not apply custom format settings when used with INSERT statements. |
ST#50363 |
|
|
By default, the Document recovery option is enabled in Tools | Options | Environment | General. If you select Allow multiple copies of Toad for SQL Server to be loaded checkbox on this page, it automatically disables the Document recovery option to avoid possible conflicts. |
N/A | |
|
Export Wizard/ One Click Export |
Binary data types cannot be exported in this release. |
CR#170430 ST#41655 |
|
When exporting large results sets (approximately 500K), you may run out of memory before the operation completes. Workaround: |
CR#203483 ST#41935 |
|
|
Import Wizard |
Currently, you cannot import Excel 2007 files because they are saved using an xlsx format. Workaround: |
CR#221667 ST#42416 |
|
Maintenance Plans |
(LiteSpeed 4.8 plans converted to SSIS plans) When adding a Back Up Database task to a LiteSpeed 4.8 Maintenance Plan, selecting the Remove files older than checkbox does not remove the 4.8 Maintenance Plan. |
ST#52721 |
|
(SQL Server with LiteSpeed 4.x engine installed) You cannot edit a LiteSpeed Back Up Database or Clean Up Maintenance Plan task for an SSIS maintenance plan if the LiteSpeed engine has not been upgraded to 5.0. |
ST#52548 |
|
|
Object Explorer/ Database Explorer |
Tables: Attempting to enter data for an XML data type in the Data tab results in an error. |
ST#42580 |
|
Databases:
|
ST#51164 ST#42782 |
|
|
Stored Procedures:
|
ST#44201 ST#51346 |
|
|
Query Builder |
When reverse engineering SQL from the Query tab or the Editor, consider the following:
|
ST#52569 ST#49731 ST#48258 |
|
Reports |
Currently, the schema report contains information for tables, views, and procedural objects. |
ST#48513 |
| Server Compare |
If the target server is configured with Use Windows NT Fibers, you cannot synchronize Meta Data Service Packages. |
CR#142206 |
|
SQL Optimizer |
For a list of known issues, see the SQL Optimizer release notes. |
N/A |
|
Version Control |
The Update Database function for version control often requires that objects be dropped and recreated. If tables are referenced by Foreign Key constraints, the following error occurs when executing the script: "Could not drop object N because it is referenced by a FOREIGN KEY constraint." |
CR#214601 ST#42093 |
|
(TFS only) If you have not selected a sub-project, attempting to add an object results in an error. Workaround: Select Tools | Options | Version Control | Defaults and specify a sub-project in the Version control folder field. |
ST#51033 |
|
|
If you disable a version control configuration in Tools | Options | Version Control | General, and then enable the configuration, when you click OK a null reference error displays. Version control is enabled and you can ignore this error. |
ST#51933 |
The following is a list of third party issues known to exist at the time of Toad for SQL Server release.
|
Feature |
Known Issue |
Defect |
|
Export Wizard |
To export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations: 2003 PIAs 2007 PIAs
|
CR#138239 |
|
Import Wizard |
Importing large data sets from Excel (approximately 650,000 rows) is not recommended because of the amount of time it may take. This issue occurs because the Excel import component maintains the output in memory until the import completes. This can cause performance issues depending on the available system resources. |
CR#219754 |
Toad has a new look-and-feel that is similar to Management Studio, to reduce the learning curve for new users. It also includes shortcut keys to match Management Studio, reorganized menus, and simplified toolbars.
Existing Customers: To view the new look and
feel, do not migrate settings from the previous installed version or read
How do you Toad?
Setting up the New Toad for SQL Server 4.0 UI
document.
For information about upgrading refer to the Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server 4.0 | Documentation.
Before installing Toad for SQL Server, ensure your client system meets the following minimum hardware and software requirements:
| Platform |
600 MHZ minimum, 1 GHz recommended |
| Memory |
512 MB of RAM minimum, 1 GB recommended Note: The memory required may vary based on the following:
|
| Hard Disk Space | 133 MB of disk space for installation.
Note: The disk space required may vary based on the edition of Toad selected for installation. |
| Operating System |
Windowsฎ 2000 Note: The Automation feature requires the .NET Framework 3.0, which is not supported on Windows 2000.
Windows Server 2003 Windows XP Professional (32-bit or x64) Windows Vista (32-bit or x64) Windows Server 2008 |
| Additional |
.NET Framework Notes: Consider the following:
(Optional) Spotlight on SQL Server Spotlight on SQL Server 4.5 or later Web Browser PDF Viewer
Maintenance Plans To take advantage of Integration Services (SSIS) in maintenance plans, you must install Client Tools 2005 on the client where Toad is installed. |
Before installing Toad for SQL Server, ensure your server meets the following minimum hardware and software requirements:
| Database Operating System |
Windows 2000 Server with SP4 or later Windows 2000 Professional Edition with SP4 or later Windows Server 2003 (32-bit or x64 with SP1 or later) Windows XP (32-bit with SP2 or later; x64) Windows Vista (32-bit or x64) Windows Server 2008 (32-bit or x64) |
|
Supported Databases |
The following databases have been tested in this release.
Notes:
|
|
Additional |
Maintenance Plans To take advantage of Integration Services (SSIS) in maintenance plans, you must install Integration Services on any instance where you want to create maintenance plans. |
Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server SP2 using the MetaFrame Presentation Server 4.0 and Citrix Presentation Server Clients 10.2. For information about installing Toad in a Citrix environment, see Install Toad on Citrix Systems in the Toad for SQL Server Installation Guide.
The following user privileges are required for installing and running Toad for SQL Server:
If a Power user installs Toad, a Restricted user can run the application but cannot
Associate file extensions.
See the Toad shortcut icon on the desktop or the Toad menu option in the Windows Start menu. As a workaround, Restricted users can create a shortcut to the application and place it on their desktop from the install directory.
- From the Windows Start menu, select Settings | Control Panel.
- Double-click Administrative Tools.
- Double-click Microsoft .NET Framework 2.0 Configuration.
- Click + to expand My Computer, and then select the Runtime Security Policy node. A list of tasks for the node display in the right panel.
- Click Evaluate Assembly from the list of tasks in the right panel. An Evaluate an Assembly window displays.
- Browse to the location of Toad.exe in the File field.
- Click Next to view permissions for Toad.exe.
- Set the permission to Unrestricted.
Before you perform a silent installation, the following software must be installed on every system on which you are installing Toad:
ท Microsoft .NET Framework 2.0 or later
For information about installing Toad
silently, see Install Toad Silently in the Toad for SQL Server
Installation Guide.
Verify the following general requirements to ensure that the Debugger operates properly for all SQL Server installations:
Note: The security policy can be applied to the domain or local computer.
Note: Currently, you cannot debug SQL/CLR code.
To debug locally, perform the following on the Toad client:
To debug remotely, perform the following:
Install the SQL Server 2005 Workstation Components option of the SQL Server 2005 installation.
- Copy and register the ssdebugps.dll (debugging host component) on both the client and server. This file is located by default in the following directory on the server where SQL Server 2005 is installed:
C:\Program Files\ Common Files\Microsoft Shared\SQL Debugging
To register this file, open a command prompt and enter the following command: regsvr32 ssdebugps.dll
Note: If you are unable to locate this file, you can run the remote debugging setup component (rdbgsetup.exe). This file is located by default in the following directory on the server where SQL Server 2005 is installed: C:\Program Files\Microsoft SQL Server\90\Shared\1033
Your Windows account that Toad is running under must be a member of sysadmin server role in the SQL Server being debugged.
- Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).
To create a Server login from your Windows login and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:
sp_addsrvrolemember 'Domain\Name', 'sysadmin'
where Domain\Name is your Windows login
Note: By default, Windows administrators on a machine running SQL Server are SQL Server sysadmins on that machine.
To debug locally, perform the following on the Toad client:
Make sure that SQL Server 2000 with SP3 or SP4 is installed.
In Toad, commit or rollback the connection before starting the debugging session.
To debug remotely, perform the following:
On the Toad client, do one of the following:
Make sure that SQL Server 2000 with SP3 or SP4 is installed.
Copy and register the sqldbg.dll and sqldbreg2.exe (debugging host components) on both the Toad client and server. These files are located by default in the following directory on the server where SQL Server 2000 is installed:
C:\Program Files\Common Files\Microsoft Shared\SQL Debugging
To register these files, open a command prompt and enter the following commands:
regsvr32 sqldbg.dll
sqldbreg2.exe /RegServer
Note: The Remote Procedure Call (RPC) service should be started on both the Toad client and server.
- Open a command prompt and run dcomcnfg.exe.
- Expand Component Services, Computers.
- Right-click My Computer and select Properties.
- Select the COM Security tab.
- Under Access Permissions, click Edit Default, and verify permissions.
Note: By default, Windows administrators on a computer running SQL Server are SQL Server sysadmins on that computer.
The following platforms have been tested for debugging support.
Note: The Service Pack on the client must match the Service Pack on the server unless specified otherwise.
|
SQL Server 2005 Platforms Tested for Debugging Support |
|||||||
|
Client |
Server |
||||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
||
|
2003 EE |
|
|
| | |
|
|
|
2003 EE (SP1) |
|
X |
X |
X |
|
X |
|
|
2000 |
|
X |
X |
X |
|
X |
|
|
2000 Pro |
|
X |
X |
X |
|
X |
|
|
XP Pro |
|
|
|
|
|
|
|
|
XP Pro (SP2) |
|
X |
X |
X |
|
X |
|
| Vista Pro | | | | | | | |
|
SQL Server 2000 (SP4) Platforms Tested for Debugging Support |
|||||||
|
Client |
Server |
||||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
||
|
2003 EE |
X |
|
| | |
|
|
|
2003 EE (SP1) |
|
X |
|
|
|
|
|
|
2000 |
|
|
X |
|
|
|
|
|
2000 Pro |
X |
X |
X |
X |
X |
X |
|
|
XP Pro |
X |
X |
X |
X |
X |
X |
|
|
XP Pro (SP2) |
X |
X |
X |
|
|
X |
|
| Vista Pro | | | | | | | |
|
SQL Server 2000 (SP3) Platforms Tested for Debugging Support |
|||||||
|
Client |
Server |
||||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
||
|
2003 EE |
X |
|
| | |
|
|
|
2003 EE (SP1) |
|
X |
|
|
|
|
|
|
2000 |
|
|
X |
|
|
|
|
|
2000 Pro |
X |
X |
X |
X |
|
|
|
|
XP Pro |
X |
X |
X |
X |
X |
|
|
|
XP Pro (SP2) |
|
|
|
|
|
X |
|
| Vista Pro | | | | | | | |
|
SQL Server 2000 (SP3a) Platforms Tested for Debugging Support |
|||||||
|
Client |
Server |
||||||
|
2003 EE |
2003 EE (SP1) |
2000 |
2000 Pro (SP4) |
XP Pro |
XP Pro (SP2) |
||
|
2003 EE |
|
|
| | |
|
|
|
2003 EE (SP1) |
|
X |
|
|
|
|
|
|
2000 |
|
|
X |
|
|
|
|
|
2000 Pro |
X |
X |
X |
X |
|
|
|
|
XP Pro |
|
|
|
|
|
|
|
|
XP Pro (SP2) |
|
|
|
|
|
|
|
| Vista Pro | | | | | | | |
This section contains information about installing and operating this
product in
non-English configurations, such as those needed by customers outside of
North America.
This section does not replace the materials about supported platforms and
configurations
found elsewhere in the product documentation.
This release is Unicode-enabled
and supports any character set. In this release,
all product components should be configured to use the same or compatible
character
encodings and should be installed to use the same locale and regional options.
This
release is targeted to support operations in the following regions: North
America,
Western Europe and Latin America, Far-East Asia, Japan.
This release has the following known capabilities or limitations:
Knowledge XpertThe Knowledge Xpert feature is available with English language content only.
The Toad for SQL Server release package contains the following products:
For general installation information, refer to the Installation Guide
available
from the Windows Start menu under Program Files | Quest Software | Toad
for SQL Server 4.0 | Documentation.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc.
ฉ 2008 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
If you have any questions regarding your potential use of this material, contact:
| Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.