A: Check the following:

• Verify the Connection Properties, to check whether the input to the connection properties is correct.
• Check whether the server and client versions are compatible.
• Check whether database\pg_hba.conf file is configured properly. Refer to the server manual for more details.
• Check whether Data Studio.ini file is configured properly.

A: If the same SSL certificates are used by different server, then the second connection will be successful because the certificates are cached.

When you try to establish a second connection with a different server using different SSL certificates, the connection will fail because of a certificate mismatch.

A: This may happen when you drop a function/procedure and recreate it. In this case, refresh the parent folder to view the function/procedure in the Object Browser.

A: Critical error can occur in some of the following cases. Check whether:

• The connection is left idle for long time and has timed out.
• The server is running or not.
• There is enough memory available on the server and no "out of memory" is reported on the server.

A: Constraints are used to restrict the insertion of unwanted data in columns. You can create constraints on single or multiple columns of any table. It maintains the data integrity of the table.

There are three types of constraints supported:

• Primary Key constraint
• Unique Key constraint
• Check constraint

A: An index is a copy of select columns of data from a table that can be searched very efficiently. It also includes a low level disk block address or a direct link to the complete row of data it was copied from.

A: Exported, imported, and system files are encoded with the system's default encoding as configured in Settings > Preferences. The default encoding is UTF-8.

A: Opening multiple instances of Data Studio by the same user is not supported.

A: This can happen if there is another active DML/DDL operation being performed on the same object. Close all active DML/DDL operations on the object and try again. If the problem still persists, it could be that another user might be performing a DML/DDL operation on that object. Try after sometime.

A: For export result set data, the query is re-executed using a new connection. Hence the exported result may differ from the data shown in the Results tab.

A: Last login details not available is shown, when you are connected to the older version of the database server or you have logged into the database for the first time after the database has been created.

A: This happens when server returns the incorrect line number. Review the error message in Messages tab and navigate to the corresponding line number to fix the error.

A: Yes, Show DDL and Export DDL operation will display the dropped column information.

A: This happens if the value defined for -Xmx parameter is invalid. Refer to Installing and Configuring Data Studio.

A: After the number of opened Terminals or tabs reaches a certain limit based on screen resolution an icon () displays with a drop-down option at the end of the Terminal list. Click the icon and select the required Terminal from the drop-down list. If the is not available, then use the tooltip to identify the Terminal or tab. Terminal name can be searched by typing the search value above the list of SQL Terminal names.

Example:

• *s, this displays all Terminal names that starts with s.
• test, this displays all Terminal names that starts with test.
• *2, this displays all Terminal names that contains 2 in them.

A: Sometimes the language may not reflect the selected change post restart. Manually restart DS to open the tool in selected language.

A: At times the server returns an error while trying to fetch last login details. In such scenarios the last login pop-up message does not display.

A: This happens if the SQL, DDL, object names or data contains Chinese text and the Data Studio file encoding is not set to GBK. To solve this, go to Settings > Preferences > Environment > File Encoding Preference... and set the encoding to GBK.

The supported combinations of Database and Data Studio encoding for export operation are shown in Table1 Supported combinations of file encoding.

To open/view the exported files in Windows Explorer: Files exported with UTF-8 encoding can be opened/viewed by double-clicking it or by right-clicking on the file and selecting Open. Files exported with GBK encoding must be opened in MS-Excel® using the import external data feature (Data > Get External Data > From Text).

A: This message occurs if the Data Studio and Database encoding selected are incompatible. To solve this, select the compatible encoding. Compatible encoding is shown in Table 2.

A: The database does not differentiate between PL/SQL function and procedure. According to the database all procedures are functions. Hence PL/SQL procedure is saved as PL/SQL function.

A: The database allows you to edit the distribution key only for the first insert operation.

A: Yes, the database server will add the value but the value will not be visible after save in the Edit Table Data tab. Use the refresh option from the Edit Table Data tab or re-open the table again to view the added default value(s).

A: This happens because there are additional rows detected for modification/deletion based on Custom Unique Key or All Columns selection. If Custom Unique Key is selected, then it will delete/modify the rows that have exact match of the data in the column selected for deletion/modification. If All Columns is selected, then it will delete/modify the rows that match data in all columns. Hence this duplicate records matching the Custom Unique Key or All Columns will be deleted/modified if Yes is selected. If No is selected, the row that is not saved will be marked for correction.

A: The additional context menu options like Right to left Reading order, Show Unicode control characters and so on are provided by Windows 7 in case the keyboard you are using supports right to left and left to right input.

A: Following objects are not supported for DDL & DDL and Data operations.

Export DDL:

Connection, database, tablespace, foreign table, sequence, column, index, constraint, partition, function/procedure group, regular tables group, views group, schemas group, and catalogs group.

Export DDL and Data:

Connection, database, tablespace, foreign table, sequence, column, index, constraint, partition, function/procedure, view, regular tables group, schemas group, and catalogs group.

A: No. Queries will only be committed when COMMIT command is executed in the Terminal.

A: When you query a temp table from a new SQL Terminal or with the Reuse Connection Off, the resultset displays information of a regular/partition/foreign table, if a table with the same name as the temp table exists.

If the Reuse Connection is On, the resultset displays information of the temp table even if another table with the same name exists.

A: Yes, xlsx format supports maximum of 1 million rows and 16384 columns and xls format supports maximum of 64,000 rows and 256 columns.