| Database Subsetting Tool |
Home Quick Tour Tutorial Data Browser FAQ API Documentation Forum Download
FAQ
Frequently Asked Questions
Q | Why am I getting so much data back?
A | Each association will be traversed in both directions, unless there is a restriction defined. If, for example, the subject table is employee, and the association from department table to employee table is enabled, you will not only get all departments associated with any subject employee, but also all employees associated with one of these departments. If you get lines that you do not want to get, you need to make a further restriction. The Progress Panel can help you in such a case. It shows the chain of associations for each exported row back to a subject row, where the export starts. I recommend reading the tutorial that explains these things. Instead of adding all restrictions you need, starting from the unrestricted model, you can also go the opposit way: at first disable all associations (except dependencies) via the menu item "Edit->Disable all associations". Then remove restrictions until you get all the rows you are looking for. It is easier to get a working extraction model in this way, but it is more difficult to ensure that the model is not too restrictive, i.e. that you get all the rows you want. In my experience the best way to define an extraction model is to use the "Closure" view. The closure view lists all tables that are directly or indirectly associated with the subject table (where the export starts), according to the restrictions, ordered by distance. Check each table of this list from top to bottom. If you don't want to have rows from the table to be exported, select the table and disable the association which will be automatically selected (the context menu of the table is also available here). The table disapears from the list as soon as it is no longer associated with the subject. You could also first check the tables with the highest degree (the degree of a table is the total number of adjacent tables that can be reached directly with an enabled association.) this way. These are often the tables that increase the closure significantly and therefore have many associations to be restricted. In this way, you simply get an extraction model that extracts rows only from tables from which you want to extract data. Finally, check all associations between the remaining tables.
Q | What does $DISTANCE and $IS_SUBJECT mean?
A | $DISTANCE and $IS_SUBJECT are special expressions used in restriction conditions in order to define restriction models based on topological properties of rows.
Expression | Type |
A.$DISTANCE or B.$DISTANCE | INTEGER | Minimum length of all paths from the row back to any subject row. The distance of a subject row is 0.
A.$BIRTHDAY | INTEGER | Synonym for A.$DISTANCE
A.$IS_SUBJECT | BOOLEAN | Synonym for A.$DISTANCE=0
$IN_DELETE_MODE | BOOLEAN | Is true during "Delete Reduction" stage, otherwise false
Q | How do I anonymize the extracted data?
A | It's possible to anonymize the extracted data by defining filters (via "Edit" menu "Filter editor...", or table's context menu) A filter is an assignment of an SQL expression to a table column. The column values will be replaced by the result of the expression when the export file is written. For example: In order to substitute the values of the column PERSON.SSN with the constant value '123', define the filter: PERSON.SSN := '123' The filter PERSON.SSN := substr(${old-value}, 1, length(${old-value}) - 3) || '***' replaces the last 3 characters of the SSN with '***' ${old-value} is a synonym for the filtered column. The filter: PERSON.SSN := (SELECT SSN FROM TEST_SSN ORDER BY RAND() FETCH FIRST 1 ROWS ONLY) would replace the SSN with a randomly chosen SSN from a table holding test SSNs (IBM DB2)
Q | Is it possible to avoid the creation of JAILER_* tables in the database?
A | Set the working-table scope to "local database" ("Data Export" dialog) to avoid the creation of that tables in your database. The tables will then be created in a local database (H2). For DB2, Oracle and PostgreSQL, it is also possible to create the tables as temporary tables.
Q | I'm getting the message "Table has no primary key". What's wrong?
A | Jailer cannot handle tables without a primary key. Exporting data is not possible if the subject table is associated with a table without a primary key. In this case, you should manually define a primary key in the data model of the tool (not in the database!) using the Data Model Editor. Note that a key must be unique. (On Oracle, however, rowid-pseudo columns can be used instead of primary keys)
Q | The GUI is slow, what can I do?
A | Due to the dynamic nature of the layout algorithm, the table-association graph is permanently redrawn. It seems that this consumes too much cpu time on some systems. However, there is a parameter called "animation step time" which determines the minimum time (in ms) for one animation step. Increasing that parameter (Settings->Animation step time) will reduce the cpu utilization.
Q | How do I setup multi-user mode?
A | Unzip the "jailer-version.zip" file and create an (empty) file ".multiuser" in the directory "jailer". All model and settings files are then stored in a folder named ".jailer" in the user's home directory.
Q | Why do text and buttons on my Full HD, UHD or 4K displays look so small?
A | Java JRE 8 does not support HiDPI graphics. Therefore it is strongly recommended to use Java JRE 11 (or above).