39 results found
-
Executing SQL with named parameters causes a dialog to show up asking for the parameters.
If I have the following SQL:
EXEC sp_rename @objname='ardbPcbRelatedGames.PcbRelatedGamesID', @newname='PcbRelatedGameID', @objtype='COLUMN'
A dialog will pop up asking for the values for @objname, @newname and @objtype. Those already have values provided and it doesn't need to ask me for them.
2 votes -
Default column for datetime added getdate() as default.
It will not save that column. I get an error about the )
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 -
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 -
Auto re-draw causing loss of user specified relationship lines on diagraming tool
Fix issue with diagram tool auto redrawing relationship lines when tables are dropped and recreated with no changes to relationships from old to new tables.
Specifically I reverse engineered my tables into the database diagraming tool. Then painstakingly organized the tables then adjusted all the relationship lines so they take a short path and do not cross then saved the diagram.
When re-opening it everything is fine. But - if I ever drop and recreate the tables (e.g. with a script to change the schema) the diagram tool auto-redraws all the relationships and the diagram becomes a mess.
Please fix.…
1 vote -
bug:Bug in table editing
SELECT * FROM BaseProfile A
JOIN BaseProfile_Trl A1 ON A.ID = A1.ID WHERE A1.id=20200215edit table:BaseProfileTrl,After editing one row of data, I found that the entire table got updated.
1 vote -
Error on object permission
There is an error on list object permissions on Security Manager (on specific database or all server)
SQL Server: 2022 Enterprise Core
dbForge Studio for SQL Server: 6.4.73 votes -
Please make your window selection dialogs less useless.
The window selection dialogs have a Name and a Path column. You can resize the dialog to your heart's content, but it will not have any effect on the width of the Name. Which, if the window is displaying a DB object, will have the schema part of the name prepended. Which, if th. e schema part of the name is long enough to be useful, will cause the interesting part of the name to be truncated.
Provide an affordance that will allow users to resize the width of the Name column in the window selection dialog. Alternatively, provide a…
1 vote -
When I reformat the document it doesn't put Aliases, Table Names or Column Names in [] even though I have that option on.
When I reformat the document it doesn't put Aliases, Table Names or Column Names in [] even though I have that option on.
Formatting should enforce the rules I have in place. I want Table Names, Column Names, Aliases all enclosed in [].
2 votes -
formatting turn off
When I open an existing stored procedure or view with Modify menu item, dbForge studio formatting is automatically applied. Is there a way to prevent this?
3 votes -
intellisense in select
if you write part of a column name, intellisense gives you a list to chose from, but automatically selects the first row, so you can confirm the choice by pressing TAB. That works in WHERE, ON, GROUP BY, ORDER BY statement, but not in SELECT. I am quite sure that in one old Release this worked. not sure, why it does not anymore.
Right now in SELECT you have to write part of the column name and then use cursor down to select the first item on the list, then press tab.1 vote -
import dbf file
When we do an import for dbf file, the first file is ready to create a new table with the file name for the table's name. At the end, when the import is done, we can click on "Import more". We select a new dbf file but it tries to import in an existing table or the previous table name and a number at the end. It must always be the file name for the table name when we want to import to a new table.
Thanks a lot!1 vote -
V.6.0.563 Container's title and stamp text color
Since V.6.0.563 in the diagram fonctionnality, the Container's title and the stamp's text color are white, resulting in very hard to read titles for the containers and impossible text to read in stamps.
21 votes -
Save a file even if it contains errors
If a DML query contains an error, the file is not saved. It is absurd to have to go into Notepad to save a file.
1 vote -
Data Editor should be case sensitive when determining whether to update
When a value is changed in the Data Editor, the Data Editor logic compares the value with the existing value and makes a decision whether to update the existing value based on whether the new value is considered different. Currently, this equality comparison is case insensitive, which is a bug. It must be case sensitive. SSMS will update data based upon consideration for case sensitivity, but not the Data Editor.
1 vote -
Shortcut Ctrl +Alt+o conflict with windows Alt+o - local alphabet letter
Shortcut Ctrl +Alt+o is in conflict with windows Alt+o . So you can't get the Polish letter 'ó' what is annoying when try to comment your code in Polish not only because the letter, but especially because jumping out of your current context. Suggestion: option for you own definition of the short cut.
10 votes -
Prevent dbForge from crashing when truncating a locked table
When using the "Truncate Table" feature on a table which has an active table lock, dbForge completely freezes up and ultimately crashes. The app should "gracefully wait" rather than crash.
3 votes
AdminPMs
(Admin, Devart)
responded
Could you please specify what product version you are using?
Please also provide us a screenshot of any possible error and perform the following:
1. Select ‘Tools → Options…’ from the main menu. The ‘Options’ window opens.
2. Navigate to the ‘Environment → Output’ branch.
3. Select the ‘Write queries sent by the program to the SQL Log’ and ‘Log application errors’ options.
4. Unselect the ‘Delete application log after closing’ option. Click ‘OK’.
5. Reproduce the issue and send us the *.log file with the latest date from the folder:
SystemDrive\Users\%UserName%\AppData\Roaming\Devart\dbForge Studio for SQL Server\ -
enable
Window headings are only sql, sql1, sql2 an not the name of the datatable.
1 vote -
Save breakpoint information when closing a query
If you set a breakpoint, then close the query, when you open the query back up, the previously set breakpoint is no longer present.
1 vote -
Search does not find all objects
Search does not find all stored procedures in a case sensitive database. The default case insensitive search misses some objects. To make it work, you must specify the exact case sensitive search string and make the search case sensitive. The default server collation in my instance was case insensitive.
1 vote
- Don't see your idea?