381 results found
-
Set Compatibility Level to SQL 2022 (160) on Edit Database Page
Right click on a database on a SQL Server 2022 Enterprise Edition Instance and select Edit Database. Switch to the Options tab. Select the Compatibility level dropdown, I am only seeing up to SQL Server 2019 (150) as options, I am missing the SQL Server 2022 (160) option and need to manually write the ALTER DATABASE statement to set it.
1 vote -
Find results highlighted on scrollbar
In SSMS, when you search for a term, all locations of that term are highlighted on the scrollbar, making it easy to navigate to the locations of that term and to know where they appear in the file. In dbForge Studio, you can bookmark all, but that requires you to scroll through the entire document to find all instances and does not provide a complete picture of all of the places the term appears.
This is a very important feature that is missing for me as I rely on that heavily in SSMS. I would like to see similar functionality…
4 votes -
Create internal repository for saved SQL Queries
Instead of saving an
.sqlfile in a path, create a managed store with the following features:- Title, description - use AI to generate a suggestion for both fields
- Category and assiciated category management tool
- Extract and save any variables and target DB used by the query (to be used when recalling)
- Editing, deletion, importing and exporting of stored queries
- Recall stored queries with intelligent search functionality
- Dialog when recalling function that would prompt for confirmation or changes to target db, and variable values.
- recent and most used sorting in
Filemenu
3 votes -
history
Please move the Clear button for Query History from the main UI screen to be in the Options menu. In context, it seems like it is going to clear the search filters rather than wiping out the entire query history. It does warn you - but the history is so useful and important. Clearing it out should be a harder, more explicit step than just clicking twice. Not that I've done that... Multiple times...
3 votes -
Default column for datetime added getdate() as default.
It will not save that column. I get an error about the )
1 vote -
Detach stored SQL query from SQL connection
At present, if I developed a SQL query, stored it and try to load it back into dbForge at a later date, dbForge 'remembers' the SQL connection it is associated with and tries to connect automatically. I want to be able to disable this behaviour via options - eg opening file does NOT try to be clever.
EXTENDED RATIONALE
In common usage, the feature is quite useful. Unfortunately, in some of the projects I am working with, I have to constantly switch between different environments (prod, pre-prod, demo, devops, etc) protected by external VPN. All environments are hosting the same…
1 vote -
More options for sorting in List Members
In previous versions, custom snippets were in the first positions. This is not the case in the current version.
It would be nice to be able to choose in the settings what to sort the results by and the possibility to prioritize custom snippets to the first positions
1 vote -
Schema added to properties when not required
Currently when I use Query designer the resulting query is expressed as:
SELECT Hygiene360Log.Hygiene360LogId, Hygiene360Log.RequestDate FROM dbo.Hygiene360LogWhere what I want is the minimum length of text to correctly identify tables and objects, like this:
SELECT Hygiene360LogId, RequestDate FROM Hygiene360LogIt's very annoying
3 votes -
Autocomplete Improvement Suggestion
Dear Devart Team,
I suggest enhancing your autocomplete feature by making the first option selectable with the tab key. This would reduce the current two-step process (typing additional letters or using the mouse) to a single action, improving efficiency and user experience.
Thank you for considering this improvement.
Best regards,
1 vote -
Please add the new sql server 2022 features
SQL query window does not accept adding the 'WINDOW xxx AS' clause to a query with a window function.
3 votes -
Is it possible to change the default location of .dgen files?
The default location for custom data generation configs is:
C:\Users\Public\Documents\Devart\dbForge Studio for SQL Server\Data Generators
This is different than the location for the other project-related files and this makes it tough to check in and share, etc.
Is it possible to change this default location?
I have a feature request in about this, but maybe there's a hack or even something I'm missing to set this location?
1 vote -
Schema compare does not work for many identical scripts / texts
Schema compare is incorrectly marking scripts as "update" yet text wise they are completely identical (including control characters and white spaces)
3 votes -
I'd like to be able to edit or delete user defined (custom) data generation configurations directly from the GUI
I'd like to be able to delete user defined (custom) data generation configurations directly from the GUI.
Currently, you can create (but not delete, nor edit) user defined custom data generator configurations easily.
Often it is necessary to delete these custom configs because you've created new ones...or saved it too many times...or for other reasons. However, there's no option to delete from the GUI. In order to delete them, you have to find their location and delete xml files found under C:\Users\Public\Public Documents\Devart\dbForge...\Data Generators... there you're presented with only timestamped files with no naming that indicates which user defined generation…
1 vote -
Orderly Fashion Data Pump (From parent to children + referential integrity)
I am trying to do a data pump but once it is finished the data is almost useless because I don't need 1,000 records per-table, but as many as meaningful are, the children records derived from smaller amounts of records in its corresponding Mater or Parent tables
So If have for instance ... let's say Businesses (1) and Stores (2) so I'd like to pump data just for these entities not 1,000 business and 1,000 stores but 1,000 billing records, 10,000 stock count records, 8,000 items catalog for each store ... derived from previous node ... like a tree structure…
1 vote -
pin tab
how is possible there is no simple thing as pin tabs?
2 votes -
When you have an existing data compare and you change the target, it doesn't work
Take two identical databases on different SQL Server instances (or on prem vs Azure). Ensure they are identical by doing a schema compare. Take a data generation file that is configured and works for one database. Take that file and change the target to the new database. The pre-existing configuration does not get applied to the new database.
The workaround is to create a copy of the existing data generation file, open the new configuration .dgen file in a text editor and change the ConnectionString line in the xml to match the new database's properties. In order to get the…
1 vote -
Script Object as Create / Alter (ctrl- F12) into named tab instead of no name
After Script Object as Create / Alter (ctrl- F12) please name the new tabbed window with the scripted object's name instead of SqlQuery99.sql.
And also please make this forum easier to search.
I can't believe nobody asked for this feature before, but I couldn't find an existing item to upvote.
I hate duplicate tickets just like anyone!2 votes -
As a developer, I'd like to be able to check in custom data generator configurations...
As a developer, I'd like to be able to check in custom data generator configurations with the rest of my project's configuration into source control.
Currently, the xml configuration files are stored in a separate far-off location /Users/Public/... and this makes it not ideal if you want to version your generator configurations to share with the rest of the team through Git, as an example.
1 vote -
Transpose SQL Result
I want the ability to transpose the SQL result so you only view one record at a time and having the option to sort the column names or the values. And then adding buttons to iterate through the result set.
And no, the card view does not serve this purpose.
3 votes -
Data Pump pass through imported file name
When it comes to bulk Data Pump imports from multiple files (e.g. Excel, *.csv), I'd really appreciate the ability to pass through the source import file name (as text) to a dedicated column within the destination SQL Server data table against each imported record.
Personally, I use the DevOps PowerShell Automation import pathway and would find it a really handy addition for basic audits if it was accessible as a parameter on Invoke-DevartDataImport
Thanks!
1 vote
- Don't see your idea?