Skip to content
← dbForge Studio for SQL Server

How can we improve the product?

dbForge Studio for SQL Server: Features

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Ability to set path for storing *.design files

When a sql script is being edited and saved in same directory automated created *.design file. The *.design files in working directories is no good. I suggest to add ability set path for storing *.design files in separate directory. By default it can be temp directory.

12 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Роман Пикуленко shared this idea  ·   ·  Report…  ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • AdminDevart (_, Devart) commented  ·   ·  Report

    Hi,

    Thanks for your patience!

    Just want to inform you that it is already fixed. We no longer maintain *.design files.

    So we would like to suggest updating to the latest version and check there.

    Best,

    Devart Support Team

  • Kirk Wolak commented  ·   ·  Report

    Actually, I have a COMPLETELY Different Approach/suggestion to this!

    Please consider creating a SQLite.db file, and store these settings with with the full path of the file, in there.

    Furthermore, store in there every filename/path I ever open, so I can search back. In fact, enable an option so that the SQL 1, SLQ 2 files that you create are actually saved physically in a specific folder. I don't care. Disk is cheap.

    Anyways, then with this, you no longer need the .design files!
    Next, you could allow me to search EVERY FILE I ever opened for a string, and find the list of files... And I could open them in bulk.

    Furthermore, if I could add a LABEL to a group of files that are open (Finding API_Cart_errors). And save that (one of many) labels with these files. So, in the future, if I get an API_Cart issue, I can find the files I used to address this issue last time. And go from there.

    But this solves ALL of the problems, and creates innovative ways to deal with files in the future.

  • Sundar Anupindi commented  ·   ·  Report

    Yes. The .design file something that I don't want it to get created automatically. I would love to have this feature as User Choice.

  • Aaron commented  ·   ·  Report

    The .design file "feature" is horrible. I don't even want the data, I'd rather start with a blank template every time I open a file. I've setup a task to auto delete all of the .design files from my scripts directory. The .design file clutter up my folders and makes it more difficult to find and edit my script files. dbforge is *not* my only editor.