Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
The first two settings allow configuring upload file size and memory utilization during upload, measured in MegaBytes. The last settings controls how passwords are handled during upload of server connections. All changes to system settings take effect immediately unless otherwise noted.
The above restriction applies to all file uploads including
Note: Project deployment from Aqua Data Studio is not subject to this limit for package size, but the uncompressed size of each file in the zip package is subject to this limit.
Options are 5, 10, 50, 100 or 200 MegaBytes. Any attempt to upload a file that is greater than the maximum file size specified will result in an error. The user file will be notified that the maximum file size has been exceeded.
Options are 5, 10 or 50 MegaBytes. This is used to configure the in-memory buffer size during a file upload operation. If you are low on memory you may want to set this to a small number. The trade-off is that there is more frequent disk access during the upload operation.
This is an advanced feature and, if enabled, should be activated prior to first production usage. Otherwise, existing production data such as Secure Storage will no longer be usable. Please read this entire section. If you decide to enable this feature, perform all steps prior to first usage in production.
AquaScript developers will most likely use Aqua Data Studio as their primary development environment. If the AquaScripts need database access, the developers will also register server connections in Aqua Data Studio. These server registrations are stored on the local filesystem where Aqua Data Studio is running and are saved with a ".conn" extension. The .conn file contains all necessary information to connect to the specified database, including the password. For security purposes, the password is not saved in plain text. Instead, it is encrypted and, without additional setup, can only be decrypted by the same instance of Aqua Data Studio that encrypted it. Because of this reason, by default, Aqua Data Server does not import the database password specified in the server connection when a user imports or deploys a server connection into Aqua Data Server. If you would like to enable the importing of server connection passwords, please read the next section.
Prior to enabling the "save password while importing server connections" feature, you must follow the below steps. Otherwise, the password that is imported will be unreadable and not usable by Aqua Data Server.
Each instance of Aqua Data Studio and Aqua Data Server uses a unique private key to encrypt the server connection password. This key is contained in the "pfile.properties" file located in <USER_HOME>/.datastudio or <USER_HOME>/.aquadataserver, respectively.
In order to share passwords between the two applications:
Aqua Data Studio and Aqua Data Server now share the same key for encryption and decryption of server connection passwords and hence passwords can be imported from Aqua Data Studio to Aqua Data Server.
This same key is also used to encrypt / decrypt Secure Storage fields in Aqua Data Server. Hence, if you update pfile.properties after you've already registered server connections and/or created secure storage fields, Aqua Data Server will no longer be able to decrypt the existing values, since its key has changed.
If this setting is enabled, server connection passwords will be imported via the Deploy action in Aqua Data Studio, Import action in Server Connection and Import action in Project -> Settings.