Hello all Toad Data Modeler users,

As  you may have noticed, the new version 3.4.14 has brought a perfectly new wizard – the Sync & Convert Wizard.
This wizard has replaced the Convertor dialog that allowed you to compare  and merge models, generate alter scripts and generate alter reports.  All these operations are now available in the wizard too, so, this hasn’t changed. However, there are many other significant changes  that you have definitely noticed and which, we hope, you like.

In this series, I’d like to compare the new Sync & Convert Wizard with the old Convertor, show you the differences  and emphasize the advantages of the changes we made.
Let’s start with two most discussed functionalities that were available in Convertor but are not available in the new wizard.

Convertor
1. It was one dialog (one form) for all the actions.
It might have appeared as advantage but in reality it was a bit different as we learned from your feedback with which we had to agree finally. The Convertor form was not intuitive, but complicated and confusing. Your feedback was clear: You prefer a better GUI to a powerful but hard to understand functionality.

2. Model comparison and merge of different database platform was possible.
Again, it may have sounded like a great thing. The reality was different.  There are many differences between databases - different types of objects, constructions that are possible in one database are not possible in another database etc. Unfortunately, via the Convertor form we were not able to care for all the exceptions, which sometimes resulted in inconsistent final model (after model merge).
Your feedback was clear:  You prefer a stable and clear  solution with less functions to unstable Convertor with many functions.

So, as we always listen to advice and requirements of our users, we have come up with the new Sync & Convert Wizard.
We changed the GUI, partially re-wrote the code that handles generation of alter scripts in order to make this feature more stable, and improved the performance.
The new Sync & Convert wizard is now more user-friendly, clearer,  faster and easier to use and understand. However, simplification of the GUI has brought some limitations.

Limitations of the new Sync & Convert Wizard

•   If you want to perform two actions, e.g. update a model and also generate alter script, you have to use the wizard twice.
•   If you want to compare two models of a different database platform, you have to do model conversion first and then you can compare the two models, now of the same database platform.
•   If you want to compare a logical model with physical model, you have to convert the model to physical (or logical)  and then compare two logical or two physical models.

We believe that in these cases, it is not a problem to use the available solutions (or workarounds if you want).
At the moment we do not plan to implement the functionality of model comparison of different db platforms back. We definitely agree with you – we’d rather work with a stable and clear wizard  with less functions than with unstable and complicated Convertor with many functions.

Next time we will go through standard scenarios and compare the old Convertor dialog with the new Sync & Convert Wizard.

If you have any comments or questions, please do not hesitate to write us – here or post a new thread to the Modeling community forum.

Regards,

Vladka + Vaclav

Hello Toad Data Modeler users,

I am pleased to announce the new release of Toad Data Modeler version 3.4.14.
This version brings great new features and enhancements. Please see their brief list below.

============
New Features
============
General:
- Support for DB2 LUW 9.5
- New Sync & Convert Wizard for model conversion, model merge, alter script generation, model compare  and alter report generation.
- Alter script for MySQL 5.0 and MySQL 5.1, PostgreSQL 8.1, 8.2, 8.3, DB2 UDB 8, DB2 v9, DB2 v9.5  database
- Import from DDL script of MS SQL Server 2005 and 2008, MySQL 5.0 and 5.1, DB2 UDB 8, DB2 v9, DB2  v9.5 database
- Naming Conventions allowing you to:
   a) Define your own rules for physical names of objects.
   b) Synchronize caption (logical name) and name (physical name) of objects of your model.
   c) Verify whether the physical names of objects match the naming convention rules.
- Support of macros (select Macros on the main menu)

More information on this release can be found at:
http://modeling.inside.quest.com/thread.jspa?threadID=18630&tstart=0

We look forward to your feedback!

Regards,

Vladka + TDM Team

Hello,

I’m pleased to announce that another BETA version has been released.
The Beta 3.4.10.2 brings great new features such as for example naming conventions, perfectly new Sync & Convert Wizard, alter scripts for DB 2 db and LIVE Reverse Engineering for all supported databases! 

=============================
New Features and Enhancements
=============================
* Naming Conventions
* Sync & Convert Wizard for model conversion, model merge, model compare and alter script generation
* Alter scripts for DB2 UDB 8, DB2 v9, DB2 v9.5
* LIVE RE for the following databases: MS SQL Server 2000, 2005 and 2008, MySQL 5.0 and 5.1, Sybase ASE 12.5 and 15,  PostgreSQL 8.3, 8.2, 8.1, DB2 UDB 8, DB2 v9 and DB2 v9.5.
* Reports: Watermarks in RTF and PDF reports for physical and logical models.
* New option in the Options dialog: Print Gradient, Save Passwords with Aliases, Message Explorer Log Path, Sync and Convert Log Path
* GUI: Pop-up menu on tabs of Designer and Workspaces with options Move Tab Left, Move Tab Right, Close Other Tabs, Close
  * plus other enhancements and bug fixes.

=============
Documentation
=============
Complete list with detailed description can be found at:
http://modeling.inside.quest.com/entry.jspa?externalID=2933&categoryID=29

Naming Conventions PDF document:
http://modeling.inside.quest.com/entry.jspa?externalID=2932&categoryID=159

New Sync & Convert Wizard PDF document:
http://modeling.inside.quest.com/entry.jspa?externalID=2931&categoryID=159

New BETA version movies:
http://modeling.inside.quest.com/kbcategory.jspa?categoryID=273

=============
BETA Download
============= 
Download the new Beta from:
http://modeling.inside.quest.com/ann.jspa?annID=150

We look forward to your feedback!

Regards,

Vladka & TDM Team

Hello,

I’m pleased to announce that another BETA version has been released.
Toad Data Modeler 3.4.2.6 brings great new features, many enhancements and also bug fixes. Please see their brief list below.

=============================
New Features and Enhancements
=============================
* Alter script for PostgreSQL 8.1, 8.2, 8.3 database
* Import from DDL script of MS SQL Server 2005
* Support of macros (see the new item Macros in the main menu)
* Significant enhancements in Convertor that is now: faster, more stable, more clear (one direction conversion - Model 1 => Model2), with progress bars and a new button Refresh Necessitated Items.
* PDF and RTF Alter reports for physical and logical models
* Many GUI improvements:
   - Possibility to select colors for attributes (Settings | Options | Physical Model | Entity tab | Attribute Colors area)
   - Fit to Screen icon on the toolbar
   - Highlighting a relationship line on the Workspace when you select caption of the relationship.
   - Automatic wordwrap in object Note
   - Autolayout after option Fill Parent and Child Objects of entities
   - and more.
* Bug fixes in Convertor and Oracle, Sybase, MS SQL Server and MS Access databases.

=============
Release Notes
=============
Complete list with detailed description can be found at:
http://modeling.inside.quest.com/entry.jspa?externalID=2793&categoryID=29

=============
BETA Download
============= 
Download the new Beta from:
http://modeling.inside.quest.com/ann.jspa?annID=150

We look forward to your feedback!

Regards,

Vladka & TDM Team

Hello Toad Data Modeler users,

I am pleased to announce the new release of Toad Data Modeler 3.3.8.11.

Version 3.3.8.11 is a patch to version 3.3.7.22. It brings several bug fixes, particularly fixes for alter script generation. 
Their complete list can be found in the Release Notes document available at:
http://www.quest.com/Toad-Data-Modeler/release-information.aspx

==================
Installation Guide
==================
There is one installation package for Commercial and Trial version of Toad Data Modeler.
Please read the Installation Guide.pdf document carefully before you install Toad Data Modeler.

Limitations of trial version:
- 15 -day trial period,
- multiple features limited to a maximum of 25 entities*.

The Installation Guide is available on the Download page.

*Note: Information on limitations of Trial version is also available at:
http://modeling.inside.quest.com/ann.jspa?annID=241

===============
Download/Update
===============
Download Toad Data Modeler 3.3.8.11 from:
http://www.quest.com/common/registration.aspx?RequestDefID=10037
or via the support.quest site at:
https://support.quest.com

==========================
Purchase and Support Links
==========================
Visit Quest’s online store:
http://info.quest.com/buyToadDataModeler

Get Support:
For technical questions contact Technical Support at:
http://www.quest.com/support/

Quest Software Offices:
http://www.quest.com/about/about_us.asp

=======================
BETA Testing Invitation
=======================
Last week a new BETA 3.4.1.4 was released. The new BETA brings:
* Support for DB2 LUW 9.5
* Alter script for MySQL 5.0 and MySQL 5.1 database
* RTF  reports for logical model
and much more.

Please read the BETA release announcement for more details:
http://modeling.inside.quest.com/thread.jspa?threadID=9239&tstart=0

Let me invite you to download BETA and test new and enhanced features. Your feedback is greatly appreciated!

Thank you for your co-operation and support!

Enjoy the new version 3.3.8.11!

Regards,

Vladka & TDM Team

Hello,

I’m very happy to announce the release of Toad Data Modeler 3.4.1.5. BETA.
This Beta brings new features and many fixes and enhancements. Please see their brief list below.

=============================
New Features and Enhancements
=============================
* Support for DB2 LUW 9.5
* Alter script for MySQL 5.0 and MySQL 5.1 database
* RTF  reports for logical model
* Possibility to generate HTML, RTF, PDF reports for PER model and HTML, RTF reports for LER model only for the selected Workspace
* Possibility to generate alter report in RTF and PDF format
* Propagation of attributes via foreign keys - possibility to set it up for your models.
* Logical model - Model Properties option available in Model menu or context menu in Model Explorer or Application View
* XSL Transformation - Possibility to save XSD file directly from the XSL Transformation dialog
* fixes for alter script generation, GUI and particular databases

For more details, please read the BETA release announcement at:
http://modeling.inside.quest.com/thread.jspa?threadID=9239&tstart=0

=====================
IMPORTANT INFORMATION
=====================
Beta 3.4.1.5 requires that you are running a commercial or trial copy of Toad Data Modeler. You need to have a  valid license key for the commercial or trial copy of Toad Data Modeler to be able to run the BETA.

We look forward to your feedback!

Regards,

Vladka & TDM Team

Hi,

In part two of the XSLT Reports series, I will explain you how to define items that will be displayed in GUI. You will learn how to define default Description, file name, suffix and also how to define parameters and other settings.

See below a new XSL template created for one of our community members.

And this way your definitions will be displayed in Toad Data Modeler.

Let’s continue with the XSLT structure.
In the stylesheet element, you can see definition of standard XSLT namespace plus two additional namespace definitions. The first additional namespace is xmlns:tdm="http://www.quest.com/toad-data-modeler", used for TDM related items, the second additional namespace is xmlns:msxsl="urn:schemas-microsoft-com:xslt", used only when JavaScript function needs to be executed during XSL Transformation.

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:tdm="http://www.quest.com/toad-data-modeler"
xmlns:msxsl="urn:schemas-microsoft-com:xslt">

The Stylesheet element is followed by several TDM related elements.

<tdm:description>Output contains Relationship name, parent entity and child entity names and parent and child attribute names. You can change ListSeparator as well as AttributeSeparator parameters. ListSeparator separates CSV values, AttributeSeparator separates attribute names (relationship created using PK of multiple columns.) </tdm:description>
<tdm:caption>Relationships (CSV)</tdm:caption>
<tdm:default-filename>relationships</tdm:default-filename>
<tdm:default-suffix>csv</tdm:default-suffix>
<tdm:db-platforms>
<tdm:db-platform>all</tdm:db-platform>
</tdm:db-platforms>

• tdm:description - use this element to describe your XSLT. The content will appear in GUI, see the screenshot above.
• tdm:caption - allows you to name your XSLT. Whatever you write into this element, it will appear in combo-box.
• tdm:default-filename - gives you the possibility to specify a default name for output.
• tdm:default-suffix - hmmm. It is not very hard to guess what this stands for, isn’t it?
• tdm:default-filename - gives you the possibility to specify a default name for output.
• tdm:db-platforms - here you can see db-related restriction.
  The following definition means that the template is valid for all models created for all target databases.

  <tdm:db-platforms>
  <tdm:db-platform>all</tdm:db-platform>
  </tdm:db-platforms>
  

  This way you can define restriction and say to TDM that the XSLT should be available only for Oracle models.

  <tdm:db-platforms>
  <tdm:db-platform>OR9</tdm:db-platform>
  <tdm:db-platform>OR10</tdm:db-platform>
  <tdm:db-platform>OR11</tdm:db-platform>
  </tdm:db-platforms>
  

  What happens if you create a model for MS SQL Server and open the XSL Transformation dialog? Templates for Oracle model will not be loaded and will not appear in the combo-box.

Now see section 4 in the screenshots. Top-level parameters defined using standard XSLT instructions will appear in GUI. This way you can define parameters before you transform source to ouptut.

<xsl:param name="ListSeparator" select="," />
<xsl:param name="AttributeSeparator" select=";" />

That’s all for now. If you want to use the XSLT template, have a look at the following page:
http://modeling.inside.quest.com/entry.jspa?externalID=2575&categoryID=407

Have a nice day,

Vaclav

Hi,

I am going to write several articles related to generation of customized outputs from Toad Data Modeler. I hope you will find them useful and informative - and maybe you will get some inspiration for making customized templates. In the series you will find out:

• How to generate simplified XML files
• Where to get XSD file that describes structure of simplified XML
• How to create new XSLT file and where to put it
• How to define default file name and default suffix for outputs
• How to define Name and Description of your templates
• How to create parameters that will appear in GUI
• and finally an example of XSLT file that generates XSD from an Oracle model

At the end of this article you will find out that there is an easy way how to e.g. reverse engineer a database system and generate XSD schema for all reversed tables.

Let’s start with basic information and explanations. The current version of Toad Data Modeler allows you to generate detailed report via standard Model | Report… feature. However, there is also another possibility how to generate reports or other outputs. Click Model | Reports / XSL Transformation…. to see the other possibility. A dialog with predefined report types will open.

We can see there that using the XSL transformations we can generate HTML, CSV or XML files. What if we want to generate XSD, SVG or for example XAML code? Is it possible? - Sure! The XSL transformation allows us to work with data stored in our models without the necessity to study internal structure, scripting etc. If you are familiar with XML, xPath and XSLT, then it will be very easy for you to iterate tables, columns and other data and generate output you need to generate.

How it works: for every XSL transformation you need a source (XML file), a template (XSLT file) and a way how to do the transformation. Output type can be specified in the XSLT file.

In Toad Data Modeler, there is GUI that allows you to locate XSLT templates. But..where is the source? Where is XML? Good questions - On the XSL Transformation dialog, click the More button. The dialog will become twice large than it was and you will see there buttons Save XSD files as… and Show XSD File. Click the Show XSD File button. If XSD files are associated with some third party application (e.g. Visual Studio), then the file will open in the associated application. XSD file describes structure of “simplified XML”. In other words, it describes structure of our source. OK, how to generate a real XML file for testing purposes etc.? In the XSL Transformation dialog, select the Complete XML (XML) item from the first combo-box.

Then click Transform. This way you can geneate XML file. We call it “simplified XML”, because, as you probably know, all files created in Toad Data Modeler are in XML format. Save your model as *.TXP file and edit the file in notepad. You will see XML file structure. What’s the difference between simplified XML and standard TXP file? - In the amount and form of information. For example, in simplified XML you will find data types named logically, in TXP the same information is represented by GUID code. Also, simplified XML doesn’t contain information related to workspaces, generators and other data required by Toad Data Modeler application. That’s why you can get oriented in simplified XML much faster.

In next article I will explain how to create a new XSL Template and describe structure of XSL Templates used in Toad Data Modeler. Now I’d like to show you that using one relatively simple XSL template we can generate XSD for Oracle models. Download the “XML Schema (XSD) - Elements” template from the following location:
http://modeling.inside.quest.com/servlet/KbServlet/download/2574-102-4883/xsd-elements.zip

and put it to the same folder where system XSL templates are stored. Open the XSL Transformation dialog and see value in XSL File Location.

Then open any Oracle model or reverse engineer your existing Oracle database structure, click Model | Report / XSL Transformation… item and see a new item in the first combo-box. Click More, define parameters and then click Transform to generate the output and see the result.

The output can be visualized also in Visual Studio (considering column names are unique).

Regards,

Vaclav

Hi,

As you probably know, Toad Data Modeler allows you to convert a model from one database system to another. You can reverse engineer a physically existing Oracle database structure and convert your model to PostgreSQL or MS SQL Server model etc. Tables, relationships, columns and data types will be converted automatically together with logical information. Other database specific items like Triggers, Stored Procedures, Views etc. can be converted too, however, if you select such object types they will be automatically commented out in your newly created model. Why? Because you can write SQL code for Views or Triggers etc. that will work in Oracle, but won’t work in MS SQL Server. And you can face similar problems after converting Oracle 9 model to Oracle 11 model.

How can we easily remove comments (I mean automatically added comments) from the newly created model? - Via scripting!

See below a script that removes comments from newly created Oracle 11g model (converted from Oracle 10g model.)

function main()
{
var app = System.GetInterface('Application');
var Model = app.Models.GetObject(0);
//... parameter in GetObject determines with which model the script should work.
//0 = first model listed in the Application View, 1 = second model listed in the Application View etc.
var i, j, k;
var Entity, Trigger, View, Procedure, Function, CheckConstraint, Attribute, Domain, Default;

Model.Lock();

//Triggers, CheckConstraints
for (i=0; i<Model.Entities.Count; i++)
{
Entity = Model.Entities.GetObject(i);
for (j=0; j<Entity.Triggers.Count; j++)
{
Trigger = Entity.Triggers.GetObject(j);
Trigger.SQL = RemoveCommentChars(Trigger.SQL);
}
for (j=0; j<Entity.CheckConstraints.Count; j++)
{
CheckConstraint = Entity.CheckConstraints.GetObject(j);
CheckConstraint.SQL = RemoveCommentChars(CheckConstraint.SQL);
}
for (j=0; j<Entity.Attributes.Count; j++)
{
Attribute = Entity.Attributes.GetObject(j);
for (k=0; k<Attribute.CheckConstraints.Count; k++)
{
CheckConstraint = Attribute.CheckConstraints.GetObject(k);
CheckConstraint.SQL = RemoveCommentChars(CheckConstraint.SQL);
}
}
}

//Domain CheckConstraints
for (i=0; i<Model.Domains.Count; i++)
{
Domain = Model.Domains.GetObject(i);
for (j=0; j<Domain.CheckConstraints.Count; j++)
{
CheckConstraint = Domain.CheckConstraints.GetObject(j);
CheckConstraint.SQL = RemoveCommentChars(CheckConstraint.SQL);
}
}

//Defaults
for (i=0; i<Model.Defaults.Count; i++)
{
Default = Model.Defaults.GetObject(i);
Default.Value = RemoveCommentChars(Default.Value);
}

//Views
for (i=0; i<Model.Views.Count; i++)
{
View = Model.Views.GetObject(i);
View.SQL = RemoveCommentChars(View.SQL);
}

//Procedures
for (i=0; i<Model.Procedures.Count; i++)
{
Procedure = Model.Procedures.GetObject(i);
Procedure.SQL = RemoveCommentChars(Procedure.SQL);
}

//Functions
for (i=0; i<Model.Functions.Count; i++)
{
Function = Model.Functions.GetObject(i);
Function.SQL = RemoveCommentChars(Function.SQL);
}

Model.UnLock();
}

function RemoveCommentChars( strValue )
{
return strValue.replace(/^--/g,"").replace(/\n--/g,"\n");
}

How to run the script in Toad Data Modeler? Do the following, please:

• Enable Expert Mode - click Settings | Options and in section General, enable the Expert Mode checkbox.
• Click Tools | Scripting Window to open a form from where the script will be executed.
• Copy and paste the script to the main area.
• Click the Execute button (green arrow icon).

Regards,

Vaclav & TDM team

Hello all,

How are you doing in the new year? I do believe that very well.
Let me wish you good health and good all year 2009.

Our team is again fully at your disposal, ready and looking forward to your posts in the Modeling community. Please feel free to ask questions, post suggestions, requirements etc. We listen to your ideas and are pleased to help.

Let me summarize current state regarding Toad Data Modeler:

* Latest version - Toad Data Modeler 3.3.7.22 is available at:
http://www.quest.com/common/registration.aspx?requestdefid=10037

Note: We’ve been reported some troubles during the download by some users. Nevertheless, whenever we check it out, it works fine. So, if you encounter any problem during the download, please do not hesitate to contact the Quest Support team at: support@quest.com.
You can also call them, see the numbers at: https://support.quest.com/SUPPORT/index?page=contactSupport.
Thanks.

* Flash movies introducing new features/enhancements in latest TDM version can be found at:
http://modeling.inside.quest.com/kbcategory.jspa?categoryID=158

* Beta program continues
We are working at a new Beta version. At the moment no BETA is available as the official TDM version 3.3.7.22 is the most up-to-date version.

* Modeling community contest
So far, two third generation i-Pods and four Amazon Gift certificates have been given! The Modeling community contest continues also in the new year. New contest conditions will be announced soon. (Next time, you can be the winner.  ).

Well, I hope I mentioned all information that is important and helpful for you. In any case, if you have any questions, please do not hesitate to write.

We look forward to hearing from you.

Have a nice day.

Take care,

Vladka + TDM Team