Toadฎ for SQL Server

Beta Version 4.0.0.707

Beta Release Notes

Released: July 01, 2008


Contents

Welcome to Toad for SQL Server

New v4.0 Functionality

Resolved Issues and Enhancements

Known Beta Issues

Third Party Known Issues

System Requirements

Global Operations
 

Beta Group


Welcome to Toad for SQL Server

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.
 


New v4.0 Functionality

 

 

 

 

 

 

 

Simply type or paste a SELECT statement into the editor on the Query tab and click on the "Model the SQL statement in the Query tab" toolbar button to draw a diagram of the objects and relations in the SQL statement. The statement can contain calculated columns, WHERE, HAVING, GROUP BY, ORDER BY clauses, and sub SELECT statements.

 

 

Errors in the SELECT statement will be flagged in the editor and added to the Output window.

 

 

 

 

 

 

 

 

 

To continue the example, let's do a "Replace All," and change "CA" to "CATEST". It now looks like this:

 

    Notice that the Data tab now has "Submit" and "Reject" buttons at the bottom. These changes will not be made to the database until you select the "Submit" button or you can just reject the changes by selecting the "Reject" button. Also, the rows that were changed are indicated by the delta symbol in the left-hand side gutter of the editor.

 

    The Shift+Click and Ctrl+Click also has another use. You can pick a disparate set of cells like this:

 

 

    Now if you do a Copy Cells or Ctrl+C, and select a different row, and do a Paste or Ctrl+V, the copied cells will be copied exactly in this pattern starting at that row. Toad is smart enough to copy it to the correct columns no matter what cell you actually have selected for that row. In this example, we have selected the row with the name "Ann Dull", and after the paste, the data looks like:

 

 

Notice that the Data tab now has "Submit" and "Reject" buttons at the bottom. These changes will not be made to the database until you select the "Submit" button or you can just reject the changes by selecting the "Reject" button. Also, the rows that were changed are indicated by the delta symbol in the left-hand side gutter of the editor.

 

 

        In this example, after selecting "Set 2", the Data Diff Viewer is invoked:

 

 

    There is also an option off of the "Compare To->History" submenu to save the current data. This is useful from the Database Explorer's Data tab when, over time, the data might be changing and can then be compared against this data that was saved.

 


Resolved Issues and Enhancements

Feature

Resolved Issue

Change Request

New in this Beta Drop
 

Code Completion

Searching in list should be case-insensitive regardless of db's case sensitivity.

CR50635

Right click when Large Script, causes freeze.

CR48447

Exception occurs when pressing Ctrl+. key in an empty editor.

CR49509

Code completion doesn’t function correctly and exception is thrown when invoking code completion in the second editor.

CR51333

Exception occurs when pressing Ctrl+. key after "(" in the insert statement.

CR46833

Data Grid

Only allow 2 digits entering into the scale for money data type.

CR51108

Database Explorer/Object Explorer

Refresh of explorer should respect the expanded state of the active node.

CR50250

Editor

Auto-replace only function when connected to 2K, not 2005.

CR50791 (Reported by Tim Sewell)

ER Diagram

Relationship is not shown between tables via foreign key.

CR51393

Generate Data Script

Only 1000 rows are generated if the total rows are over 1000.

CR50005

Query Builder

Execute button is disabled when querying a table in A database first then querying a table in B database.

CR49274

Version Control

CVS does not work with new version of cvsnt.

CR51457

Exception is thrown when clicking the server field without selected source provider.

CR51235

 
 

In Previous Beta Drops

 

Code Completion

Exception and Toad crashes when entering convert statement.

CR47019

Object names beginning with number breaking Insight.

CR42271

Toad crashes on typing execute or exec statement.

CR48549 (Reported by Mike Webster)

Exec statement not showing correct objects in dropdown.

CR47074

Support for local and global variables.

N/A

Display database list after typing “use” statement.

N/A

2000: List of owners was not available after typing database name and dot character.

CR44434

System.NullReferenceException after typing "dbo." and displaying the list of objects.

CR45354 (Reported by Darren Myher)

Connection Manager

On a new install, Toad SS will automatically import connections from Enterprise Manager and Mgmt Studio.

N/A

v3.2 release does not allow connecting to SQL Server 2008 Community Technology Preview (CTP).

N/A

Connections Dialog

Double-clicking on Connections Dialog column header causes exception.

CR47403

Data Compare

Data Compare doesn't support IDENTITY column in SQL Server.

CR48304

Database Backup

Clicking Contents button raises an error.

CR50278 (Reported by James Tan)

Database Explorer/Object Explorer

In the Object Explorer, Generate SQL to Editor appends to open editor. In the Database Explorer, it opens a new editor. We now made both to act consistently, regardless of where it is invoked. Both will open a new editor.

CR50462 (Reported by Peter Larbalestier)

Creation date sorting is not in chronological order.

CR46324

Run procedure from LHS of the browser does not execute procedure if there are no parameters.

CR49651

Toad throws System.InvalidCastException for some databases where SUSER_SNAME() returns NULL.

Reported by Tim Sewell, John Gay, James Tan

System.InvalidCastException when generating DDL scripts from a database.

Reported by Fik vax

Login: Clicking "User Mapping" right-hand side tab crashes Toad.

CR47405

Tree node cannot be collapsed if it has been expanded once.

CR43999

Changes to simplify the Tools menu and Tools toolbar.

N/A

Database Browser renamed to Database Explorer, Object Palette renamed to Object Explorer.

N/A

New functionality: you can press F2 now to change object name in place in Database Explorer.

N/A

SQL Server Database error when tables node is collapsed and no table object is shown after the error.

CR44002 (also reported by Mike Carillon).

Improvements in showing view script.

Reported by mikedepetris

Toad Crashes when trying to view the Reporting Services database that has a different collation than the master database.

Reported by Matt Sprygada

Toad fails to open a stored procedure with long enough name in 2000 database.

Reported by Scott Beckstead

Editor

Pressing TAB in the Editor indents instead of inserting a tab character.

CR47676 (Reported by Darren Myher)

Code Snippets don't work when connected to a 2005 instance.

CR47985

ArgumentOutOfRangeException when opening a SQL file that has syntax errors.

CR48667

Pressing TAB in the Editor indents instead of inserting a tab character.

CR44588

Code Completion: Better handling of object names with spaces.

CR42857

On a new install, defaults to opening up a new Editor upon connection rather than a Database Explorer.

N/A

New functionality: consolidating to one Execute button in the editor using F5, which will execute highlighted text and, if nothing is highlighted, execute all text in the editor; F9 functionality of running just the batch that the cursor is on still exists, but only through the F9 hot key.

N/A

ER Diagram

ER diagram always prints on a single sheet of paper making the objects and text very small.

CR42699

Export/Import

Export Wizard does not export data from the second result set.

CR44823

Added functionality to import multiple spreadsheets from Excel.

N/A

Object Editors

Backspace error in Find/Replace dialog.

CR43644

Exception occurs after creating synonym with Extended Properties.

CR46279

Query Builder

Exception is thrown when opening a saved file with subqueries and selecting statement type.

CR48350

Script Engine

 

Empty script when generating Alter script for stored procedures, views, functions via Generate SQL.

CR46211 (Reported by Lorenzo Statie)

Comment blocks before "create procedure" and "create function" don't show.

CR46212 (Reported by Lorenzo Statie)

Version Control

Config the server name for subverson throws a null reference exception.

CR44067

     


Known Beta Issues

Feature

Known Issue

Change Request

 

General

Customized options selected in the Configuration wizard are not applied if you are running Toad as a Restricted user.

Workaround:

Customize these settings in the Options pages in Toad (Tools | Options from the menu).

CR0216699

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:

Enter any valid value in the identity column, and then press F5 to query the server for the correct value. This replaces the placeholder value you entered with the correctly incremented one.
 

CR0117786

Data Reports

Currently, you cannot create a Label Report in the Toad Data Report wizard.

CR0215945

Databases

When generating a DDL script for databases, the following objects are not included in the script:

  • Application roles

  • Schemas

  • Synonyms

CR0216490

Debugger

You cannot debug stored procedures with the following input parameters in this release:

  • Binary

  • Varbinary

  • Bit

  • Timestamp

  • Image

CR0133602

CR0133634

CR0133636

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 results in an error message stating, "String or binary data would be truncated" and data is not inserted into the temporary table.

Workaround:

Increase the size of the varchar columns in the temporary table.

CR0211704

Editor

The following object types are not found when using the View Object at Cursor (F4) feature:

  • Triggers

  • Procedures

  • Functions

  • Users

  • Hosts

CR0164917

Export Data

Binary data types cannot be exported in this release.

CR0170430

When exporting large results sets (approximately 500K), you may run out of memory before the operation completes.

Workaround:

Create a view for the query and export using that view.

CR0203483

Exporting more than 65,536 rows to an Excel 2007 instance causes an error.

Note: This issue does not affect Excel 2000 or 2003.

CR0211832

 

Log Reader

Sometimes when installing 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 components.

  3. 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.

  4. Execute the following commands on the SQL Server instance:

  5. EXEC sp_addextendedproc 'xp_qlr_version', 'xp_QuestLogReader.dll'

  6. EXEC sp_addextendedproc 'xp_qlr_logfile', 'xp_QuestLogReader.dll'

  7. EXEC sp_addextendedproc 'xp_qlr_loginfo', 'xp_QuestLogReader.dll'

  8. EXEC sp_addextendedproc 'xp_qlr_logread', 'xp_QuestLogReader.dll'

CR0216499

Maintenance Plans

We are in the middle of making more changes with the Maintenance Plan functionality for both 2000 and 2005 so, for this drop, please refrain from testing this area and reporting issues because we want to make sure these new changes are in. We will announce when they do get in and it is ready for more feedback.

 

Schema Compare

Default constraints, check constraints, foreign keys, and case differences display in schema compares even though you select options to ignore them on the Compare Options page (Tools | Options | Schema Compare | SQL Server | Compare).

CR0215192

CR0212297

CR0212301

Server Compare

If the target server is configured with Use Windows NT Fibers, you cannot synchronize Meta Data Service Packages.

CR0142206

SQL Tuning

For a list of known issues, see the SQL Tuning Release Notes.

N/A

Version Control

Toad is providing a more in-depth integration with popular VCS vendors. If you are using SCC as the provider from the a release earlier than v3.0, you currently cannot use this provider in Toad at this time. Also, you may not want to migrate settings to the current release.

N/A

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."

CR0214601

 


Third Party Known Issues

The following is a list of third party issues known to exist at the time of Toad for SQL Server release.

Feature

Known Issue

Change Request

Export Wizard

In order 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

http://www.microsoft.com/downloads/details.aspx?FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&DisplayLang=en
 

2007 PIAs

http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en

 

CR0138239

 


System Requirements

Client Requirements

Before installing Toad for SQL Server, ensure your client system meets the following minimum hardware and software requirements:

Platform

600 MHZ minimum

Memory

512 MB of RAM minimum, 768 MB recommended


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

  • Applications that are running on your system when using Toad
  • Size and complexity of the database
  • Amount of database activity
  • Number of concurrent users accessing the database
Hard Disk Space 130 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

Windows 2003

Windows XP Professional (32-bit or x64)

Windows Vista (32-bit; Ultimate edition with XP Graphics has been tested)

Note: SQL Tuning is not supported on Windows Vista (any edition).

Additional Software The Automation Script Designer feature requires the Microsoft .NET Framework v3.0 or later. If not using this feature, then only Microsoft .NET Framework v2.0 or later is required.

Note: In order to run Toad, the .NET security policy must be set to Unrestricted. For information about setting this policy, refer to User Privilege Requirements.


(Optional) Spotlight on SQL Server 4.5 or later


Microsoft Internet Explorer 6.0 or later


Adobe Acrobat Reader 5.0 or later

Server Requirements

Before installing Toad for SQL Server, ensure your server meets the following minimum hardware and software requirements:

Operating System

Windows 2000 Server with SP4 or later

Windows 2000 Professional Edition with SP4 or later

Windows XP (32-bit with SP2 or later; x64)

Windows 2003 Server (32-bit or x64 with SP1 or later)

Windows Vista (32-bit; Ultimate edition with XP Graphics has been tested)


Note: The Log Reader server components are not supported on Windows Vista (any edition) or any x64 server. Also, the Log Reader cannot process transaction log files from an x64 server.

Supported Databases

Microsoft SQL Server 2000 with SP3, 2005 with SP2


Note: SQL Server Compact Edition is not supported.

Additional

Software

Microsoft SQL-DMO 8.0 (included if client connectivity is installed)


Note: Client connectivity and configuration for each database is a pre-requisite for connecting.

User Privilege Requirements

The following user privileges are required for installing and running Toad for SQL Server:

  1. From the Windows Start menu, select Settings | Control Panel.

  2. Double-click Administrative Tools.
  3. Double-click Microsoft .NET Framework 2.0 Configuration.
  4. 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.
  5. Click Evaluate Assembly from the list of tasks in the right panel. An Evaluate an Assembly window displays.
  6. Browse to the location of Toad.exe in the File field.
  7. Click Next to view permissions for Toad.exe.
  8. Set the permission to Unrestricted.

Debugging Requirements

Verify the following general requirements to ensure that the Debugger operates properly for all SQL Server installations:

Note: Currently, you cannot debug SQL/CLR code.
 

SQL Server 2005 Prerequisites

To debug locally, perform the following on the client machine:

  1. Install the SQL Server 2005 Workstation Component option of the SQL Server 2005 installation.
  2. In Toad, commit or rollback the connection before starting the debugging session.

To debug remotely, perform the following:

  1. On the client machine, install the SQL Server 2005 Workstation Component option of the SQL Server 2005 installation.
  2. 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: regsrv32 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

  1. Make sure the following permissions are set:

sp_addsrvrolemember 'Domain\Name', 'sysadmin'

where Domain\Name is your Windows login

  1. In Toad, commit or rollback the connection before starting the debugging session.

Platforms Tested for Debugging Support

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
(SP4)

2000 Pro (SP4)

XP Pro

XP Pro (SP2)

Vista Pro

2003 EE

—

—

— — —

—

—

2003 EE (SP1)

—

X

X

X

—

X

—

2000
(SP4)

—

X

X

X

—

X

—

2000 Pro
(SP4)

—

X

X

X

—

X

—

XP Pro

—

—

—

—

—

—

—

XP Pro (SP2)

—

X

X

X

—

X

—
Vista Pro — — — — — — X

SQL Server 2000 (SP4) Platforms Tested for Debugging Support

Client

Server

2003 EE

2003 EE (SP1)

2000
(SP4)

2000 Pro (SP4)

XP Pro

XP Pro (SP2)

Vista Pro

2003 EE

X

—

— — —

—

—

2003 EE (SP1)

—

X

—

—

—

—

—

2000
(SP4)

—

—

X