Toad^® for SQL Server

Beta Version 5.0.0.157

Beta Release Notes

Released: March 08, 2010

Contents

Welcome to Toad for SQL Server

With Toad, developers and database administrators can use a familiar, proven tool to manage databases. Toad empowers developers and administrators, of varying skill levels, to rapidly create and execute queries, automate database object management and develop SQL more efficiently.

Back to Top

New v5.0 Functionality

SQL Azure Support

• After creating an account and configuring the SQL Azure Firewall, you can connect to a SQL Azure database the same way you connect to your on-premise SQL Server.
  
   

• When Browsing and working with objects, the look and feel of the Object Explorer is the same as your on-premise SQL Server.
  
  
  

• Toad also includes SQL Azure support for the following features, and provides the same look and feel in these features that you find when using your on-premise SQL Server:

  • Group Execution

  • Export/Import

  • Query Builder

  • Master Detail Browser

  • Schema Reports

  • Data Reports

  • Execution Plans (both actual and estimated)

  • Stored Proc/Function Execution

Collaboration

You can now view RSS and Twitter feeds, including Toad Community postings from within Toad using the new Collaboration window. You can access this window from View | Collaboration. Once open, you can click any entry to open the related content. An icon indicates an RSS feed and an icon indicates a Twitter entry.

When you open the Collaboration window, it polls all RSS and Twitter feeds that you have defined in the Collaboration options page (Tools | Options | Environment | Collaboration). The first time you open the Collaboration window, the options page automatically displays.

In the Collaboration options page, you can also define your Twitter account details and a Twitter search to follow in Toad. The search defaults to a specific search depending on which product you use. By default, any posts in Toad are posted to this specific search. You can also clear the Only Search checkbox to display all your twitter posts.

In the Collaboration window, you can click at the top of the window to compose a new entry. You can select the drop-down arrow beside the icon to select which feed you want to post to.

To post to Twitter, use the entry field at the bottom of the window. When using Twitter, if you click an item in the list, an appropriate reply entry is entered in the field. If the post contains a link, that link is opened in the Web Browser as well. To post an update, press ENTER or click the lower-right Twitter icon. If you click the camera icon to the right of the twitter icon, you can toggle whether you want to include a screen shot of Toad with your post (After posting, this option always reverts back to false).

Debugger

Debug Trace

The debugger trace functionality adds the ability of any Toad debugger to generate a trace on a piece of code executed through a debugger, which can then later be replayed to investigate what actually happened during the execution. One additional feature of replaying the trace is that you can step both backwards and forwards in the debugger to evaluate the execution.

You enable debug trace collection by selecting the Collect debug trace checkbox in the Debugger Start Parameters window that displays when starting a debug session. You can also open this window by clicking on the Debugger toolbar.

Note: This flag is cleared after every execution (You probably don’t want to collect execution traces on every execution).

You can also enable and disable trace collection while executing using a new toggle on the Debugger toolbar.

When a debug trace has been created, a window displays that lets you browse through, delete, and replay debug traces. You can also open this window by selecting Debug | Windows | Debug Traces from the menu.

Each item in the list represents saved debug traces and you will only see the traces that were created for the current connection. When you hover over an item in the list, the full name of the piece of code and the value of any specified parameters when you executed it display. To replay a trace, double-click it in the list or click .

You can also generate a coverage report from the trace by clicking .

The debug trace collects the following:

·         Local parameters and arguments. Global variables are not collected by default, but can be enabled in the options.

·         Step information and callstacks.

·         Scripts of all involved code. This means that when you replay a trace you will see the script in the editor as it looked when the trace was created regardless of whether the object has been changed in the database.

The debug trace does not collect the following:

·         Anything returned to the script result or output.

·         The final return value from a function.

In addition, debug trace options are available in Tools | Options | Debugger | General. 

The first option determines whether the trace should record every line executed while debugging or the lines where you break or step over. By default all lines are executed.

Database Administration

Object Explorer

• (SQL Server 2008 only) Toad now supports Resource Governor functionality under the Management node in the Object Explorer.
  

  You can right-click a resource pool and create, edit, or remove a classifier function.

  Note: Once created, the classifier function displays in the Functions node for the selected database.
  
  
   

  In addition, you can manage workload groups for a resource pool in the Object Viewer window.
  
  

• (SQL Server 2008 Enterprise and Development Editions only) You can now add a filter to indexes in the Create/Alter Index window.
  
  
   

Data Management

Export Wizard

• When exporting to an Excel file, if there are multiple tables, Toad now exports to a single file and adds each table as a separate worksheet within that file.

• Toad now checks the directory you are exporting to and if a file with the same name already exists, the text of the Overwrite checkbox turns red as a warning so you can either overwrite or rename the file. The Next button is also disabled until you make a change.
  
  

• If you select a single table to export in the Export Wizard, you can specify a different name for the worksheet than the actual table name.
  
  

Export Wizard

• You can now execute an export template against a different connection than the one saved with it. For example, this allows you to use the same export template against your test, development, and production databases. To execute the template against a different connection, make sure you are connected to, and the new database has focus in the Connection Manager when you execute the template.

Import Wizard

You can now execute an import template against a different connection than the one saved with it. For example, this allows you to use the same import template against your test, development, and production databases. To execute the template against a different connection, make sure you are connected to, and the new database has focus in the Connection Manager when you execute the template.

Back to Top

Resolved Issues and Enhancements

Back to Top

Known Beta Issues

Back to Top

Third Party Known Issues

Back to Top

System Requirements

Client Requirements

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

Server Requirements

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

Citrix Requirements

Limited testing has been performed for Citrix support on Windows Server 2003 Enterprise Server (Service Pack 2) using the MetaFrame Presentation Server 5.0 and Citrix Presentation Server Clients 10.2. See "Install Toad on Citrix Systems" in the Toad for SQL Server Installation Guide.

User Privilege Requirements

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

• Only Power users and Administrators can install Toad.
• If a Power user installs Toad, a Restricted user can run the application but cannot
  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.
• If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and the Toad menu option in the Windows Start menu with any user on the computer.
• In order to run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy:

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.

• To create or modify the QuestSoftware.ToadSecurity table to enable Toad Security, the user who maintains this table must have privileges to create, insert, update, and delete it. All other users need only the ability to read the QuestSoftware.ToadSecurity table to use Toad Security.

Debugging Requirements

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

• Disable all firewalls or open corresponding ports. Windows XP SP2 includes an embedded Windows firewall that should be disabled or ports opened as well. Specifically, the TCP 135 port must be opened and Toad.exe must be added to the Exceptions list. The same is true for the remote (SQL Server) computer--TCP 135 port must be opened and sqlservr.exe must be added to the Exceptions list.
• Stop any antivirus software that can lock the corresponding components, settings, etc.
• Check your security policy because it may include an access lock to the remote server.

Note: The security policy can be applied to the domain or local computer.

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

Configure Debugging for SQL Server 2008 

To debug locally, perform the following on the Toad client

1. Install the SQL Server 2008 Client Tools on the Toad client.
2. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following

1. Install the SQL Server 2008 Client Tools on the Toad client.
2. Make sure the following permissions are set:
   • 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 account 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.

3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2005

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

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 Toad client, do one of 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

2. Make sure the following permissions are set:

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

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

Configure Debugging for SQL Server 2000

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

1. Make sure that SQL Server 2000 with SP3 or SP4 is installed.

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

To debug remotely, perform the following:

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

2. Make sure the following permissions are set:
   • Your Windows account that Toad is running under must be a member of the sysadmin server role for the instance you are debugging.
   • 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 account 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.
   • DCOM Access permissions must be granted for the system account and the group or user who needs access.
     
     To verify permissions:

     1. Open a command prompt and run dcomcnfg.exe.
     2. Expand Component Services, Computers.
     3. Right-click My Computer and select Properties.
     4. Select the COM Security tab.
     5. 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.

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

Back to Top

Global Operations

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:

• Quest SQL Optimizer for SQL Server—This release supports any single-byte character set. Double-byte or multi-byte character sets are not supported. In this release, all product components should be configured to use the same or compatible character encoding 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.
   

Back to Top

Beta Group

You can join the Toad for SQL Server beta discussion group by sending an email to: toad_ss_beta-subscribe@yahoogroups.com

Back to Top

© 2010 Quest Software, Inc.

ALL RIGHTS RESERVED.

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.

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.

If you have any questions regarding your potential use of this material, contact:

Refer to our web site for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, AccessManager, ActiveRoles, Aelita, Akonix, AppAssure, Benchmark Factory, Big Brother, BusinessInsight, ChangeAuditor, ChangeManager, DeployDirector, DirectoryAnalyzer, DirectoryTroubleshooter, DS Analyzer, DS Expert, ERDisk, Foglight, GPOADmin, Imceda, IntelliProfile, InTrust, Invirtus, iToken, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, LogADmin, MessageStats, Monosphere, NBSpool, NetBase, NetControl, Npulse, NetPro, PassGo, PerformaSure, Quest Central, Quest vToolkit, Quest vWorkSpace, ReportADmin, RestoreADmin, SelfServiceADmin, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Storage Horizon, Tag and Follow, Toad, T.O.A.D., Toad World, vAutomator, vControl, vConverter, vFoglight, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vSpotlight, vStream, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vBackup, Vizioncore vEssentials, Vizioncore vMigrator, Vizioncore vReplicator, Vizioncore vTraffic, Vizioncore vWorkflow, WebDefender, Webthority, 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 document are property of their respective owners.

Disclaimer

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.

Back to Top