Profile Sharing

Working with Multiple IDEs? Your Profiles Are Already Shared.

If you use more than one development tool on Windows — say SSMS for database work and VS Code for application code, or JetBrains alongside Notepad++ — you no longer need to configure SQLinForm separately in each one.

Starting with Version 26.2, all SQLinForm plugins on the same Windows machine automatically share the same profiles. There is nothing to set up, nothing to import or export, and nothing to keep in sync. Install SQLinForm in any combination of IDEs, and your formatting settings are available everywhere — instantly.

Note: Cross-plugin profile sharing is available on Windows (x64). On macOS and Linux, where only VS Code and JetBrains are supported, each plugin manages its own local profiles. However, the Team Folder feature (see below) works on all platforms — so you can still share profiles across machines and operating systems via a shared network drive.

What This Means in Practice

• Configure once, use everywhere — Set up your formatting options in VS Code, and they’re immediately available in SSMS, JetBrains, Notepad++, DBeaver, and the Portable App
• All 5 profiles shared — Including your custom profile names
• License shared — Your Pro license is recognized by all plugins automatically, no need to enter it multiple times
• Zero configuration — It just works out of the box

Supported Products

Working in a Team? Share Formatting Standards with One Click.

Code reviews shouldn’t be about formatting. If your team wastes time discussing comma placement, keyword capitalization, or indentation style, SQLinForm’s new Team Folder feature is for you.

The idea is simple: your team lead configures the desired formatting options once and saves them to a shared location. Every team member points their SQLinForm to that same location. From that moment on, everyone formats SQL the same way — across all IDEs, without any manual effort.

How It Works

1. Team Lead creates a shared directory on a network drive (e.g., \\server\share\SQLinFormTeam\)
2. Team Lead sets this directory as the Team Folder in any SQLinForm plugin and configures the formatting options
3. Team Lead shares the path with the team
4. Each developer sets the same Team Folder path in their IDE and switches to Team mode
5. Done. Everyone uses identical SQL formatting, across all IDEs, with zero maintenance

Why Teams Love This

Local/Team Toggle

Every developer has a Local/Team toggle in the SQLinForm toolbar. This lets them instantly switch between their personal profiles and the team-managed profiles:

Switching is instant. Both sets of profiles are always preserved independently.

Team Folder Setup Guide

Step 1: Create the Team Folder

Create a shared directory that all team members can access. No special folder structure is required — SQLinForm will initialize the profile files automatically when the folder is first used.

Step 2: Configure the Team Folder

VS Code / JetBrains / Notepad++

1. Open the SQLinForm Settings Panel
2. Click the Team menu in the toolbar
3. Select Set Team Folder…
4. Browse to and select your shared directory
5. Click the Team toggle to switch to Team mode

SSMS 18–22 / Visual Studio 2022–2026

1. Open the SQLinForm Tool Window
2. Click the Team menu in the toolbar
3. Select Set Team Folder…
4. Browse to and select your shared directory
5. Click the Team toggle to switch to Team mode

DBeaver (External Formatter)

In DBeaver’s external formatter settings, configure the command line as follows:

cli.exe" -dbeaver ${file} -p 1    (Local Profile 1)
cli.exe" -dbeaver ${file} -t 1    (Team Profile 1)

Use -p followed by the profile number (1–5) for local profiles, or -t followed by the profile number for team profiles. The ${file} parameter is DBeaver’s temporary file used for communication and cannot be changed.

Step 3: Share the Path with Your Team

Send the Team Folder path to your team members. Each person only needs to configure it once — after that, they can switch between Local and Team mode at any time.

Profile Storage Locations

All SQLinForm plugins store their shared profiles in a central directory:

Windows

%AppData%\Roaming\SQLinForm\
├── Profiles\
│   ├── profile1.json
│   ├── profile2.json
│   ├── profile3.json
│   ├── profile4.json
│   ├── profile5.json
│   └── profileNames.json
├── License\
│   └── license.cfg
└── settings.json

macOS

~/Library/Application Support/SQLinForm/

Linux

~/.config/SQLinForm/

Each profile is a human-readable JSON file using property names (e.g., GEN_NBR_SPACES_INDENT) rather than internal IDs. You can inspect or compare profiles with any text editor.

When using a Team Folder, the same file structure is created in the Team Folder directory. The Local/Team toggle switches between these two locations.

Automatic Migration from Previous Versions

When you update to Version 26.2, your existing profiles are automatically migrated to the new shared location. This happens once on first launch — no manual action required. The migration applies to VS Code, SSMS 18–22, Notepad++, and the Portable App.

JetBrains users are not affected, as the JetBrains plugin was released with shared profile support from the start.

Where to Find Your Old Profile Backups

During migration, a backup of your previous profiles is saved in a plugin-specific subfolder inside the shared Profiles directory:

These backup folders are created automatically and are never deleted. If anything goes wrong during migration, your original settings are safe.

Note: If you had multiple SQLinForm plugins installed before the update, the first plugin to launch performs the migration and copies its profiles to the shared location. Subsequent plugins detect that shared profiles already exist and create only their own backup — they do not overwrite the shared profiles.

Troubleshooting

Legacy: Import/Export

The Import/Export feature is still available under Profile → Import Profile… and Profile → Export Profile… for special use cases — such as sharing a profile via email, archiving a configuration, or migrating from older versions. For day-to-day use, however, import and export are no longer needed.