40 results found
-
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 -
13 votes
-
Commit in Git
After making Commit several times in Git, dbForge Studio For SQL starts eating a lot of RAM
12 votes -
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 -
Relationship names on a DB diagram are not "comments". Need ability to show table descriptions independent of showing relationship names.
When "show comments" is selected, both table descriptions and the names of relationship lines are displayed. The relationship names are not comments, and mostly clutter up an otherwise clear and concise diagram. Show comments should only show table "comments"; a separate button/option is needed to display relationship names for those who want to see them (I do not).
6 votes -
The toolbar moves every time I click execute query or click away and back to the window. I put them where I want them and they reset with e
I customize the tool bar and arrange them how I want them and the reset on their own if I do anything like execute a query, move to another tab and move back, etc. They should lock in place and be the same on each query window.
4 votes -
Disconnect studio from Delphi
In Delphi if you use the Devart SQL server components, dbForge studio is launched automatically. There is a bug if you close Delphi, studio hangs and is no longer usable.
3 votes
AdminDevart
(_, Devart)
responded
Could you please let us know what version of dbForge Studio for SQL Server you are using?
-
Pewrmit override Alias name assignment during Query design when LONG table names prevent viewing of columns/fields in the columns window.
From a SSMS Query window execute a statement like:
CREATE TABLE #tempAllBin (ID Int);
Then, in your query designed, browse to the TempDB and locate the new temp table. It will have a name like: "#tempAllBins________________________________________________________________________________________________________000000090BC2".
Select this table name and drag it into the query designer window in your tool. - The length of the table name makes it impossible to view the column names in the column window, as well as a number of other complcations arising from the length of that table name. I see no way to assign a SHORTER ALIAS Name in your query designer…3 votes -
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 -
Ads within DbForge Express interfere with other programs
Everytime I start dbForge Studio Express I get an advertisement about Cyber Monday discount. Don't get me wrong: I love the discount, but I don't need to see the ad every time I started dbForge Studio. More importantly: the advertisement interferes with other programs, because it shows after a while when I switched to another program. It'd like to see the ad only in dbForge Express and an option added called 'Do not show again'.
3 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 -
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 -
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 -
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\ -
Data Viewer is not working after a day of application activity
Data Viewer is not working after a day of application activity
Data Viewer stops displaying anything in a day after being started. You will need to restart the application so it starts working again.
3 votesAdminDevart
(_, Devart)
responded
Please let us know if the issue still persists in the product version 4.0 http://www.devart.com/dbforge/sql/studio/download.html
-
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 -
Edit wrong trigger
When triggers in different schema have the same name the wrong one can come up when using the editor.
ex. in the same database
netsuite.trgItemHistory
fitmentdashboard.netsuite.trgItemHistory1 vote -
Multiple Document Interface too sluggish
The MDI component used has always been problematic. For a time it would regularly crash, but this was eventually fixed. However, I can't help but to notice how sluggish it is when the monitor is greater than 1280x1024 or if you the tabs are split. Some kind of improvement in performance would be desirable.
1 vote -
Table along with its column becomes not visible once added
After a table is added, it's not visible with its columns in SQL Editor.
1 vote -
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
- Don't see your idea?