Version 3.3.5
Release Notes
November 20, 2008
| Known Issues | ||||
| For More Information |
Quest Software's Toad Data Modeler helps organizations create, maintain and document their database systems with an easy-to-use graphical interface into new or existing database structures. Toad Data Modeler enables users to reverse engineer database structures, update models, design and generate SQL, compare models and generate alter scripts, create HTML or RTF reports, in addition to versioning of database designs and creation of to-do lists.
Toad Data Modeler 3.x represents a major increase in the capabilities in comparison to Toad Data Modeler 2.x. It's a much more powerful database design tool bringing users many new efficient and useful features that are accompanied by completely new, clear and intuitive user interface.
Updates to Toad Data Modeler 3.3.5:
Reverse engineering
- Support for Oracle 11g client
- Unicode support for Oracle/Direct connection to MySQL (For MySQL db, is not necessary to have the appropriate database library (libmySQL.dll) now.)
Enhanced MS SQL 2005
- Modifications in generation of Drop Clustered Index. - When Clustered Index is dropped, it will be automatically set to which Filegroup/Dataspace and FilestreamFilegroup (FilestreamFilegroup is only for MS SQL Server 2008) to which a table will be moved (according to the definition in the table).
- New checkboxes "Statistics NoRecompute", "Allow Row Locks", "Allow Page Locks" on tab "Index Options" in Index Properties dialog and Key Properties dialog.
Checkbox IGNORE_DUP_KEY has been renamed to "Ignore Duplicate Key Values".
These new properties are loaded during reverse engineering also to Views to tab "Create Index" (previously, these properties were not loaded there).
GUI Enhancements - M:N Relationships in physical model
- Find
In Script option (Edit menu)
This option allows you to find particular text in scripts (e.g. exact row
and column in particular script in particular package, Expert mode must be
enabled).
- Information on where a file with the selected package (.txg file) is
saved.
Package Explorer | Properties dialog of the selected package |
General tab | Package File box. Click the icon next to the box to
get to the location straight away.
- Filter on packages in Package Explorer (Filter the packages by database
systems.)
- Commit and Save option in Script Editor
This option allows you to commit changes made in the script and save the
particular package at the same time from the Script Editor.
- If an error occurs and it is an error in script, the script will open and particular problematic line in the script will be highlighted.
New Features in Toad Data Modeler 3.3.5:
New Features and Enhancements (in comparison with MS SQL Server 2005):
- New data types of type DATE: date, datetime2, datetime2(x), datetimeoffset, datetimeoffset(x), time, time(x).
- New spatial data types: geometry, geography.
- Other new data types: hierarchyid.
- Rowversion is generated instead of data type timestamp (they are synonyms and it is recommended to use rowversion).
- Possibility to define attribute as Column Set in entity. - For this purpose, there is a new data type "Xml Column_Set" in the Attribute Properties dialog. (Similar as when you select auxiliary data type Computed Column for Computed Column.)
- Possibility to set Data Compression in the Entity Properties form. - See the new "Data Compression" tab where you can set Data Compression either for all table (combo box "Compression Type") or for particular partitions. (To accomplish this, it is necessary to select checkbox "Set Compression Type on Individual Partitions" and fill out the box in the "Set Compression Type on Individual Partitions" area. See the auxiliary combo box Compression Type for Partition", box "Partition Number" and button "Add to List").
Note: To load Data Compression defined in a table during reverse engineering, it is necessary to select the new checkbox "Load Data Compression for Tables" in the Reverse Engineering Wizard (it is selected by default).
- Possibility to define Filestream Filegroup in the Entity Properties form. (See a new combo box on the General tab, Data Space area.) In tables that are not partitioned, you can make selection from a new list FilestreamFilegroup. In partitioned tables, you can make selection from a new list PartitionScheme.
Note: To be able to define Filestream Filegroup, the database requires columns with the Filestream property.
- New Filestream checkbox in the Attribute Properties dialog. This checkbox is available only for columns of varbinary(max) type.
Note: Database requires a column of type unique identifier and with ROWGUIDCOL and NOT NULL set. This column (only this one) must be used in Unique or PK constraint that is generated inside a table definition. User has to define such a column on his own.
- New checkbox Sparse in the Attribute Properties dialog. This checkbox is available only for some data types. (It is not available for these data types: geography, geometry, image, ntext, text, timestamp, user-defined data types, computed column).
- Possibility to define Filtered Index. See the new box "Expression for Filtered Index (WHERE)" in the Index Properties dialog.
- Possibility to define Filestream Filegroup in Clustered Index (see the new combo box in the Index Properties dialog | General tab | Data Space area). In tables that are not partitioned, you can make selection from a new list FilestreamFilegroup. In partitioned tables, you can make selection from a new list PartitionScheme.
Note: To be able to define Filestream Filegroup, the database requires columns with the Filestream property in a table.
- Possibility to define Data Compression in the Index Properties dialog. - See the new "Data Compression" tab where you can set Data Compression either for all index (combo box "Compression Type") or for particular partitions. (To accomplish this, it is necessary to select checkbox "Set Compression Type on Individual Partitions" and fill out the box in the "Set Compression Type on Individual Partitions" area. See the auxiliary combo box Compression Type for Partition", box "Partition Number" and button "Add to List").
Note: To load Data Compression defined in index during reverse engineering, it is necessary to select the "Load Index Options" checkbox in the Reverse Engineering Wizard (it is selected by default).
- Parameters specific for XML Index are available on a new tab "Secondary XML Index Parameters". (In previous MS SQL versions, it was on tab General.)
- Support for new Spatial Index. - It can be defined via standard Index Properties dialog, however there is no use filling out some boxes in the dialog (similarly as for XML Index). Added new tab "Spatial Index Parameters" with parameters determined for Spatial Index (Bounding Box can be/must be filled out only for Geometric Spatial Index, which is for Index of column with data type Geometry).
Notes:
Now index can be generated as normal (relational) index, primary XML index, secondary XML index and Spatial index. What index will be generated is selected automatically by the following conditions (particularly by data type of particular attribute):
If index has only one column and this column is of XML type, XML index will be generated. For the XML index it is searched whether the box "Primary XML index..." is filled out. If it is filled out, then it is a secondary XML index. Otherwise it is a primary XML index.
If index has only one column and this column is of Geometry or Geography type, Spatial index will be generated then.
Database requires a primary key in a table if Spatial Index exists. User has to arrange it on his own.
- Possibility to set Data Compression in the Key Properties dialog. - See the new "Data Compression" tab where you can set Data Compression either for all key (combo box "Compression Type") or for particular partitions. (To accomplish this, it is necessary to select checkbox "Set Compression Type on Individual Partitions" and fill out the box in the "Set Compression Type on Individual Partitions" area. See the auxiliary combo box Compression Type for Partition", box "Partition Number" and button "Add to List").
Note: To load Data Compression defined in index during reverse engineering, it is necessary to select the "Load Index Options" checkbox in the Reverse Engineering Wizard (it is selected by default).
- Possibility to set up Filegroup (combo box "Filegroup") and Stoplist (the "Stoplist" area with the "OFF" checkbox and the "Stoplist" combo box) in the Entity Properties form and View Properties dialog | Fulltext Index tab.
- Removed parameters "On Filegroup" and "In Path" from Fulltext Catalog (such parameters are used only in MS SQL Server 2005).
- Possibility to define new "User-Defined Table Type" in User Data Types. (Till now there was only a place for "CLR User-Defined Type".) To determine the type, use the new "Type" combo box. (In the combo box, you can select CLR for "CLR User-Defined Type" and TABLE for "User-Defined Table Type").
Notes:
The definition of "User-Defined Table Type" should be defined to the "User-Defined Table Type Definition" box on tab General. This box will appear only if the TABLE Type is selected. To the box, write the text that is defined in syntax in brackets after AS TABLE, for example "a int, b int" (without the quotation marks).
Although this type is available in attributes, it is not possible to use it there.
- Checkbox "Generate SQL Only" is available in User Data Types. If this checkbox is selected, the SQL tab will appear. It the checkbox is clear, the SQL tab will be hidden.
- Function of type Aggregate can now have more input parameters separated by comma (should be written to the "List of Arguments" box).
- Function of type CLR Table-Valued can now define Order (the "Order (List of Column Names)" box) where column names should be separated by commas.
- Function supports the Read-only property at parameters of type User-Defined Table Type. (No visual changes can be seen.)
- Procedure supports the Read-only property at parameters of type User-Defined Table Type. (No visual changes can be seen.)
- New list/object "FilestreamFilegroups" in Physical Model Explorer. - Similarly to Filegroups, FilestreamFilegroups work in Toad Data Modeler 3.x only as a list. During script generation, the FilestreamFilegroups definition is not generated and during reverse engineering the definition is not loaded either (only names are loaded).
- New list/object "Stoplists" in Physical Model Explorer. - Similarly to Filegroups, Stoplists work in Toad Data Modeler 3.x only as a list. During script generation, the Stoplist definition is not generated and during reverse engineering the definition is not loaded either (only names are loaded).
Support of PostgreSQL 8.3
- New data types: tsvector, tsquery, txid_snapshot, uuid, xml.
- User Data Types - Possibility to define "Enumerated Type" - see the new data type in the Type box and new tab "Enumerated Type" where this data type
should be defined (example: 'item1', 'item2', 'item3').
Note: In previous version, it was possible to define only Composite Type and Base Type.
- User Data Types, the Base Type tab - two new parameters "Type Modifier Input Function" and "Type Modifier Output Function" for support of modifiers.
Thanks to these new parameters, Base Types can also use modifiers.
- User Data Types of the Base Type tab (User-defined type in manual) can have (for example while using attributes) modifiers - e.g. user_type(20,5). In
previous version, modifiers could have only inbuilt/basic data types (types varchar(40) or number(20,5)).
Notes:
* When you select the Base Type from the Type box, new boxes "Name of Parameter" and "Default Value of Parameter" will appear. "Name of Parameter" - when
you select an attribute with selected User Data Type, a box with an option to define parameters will appear.
* "Default Value of Parameter" is just an instrument and is not generated.* When there is a possibility to define more modifiers for a Base Type, such User Data Type used in an attribute will be written to appropriate parameter in the Attribute Properties dialog e.g. as: "30,20,5". During reverse engineering only Typmod will be loaded. Typmod is a number where the parameters are coded. If user needs to decode the Typmode during reverse engineering, function ParseTypmod(Length, format_type) in script REDataMigratorDBPG83 should be overwritten.
If one modifier is used during reverse engineering, everything will be loaded properly.
* Modifiers of Base Type can be used in: attributes, composite type attributes, dictionary types (in PostgreSQL called Domains) and in TDM domains.
- Index Properties dialog | Items tab | new parameter ASC / DESC for items of columns.
- Index Properties dialog | Items tab | new parameters NULLS LAST / NULLS FIRST for items of columns. To use the parameters, see the Items tab, Expression box and select "Generate Expression" checkbox. If parameters NULLS LAST / NULLS FIRST are not selected by default, expression is used during reverse engineering. In this case, e.g. the following will be written in Expression instead of selection of single columns: a, b NULLS FIRST, d DESC, f DESC NULLS LAST.
- Function Properties dialog - new parameters Cost, Rows, Set. Set parameter can be defined by the ALTER FUNCTION command written to After Script section. Here it will be also loaded during reverse engineering. Example of ALTER FUNCTION:
ALTER FUNCTION myfunc(integer, integer) SET DateStyle=postgres, dmy;
Notes:
* During script generation, default values of parameters Cost and Rows are not generated (default for Rows is 1000, default for Cost is 1 for c/internal language and 100 for other languages).
* Note from a manual: Rows is only allowed when the function is declared to return a set.
- Possibility to use array for composite type and new enum type. (Array for domain type is not supported yet.)
What is not supported in PostgreSQL 8.3:
- CREATE OPERATOR FAMILY
- Text Search commands: CREATE TEXT SEARCH PARSER, CREATE TEXT SEARCH CONFIGURATION, CREATE TEXT SEARCH TEMPLATE, CREATE TEXT SEARCH DICTIONARY.
The following is a list of issues addressed and enhancements implemented in this release of Toad Data Modeler.
|
Feature |
Resolved Issue |
CR # |
| Licensing |
Toad Data Modeler Trial version - new dialogs with information about remaining trial days and key expiration. Screenshots of the dialogs and other details can be found in the Installation Guide pdf document that is included in the Toad Data Modeler installation package. |
54 038 |
| There was a problem with license where the Site Message contained special characters. Solution: License file is coded for Unicode. |
50 873 |
|
|
General |
Problem to save a model after RE when an SQL of the model contained CDATA
command. (Immersed CDATA commands are not allowed.) Solution: Invalid CDATA nodes are coded via 64Base encoding algorithm. |
54 442 |
| "Error during consolidation" during startup of TDM when only the following databases were installed: MS SQL 2005, MS SQL 2008 and MySQL 5.0. Fixed. |
54 386 |
|
|
Option to save models as a formatted XML file. (Settings menu | Options | General | Save Models as Formatted XML Files checkbox) |
53 563 |
|
|
Incompatibility – We do not recommend to open and save models created in
developmentally higher version of Toad Data Modeler (e.g. 3.3.x) in lower
version of Toad Data Modeler (e.g. 3.2.x). Since version 3.3.5 a new message will occur when you attempt to open such a model in a lower version. Example wording: "Model 'MyModel' you are attempting to open in this product version (version 3.3.5.5) was last saved in a developmentally higher version of the product (version 3.3.5.6). If you save the model in this lower product version (version 3.3.5.5), some information of the model can get lost. Would you like to open the model anyway?" |
51 802 |
|
|
Import from Toad Data Modeler 2.x |
Logical names in MS Access models were not imported. Problem fixed. |
51 256 |
| Import of Views - The 'Generate' property of views migrates now. |
37 366 |
|
|
During import from TDM 2.x, TDM 3.x names check constraints with unique default names within an entity now (same as during modeling). (Until now, it was only within an attribute.) The result of this is that check constraints do not have same names. |
n/a |
|
| Physical Modeling | Domains, schemas, dictionary types when copying entities. There was a bug – a copy of domain was made too, which was an incorrect behavior. Fixed. | 52 590 |
| Support for PostgreSQL 8.3 | 47 651 | |
| Support for MS SQL Server 2008 | 46 927 | |
| Support for MySQL 5.1 | 39 246 | |
|
SQL/DDL Script Generation |
A new message protecting you from overwriting Script.sql file will appear. |
46 076 |
| UNSIGNED item did not refresh properly in generated SQL code after the data type change (from SmallInt to Char). Fixed. |
44 149 |
|
|
Preview function before you save the generated SQL code. See the DDL Script Generation dialog | Show Preview before Save. |
35 763 |
|
| Alter Script Generation |
Settings defined in DDL Script Generation dialog are taken for the alter script
generation (quotations, schema prefix, primary key inside or outside
statements). Note: It is recommended to set up the same DDL script generation settings for both models that are being compared in the Convertor. |
53 876 |
| Alter scripts for MS SQL 2005. |
44 470 |
|
| Logical Modeling | LER to PER conversion: Cycled relationships will be ignored during LER to PER conversion and will not be converted. A message informing about this will be written in Message Explorer. |
54 457 |
| LER to PER conversion: Cardinality was not converted properly if Mandatory specification in logical model between left and right side was changed. Fixed. |
51 804 |
|
| Valid Values for Char data type. |
37 052 |
|
| Model Merge | Stack overflow error during model update/merge/conversion fixed. |
53 873 |
| New attributes are added to the end of the attribute list in entity and Entity Properties form during model merge/model update. |
53 674 |
|
| Simple Model Merge – Original model did not unlock after the conversion process. Bug fixed. |
51 698 |
|
| Error during consolidation "TUserGroup.ReplaceConsolidatedObject" fixed. |
51 215 |
|
| Convertor, Comparator | Access violation error during LER to PER conversion into existing physical model. Fixed. |
53 439 |
| Default display of icons in Convertor was not correct (there was one line misstep). Problem fixed. |
52 642 |
|
| Possibility to name notes and pair them by name during model compare. |
47 006 |
|
| HTML/RTF Reports |
Report settings (path, layout, options) defined in the Report Wizard are saved
with a model. (There was a bug – only layout was saved.) |
47 242 |
| Cancel button works properly for interrupting the process of report generation. After you click Cancel, a dialog ‘Report was not generated’ will appear and the process will be interrupted. |
35 251 |
|
| Version Manager | After the option Show Version (only to read) you can save the version as a txp or txl file. In the Save Version as dialog, a path to the Models directory is selected by default. |
47 426 |
| Possibility to check out/check in multiple versions at one jump. |
44 765 |
|
| Description of model defined in Model Properties is transferred automatically when you add the model to Version Manager. It is also possible to add a new description to the model (when the model already is in Version Manager). |
43 818 |
|
| List Of… opens with Version Manager. |
33 460 |
|
| GUI Enhancements | Error during copying objects with empty names (CTRL+C) fixed. | 54 774 |
| Break points of relationships renamed to Handle Points. | 54 582 | |
| Focus on Workspace preserved when you close a model. (When you have more models opened in the Application Window.) | 54 568 | |
|
Right-click a Workspace to check the renamed options: Add All Model Objects to Workspace (used to be Complete All from Model), Add Selected Objects to Workspace (used to be Complete from Model). |
54 565 | |
| Sorting of attributes in the Entity Properties form: A message to set the ordinal order appeared although the ordinal order had been set before the entity form was closed. | 54 199 | |
|
Sorting of attributes – bugs with green arrows for changing ordinal order fixed.
Current behavior: |
54 192 | |
| Delete Confirmation dialog – key shortcuts added for buttons OK (ALT+O) and Cancel (ALT+C). | 53 949 | |
| Settings | Options | General | Icon Theme – the box was editable, which was not correct. Fixed. | 53 944 | |
| When you were selecting an item from the Object Navigator box, pressing the Esc key closed the dialog. Now Esc key closes only the unrolled Object Navigator box. | 52 920 | |
| Wrong message "Printer doesn't support color print" appeared in Message Explorer although the printer supported color print. Fixed. | 52 873 | |
| Labels of relationship names were truncated. Problem fixed. | 52 870 | |
| During edit of Keys in an entity, an error "Cannot focus a disabled or invisible window." might have occurred. Fixed. | 52 789 | |
| ESC key did not work on tabs Descriptions, Comments, Notes, After Script etc. (tabs with MEMO component). Problem fixed. |
51 647 |
|
|
Better access to triggers with possibility to view them and edit them. Solution: See the new feature Object Viewer. |
51 379 |
|
| First workspaces is named All Items by default. |
49 122 |
|
| A Category column on the model To Do List is available. |
48 154 |
|
| Possibility to list all attributes of the model. - Object Viewer option. |
46 115 |
|
| Procedure Properties dialog | User/Schema box refreshes properly after the change of user name in the User Properties dialog. |
43 414 |
|
|
Option to select default unit of length (for page format, print settings etc.) –
either millimeters or inches. Select Settings | Options | General tab | the Select Unit of Length box. |
43 141 |
|
|
Adding new items via down arrow on your keyboard. Example: Open the Entity Properties form | Attributes tab | select the last attribute and press down arrow on your keyboard. |
38 347 |
|
| When you drag an entity on a workspace holding the SHIFT key, it moves in a straight line. |
33 555 |
|
| Oracle 11g, Oracle 10g, Oracle 9i |
User Data Type Properties dialog – enhancements for Varray Type and Nested Table
Type When you select any of these types, a new tab appears (Varray Type tab or Nested Table Type tab). There, you can see new boxes* where you write appropriate values. Press the Create Definition button and the definition will be written in the memobox below. *Note: The content of the boxes is not saved and is not used for reverse engineering, script or report generation. |
55 194 |
| New hints in memoboxes for User Data Types and Packages. |
55 194 |
|
|
Change for CHAR/BYTE of attributes.
|
55 134 |
|
| Reverse Engineering Wizard | Tables – Tables of names beginning with USLOG$ and RUPD$ that can be automatically created during creation of Materialized View are filtered in the list of tables. |
54 945 |
|
| Model Verification - Message about duplicate key constraint names includes information on entities now. |
53 997 |
|
| Users/schemas for FK indexes are generated in SQL script. |
53 241 |
|
| Package Properties dialog | SQL tab – a new function Find. (CTRL + F) |
49 133 |
|
| Oracle 11g | Reverse engineering - Attributes of only first entity were loaded. Problem fixed. |
51 218 |
| MS SQL 2008 and MS SQL 2005 | Reverse engineering – Procedures created via command “CREATE PROC” were not loaded properly. Fixed. |
54 745 |
| SQL/DDL Script generation – Schema left off unique constraint. Fixed. |
54 445 |
|
| RE Wizard | Options tab | Load Users and Groups checkbox renamed to Load Users and Roles. |
52 881 |
|
| Reverse Engineering: Comments on views and their columns are reversed. Comments on views are stored in the View Property dialog | Description tab. Comments on view columns are loaded to View Property dialog | After Script tab (if you wanto to create them during model creation, you need to enter them manually - (-- comment and/or /* comment */)). |
51 507 |
|
| MS SQL 2008, MS SQL 2005, MS SQL 2000 | Reverse engineering – Toad Data Modeler did not generate scale of decimal datatype in the return of create function. Fixed. |
54 732 |
| MS SQL 2000 | RE Wizard | Options tab | Load Users and Groups checkbox renamed to Load Roles. |
52 881 |
| MySQL 5.1, MySQL 5.0 | Reverse engineering - UniDAC component for MySQL platform. (Now it is not necessary to have the appropriate database library (libmySQL.dll).) |
53 943 |
| MySQL 5.0 | Reverse engineering – relationships were not loaded (problem occurred on MySQL 5.0.51a.) Fixed. |
52 420 |
| PostgreSQL 8.3 PostgreSQL 8.2 | Reverse engineering - Bug during RE of index when Expression box was used fixed. |
n/a |
|
PostgreSQL 8.2 PostgreSQL 8.1 |
HTML reports - Fix of function with language "c" and "internal" (Parameters of the selected language "c" and "internal" were not written out.) |
n/a |
| Documentation | Updated list of hot keys in Toad Data Modeler. |
54 446 |
The following is a list of issues known to exist at the time of Toad Data Modeler release.
|
Feature |
Known Issue |
Defect ID |
| Toad for Oracle Integration |
Toad for Oracle cannot auto-detect this new version of Toad Data Modeler (3.3.5). |
n/a
|
| Documentation |
Documentation describes PDF Reports as one of the available formats. This functionality is not yet available |
n/a
|
Toad Data Modeler 3.x allows you to open DM2 files and DMX files of Toad Data Modeler 2.x. (DMX file is a DM2 file in XML format.) This applies only to models of database systems that are supported by both applications - Toad Data Modeler 2.x and Toad Data Modeler 3.x.
It is not possible to open models created in Toad Data Modeler 3.x in Toad Data Modeler 2.x.
Do not open and resave models originally created in a higher version of Toad Data Modeler (e.g. in v. 3.3.5) in lower version of Toad Data Modeler (e.g. v. 3.1.5).
Before installing Toad Data Modeler, ensure your system meets the following minimum hardware and software requirements:
| Platform | Pentium IV |
| Memory | Minimum 256 MB |
| Hard Disk Space | 100 MB |
| Operating System | Windows 2000/XP/Vista |
| Additional Software | none |
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, Central and Eastern
Europe, Far-East Asia, Japan.
This release has the following known capabilities or limitations: Localized
support for reports in several languages will be distributed via TDM Community.
The Toad Data Modeler release package contains the following products:
Refer to Installation Guide for installation instructions.
Note: Toad Data Modeler Trial version limitations: 15 -day trial period and multiple features limited to a maximum of 25 entities.
Get the latest product information, find
helpful resources, test the product betas, and join a discussion with the
Toad Data Modeler Quest team and other
community members. Join the Modeling community at http://modeling.inside.quest.com.
| 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.
© 2008 Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this document 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.
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 |
Refer to our web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Aelita, Akonix, Akonix L7 Enterprise, Akonix L7 Enforcer, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vANALYZER, vAUTOMATOR, vCONTROL, vCONVERTER, vEssentials, vFOGLIGHT, vOPTIMIZER, vRANTER PRO, vReplicator, Vintela, Virtual DBA, VizionCore, 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.
Toad Data Modeler contains some third party components (listed below). Copies of their licenses may be found on our website at http://www.quest.com/legal/third-party-licenses.aspx.
|
Component |
License or Acknowledgement |
| Fast Memory Manager 4.78 | Mozilla Public License Version 1.1 |
| Virtual Treeview 4.3.1 | Mozilla Public License Version 1.1 |
LICENSE AGREEMENTS FOR THIRD-PARTY SOFTWARE USED TO DEVELOP Toad Data Modeler 3.x are available in the Third-Party-Licenses.rtf file that is stored in Toad Data Modeler Bin folder.
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.