Devart Forums

(dbForge for SQL Server 4.5.60 connecting to SS2014 Enterprise)

I searched this forum but did not find an answer. I seek to set the formatting in dbForge Studio, but I'm not getting the results I expect. I've been a SSMS (and Query Analyzer) user since 2002 so I have a certain way of working. Surely, I'm not the only one who works this way.

My goal is to:
- not have "USE DATABASE GO" appear when I generate a SELECT script on a table
- have the table columns and table names bound with brackets on script generation, as in []
- have the intellisense (equivalent) offer column names as I type rather than having to perform multiple mouse-clicks to get to the column name
- when using the "Pivot Table" function the columns shown under the "PivotTable" should be listed in the table design order rather than in alpha order; since I'm accustomed to the table definitions this column order is quite jarring

I found settings for some of these things, but they don't seem to have an effect. For example, in the Options under "Generate Scripts" I deselected "Script USE DATABASE" but "USE DATABASE" persists in script generation.

Thank you in advance for any assistance.

- have the table columns and table names bound with brackets on script generation, as in []

This can be tuned under the 'Enclose identifiers within square brackets' section of the 'Text Editor -> Code Completion -> Advanced' branch of the 'Options' window that can be invoked by selecting 'Tools -> Options...' from the main menu.

- have the intellisense (equivalent) offer column names as I type rather than having to perform multiple mouse-clicks to get to the column name

The 'Code Completion' feature can be turned on as follows:

1. Select 'Tools -> Options...' from the main menu. The 'Options' window opens.
2. Navigate to the 'Text Editor -> Code completion -> General' branch.
3. Select the 'Enable Code Completion' option.
4. Click 'OK'.

- when using the "Pivot Table" function the columns shown under the "PivotTable" should be listed in the table design order rather than in alpha order; since I'm accustomed to the table definitions this column order is quite jarring

You can add a suggestion on our UserVoice forum where other users can vote for it
http://devart.uservoice.com/forums/1770 ... sql-server

We collect and analyze the information from this forum in order to make a proper roadmap for future product releases.

I found settings for some of these things, but they don't seem to have an effect. For example, in the Options under "Generate Scripts" I deselected "Script USE DATABASE" but "USE DATABASE" persists in script generation.

We will fix this issue in one of the next product builds.

Thank you very much for your reply.

I verified that all the settings you suggested are already set that way, yet they appear to not have an effect. I right-click a table and choose "Generate Script As" then choose "Select," as I would in SSMS, (so far so good) and the script is generated, but without the enclosing brackets and with "USE DATABASE." So, the settings appear to me to be ignored.

I've set the settings, closed the application, reopened the application, verified the settings are as I set them, generate a new script, but they remain ineffective.

I'm currently using the "Trial" edition. Is that relevant? Or am I doing something incorrectly?

The 'Enclose identifiers within square brackets' section relates to the 'Code Completion' feature, but not to the 'Generate Scripts' one.

Unfortunately, there is no such an option for generating scripts. We will add it in one of the next product builds.

Also,you can add a suggestion on our UserVoice forum where other users can vote for it http://devart.uservoice.com/forums/1770 ... sql-server

We collect and analyze the information from this forum in order to make a proper roadmap for future product releases.

Thank you very much. I will heed your suggestion.

I found settings for some of these things, but they don't seem to have an effect. For example, in the Options under "Generate Scripts" I deselected "Script USE DATABASE" but "USE DATABASE" persists in script generation.

We would like to let you know that we have released dbForge Studio for SQL Server, v5.0 where the issue you reported is fixed https://www.devart.com/dbforge/sql/studio/download.html

Thank you for your help in improving dbForge Studio for SQL Server.