Move all settings/templates from one PC to another?

[Chris Fischer]

I am moving from one laptop to another and would like to take all my settings for PL/SQL Dev with me. Is this possible? If so, how?

Thanks!

 

[LanderMen]

Hi,
I think that, in the directory preferences of the pl/sql it is the profile copy and paste in same directory of the destino.

Lander.

 

[Marco Kalter]

The Preferences\[username] directory contains your preferences. Other settings, such as window sizes, are stored in the user registry at:

hkey_current_user\software\allround automations\pl/sql developer

 

[Todd]

Each of our users has an "H:" drive, which is their own.

Is there a way to set one registry setting (via Active Directory Group Policy) to tell PLSQLDeveloper to pick its settings up from their H: drive, we would then keep all profiles, templates, macros online.

 

[Marco Kalter]

No, this is not possible. You can only force PL/SQL Developer to use the Application Data directory of your Windows user profile by using the APPDATA=YES command-line parameter. For example:

"C:\Program Files\PLSQL Developer\plsqldev.exe" appdata=yes

You can also add this entry to the params.ini file (instead of the command-line) to ensure that it is always enforced.

Note that this will only work with version 7.1.3 and later.

 

[Todd]

Marco-

How does the "PLSQL Developer\Preferences\Default" come into play?

What is best practice for installing to a network share for centralized deployment, that installation wouldn't allow for end users to write to the network location.

If "Default\Default.ini" can be pushed with the installation and these settings:
[Preferences]
MacroDir=h:\AppSettings\PLSQLDev\Macros
TemplateDir=h:\AppSettings\PLSQLDev\Templates
PlugInDir=h:\AppSettings\PLSQLDev\PlugIns
ProjectsDir=h:\AppSettings\PLSQLDev\Projects

we should be good to go...

Thanks!

 

[Marco Kalter]

How does the "PLSQL Developer\Preferences\Default" come into play?

It contains the default preference settings.

What is best practice for installing to a network share for centralized deployment, that installation wouldn't allow for end users to write to the network location.

In this case PL/SQL Developer will automatically store all configuration files in the Application Data directory of your Windows user profile. In other words, it should work just fine without any additional configuration.

If "Default\Default.ini" can be pushed with the installation and these settings:

That should work just fine.

 

[Robert_G]

Originally posted by Marco Kalter:
No, this is not possible. You can only force PL/SQL Developer to use the Application Data directory of your Windows user profile by using the APPDATA=YES command-line parameter. For example:

Note that this will only work with version 7.1.3 and later.

I downloaded 7.14 and it is not working.
This is pretty bad, as there are some users in my company that are not able to save any settings.
And I don't intend to give them write access to the PL/SQL folder...

I often advocate for your product, but these things make me feel uneasy doing so.
Saving settings in %appdata% should be the normal thing to do since WinNT! (Yep, way before PLSQL Dev 1.0)

So, how can I get it to work for normal users.
And when will this be the default?

 

[Robert_G]

Okay, it seems that changing params.ini to...

prefpath=%appdata%\PLSQL Developer

... will work in 7.14.
It didn't work in older versions.