On this page

Show all

Help Center/ GaussDB(DWS)/ Tool Guide/ Data Studio - Integrated Database Development Tool/ About Data Studio/ Structure of a Release Package

Structure of a Release Package

Updated on 2023-04-03 GMT+08:00

View PDF

The release package structure of Data Studio is as follows:

Click to enlarge

Folders/Files	Description
configuration	Contains information about the application launcher and the required Eclipse plug-in path.
db_assistant	Contains SQL assistant related files.
docs	Contains Data Studio User Manual.pdf which provides you with details on using Data Studio. Contains copyright notices, licenses, and the written offer for the open source libraries used in Data Studio.
features	Contains Eclipse (rich client protocol-GUI) and Data Studio features.
p2	Contains files required for provisioning and managing Eclipse and Equinox-based applications.
plugins	Contains the required Eclipse and Data Studio plugins.
tools	Contains Data Studio dependent tools.
UserData/ Autosave Logs/ Preferences/ Profile/ History/ Security/	Contains separate folders for each OS user of Data Studio. Autosave - Contains the auto saved information of unsaved queries and functions/procedures. Logs - Contains Data Studio.log which stores log information of all the operations performed in Data Studio. Preferences - Contains the Preferences.prefs file which stores the custom preferences. Profile - Contains the connection.properties, SQL History and Profiles.txt files required to manage connection profiles in Data Studio. Security - Contains files required to manage security in Data Studio. NOTE: The UserData folder is created only after the first user opens an instance of Data Studio. The Logs folder, language, memory settings and log level are common for all users. The Logs folder, Data Studio.log file, Preferences folder, Preferences.prefs file, Profile folder, connection.properties file, Profiles.txt file, and security folder are created after launching Data Studio. If the Logs folder path is provided in the Data Studio.ini file, then logs are created in the specified path. When user is not able to log in to the Data Studio because the security keys are corrupted, follow the steps to generate new security keys: 1. Delete the Security folder from the Data Studio folder > UserData > Security folder 2. Restart Data Studio
artifacts.xml	Contains the product build information.
changelog.txt	Contains the detailed change log information of release version.
Data Studio.exe/DataStudio.sh	Allows you to connect to the database and perform various operations (like managing database objects, editing or executing PL/SQL programs and so on).
Data Studio.ini	Contains run-time configuration information of Data Studio.
readme.txt	Contains the features or fixed issues of current release version.

Parent topic: About Data Studio

Previous topic: Constraints and Limitations

Next topic: System Requirements

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback