You will no longer receive e-mail notifications from this forum.
Log-In to post
I prefer my history tables to be stored in separate filegroups from the current table.
As far as I know, 2016 doesn't have an easy way to define a separate filegroup with the simple history table auto-generation command WITH (SYSTEM_VERSIONING = ON ( HISTORY_TABLE = [???_HISTORY] )).
For this to work, the history table needs to be defined and created (without pk, fk and period of course) first on one file group, then the current table created on a separate filegroup with system_versioning on to attach to it.
Maybe have an checkbox under "Temporal Table Properties" to define history table separately, and with a check of the box, the ability to specify a separate file group?
It seems to me that during generating of sql script from model action, TDM is ignoring extension settings in Order of generated objects page. Example is in attachment.
As I know it worked in older version. I am forced to use beta because of other bugs which blocks me in work.
Do you know how to force TDM to take this settings in use?
After upgrading new Win10(x64) update 1607 seems Toad beta 22.214.171.124 lost ability to print. After program starts, it gives notification that "No valid printer has been found on your computer. Some of the functions related to print might work incorrectly." Trying to choose Print.. from menu results in program crash.
TDM Version: 126.96.36.199
Server: SQL Server 2014 / SQL Server 2016
On a model with 100+ tables with lot of changes (5-10 tables, new columns) "Model\Generage Change Script" includes objects which weren't selected:
Steps to reproduce:
Using 64 bit version.
The list does not seem to retain my changes. Also, it has multiple headers for the same thing (Procedures, Functions, Entities).
See screenshot below.
If make multiple cycles of "Update Model From Database..." ->...Make some changes to the model -> "Generate Change Script "-> "Update Model From Database..." TDM shows that Column Order in multi-column index got messed up.
If a column is renamed in database and you do "Update Model From Database..." it drops the old column with all custom attributes which are stored inside the model only.
It would be nice to have a way to match old and new column in UI, so it would be treated as rename w/o loss of any attributes.
I experience the similar problem with Tables, FK, PK, etc.
i have modeler 3.4 and when i try to run the new beta version, i receive a message that license key has not been found. will the beta version run with my current version?
Our customer is executing a Reverse Engineering of 4,000 objects schema and is 17 hours executing without termination.In the past the customer had some issues of out of memory in TDM 32 bits and he was expecting the issue will resolve in 64 bits
I have a parent table and a child table. The child table has a data type with N columns. One of these columns should make reference to the key of the parent table. How to do this in TOAD Data Modeler?
We are pleased to announce that we have released the first Beta build of Toad Data Modeler 6.0 64-bit edition. It is available for download here in the Beta community site. Please let us know if experience any issues with the Beta by posting to the Beta forum or replying to this thread. Thank you for your support!
I know that there much more important issues in the product, but latest beta (188.8.131.52) seems to be not compatible with a high DPI screens. Impossible to work with a 4k screen's laptop without external monitor.
I have to read with the Toad Data Modeler 184.108.40.206 a dm2 file that I suspect it was wrote in the version 220.127.116.11 but when I import with "Case Studio Model..." the error message is showed: "XML cannot be read"
How can I import this file?
My best regards
I'm pleased to announce new release of Toad Data Modeler BETA 5.2.3!
Except for a couple of bug fixes, this BETA release brings lots of improvements and changes in GUI. I'm sure you already noticed some of them in previous Beta, e.g. new lines... Nevertheless, let me announce them officialy and point your attention to them. Here's a brief list of enhancements:* Export, Import Microsoft Excel - Export/Import feature is available for active data model and the resulting XLSX file includes individual worksheets for Entities, Attributes, Relationships and Data Types for the model. There, you can add comments and notes and modify or specify other properties. The modified Excel file can be imported back to Toad Data Modeler.
To export your model:Select File | Export | Export to Excel…
To import the data back to Toad Data Modeler:Select File | Import | Import from Excel…
* New Relationship Lines Management SystemLines are right-angled only. You can move them and their parts as you need (vertically and horizontally). Anchor points are no longer fixed on entity boxes but you can alter them as you need (column to column alignment is possible now). You can add handle points (press CTRL) and this way you can select parts of line you need to delete or move.
* Snap to Objects - automatic align among objects on the workspace.When you move an object on the workspace (e.g. entity or relationship line), a light blue line will display and you will be able to align the object to other objects in ERD easily.The Snap to Objects option is on by default - see the new icon on the toolbar or Settings | Options | Graphics. There, you can turn this function off. To turn it off for a particular moment while working in your ERD, press and hold ALT Key.
* Import and Export Settings defined in the Options dialog - This option allows you to import/export the settings (particularly helpful for already defined paths) e.g. for side by side installation of TDM or to/from TDM on another PC. Also, you can restore the default settings easily. See the new buttons in the Options dialog.
* Possibility to hide Not Null and Key Marks (Object Format dialog | Entity tab) * Go to Parent, Go to Child right-click options for relationships* Button Add Workspace beside Tabs* Possibility to close X every workspaceetc.
So, do not hesitate to explore and test these new great features. We can't wait for your feedback and other suggestions (even those that might appear to be unimportant or little).Happy modeling with TDM! :)
Vladka and TDM Team
the Export/Import function to and from Excel has a bug which is acknowledged by the developers ( http://www.toadworld.com/products/toad-data-modeler/f/30/t/23520.aspx ) and fixed in the BETA version. After downloading and installing the BETA version I was able to use it for two days and now the application refuses to start and quits with the message:
"Beta version has expired. Please download the latest beta version from http://modeling.inside.quest.com"
So far I tried uninstalling and installing BETA version again, nevertheless without success.
Is there a workaround to have the BETA Version working again?
Your support is highly appreciated.
Hi our BETA users,
New Toad Data Modeler 5.4.5 BETA has just been made available for you!
Please, DOWNLOAD, try the new stuff and LET US KNOW!
Lukas & TDM Team
Can someone please confirm that Postgres is not supported as the documentation indicates?
Currently an order of the object's generation for Postgresql is incorrect. I work with Postgresql 9.2 but the same issue will exist for other versions. The roles are generated almost at the end of the script, but schema is generated at the very beginning. The problem is that schema may require an authorization associated with the role like
CREATE SCHEMA "test_schema" AUTHORIZATION "test_application_admin"
This statement will fail because role "test_application_admin" wasn't yet created. I suggest to create roles first, but to leave a section that grants permissions to the roles at the end of the DDL script.
The second problem is that script tries to create without pre-existence check even standard and pre-defined schemas and roles like
CREATE SCHEMA "public" AUTHORIZATION "postgres";
CREATE SCHEMA "pg_catalog";
CREATE ROLE "postgres" LOGIN;
These statements will just generate error messages.