32 results found
-
Unable to fix bugs
I have reported a few bugs over the past few months, and although you are good at responding and looking into this there seems to be a few bugs that you can't seem to get right.
Upgrading. It is always painful. Links that you publish to download the upgrade don't work. There are always licencing/activation problems, etc. I upgraded yesterday as advised (having gone through the normal pain to find the right place to download), and everything seemed to work. Yet today I am asked to enter my activation key yet again. Why can't you just make the upgrade seamless?…
1 vote -
5.4.211 crashes upon schema synchronization
5.4.211 crashes upon schema synchronization
1 vote -
Autocomplete doesn't work if table belongs to schema and no alias or schema name used in join.
Example:
select *
from Schema1.Table1 join Schema1.Table2 on Table1.[AutoComplete doesn't show table fields]select *
from Schema1.Table1 T1 join Schema1.Table2 T2 on T1. [AutoComplete works properly]1 voteThis feature is implemented in dbForge SQL Complete, v5.6 https://www.devart.com/dbforge/sql/sqlcomplete/download.html
-
F3 button not working properly
Normally, if I do an incremental search (CTRL+I) or a normal search (CTRL+F), pressing F3 takes you to the next location of your search text in the current file. With DBForge it seems to jump all over the place. The only place it doesn't take you to is the next location in the current file, which basically makes it impossible to use.
1 votePlease try the latest version 5.4 https://www.devart.com/dbforge/sql/studio/download.htmlhttps://www.devart.com/dbforge/sql/studio/download.html
-
Skin styled images not showing in menu
If you set "Use styled images" in options, all the icons/images use this setting except for the cell edit cascade menu... as shown here:
1 vote -
Invalid error line for "Display Estimated Execution Plan"
use this script for test:
DECLARE @FILENAME AS NVARCHAR(500),
@FILENAMEPRE AS NVARCHAR(500),
@FILENAMESUF AS NVARCHAR(500),
@SQLSTMT AS NVARCHAR(MAX)SET @SQL_STMT = 'SELECT t1.*, CASE WHEN c1 IS NULL THEN ''Y'' ELSE ''N'' END AS [COLUMN1], t2.c3 FROM t1 LEFT JOIN (SELECT * FROM (VALUES (''v1'',''v1'',''v1''), (''v2','v2','v2''), (''v3'',''v3'',''v3'')) RET (c1, c2, c3)) t2 ON t1.c1 = t2.c2 '
if you press "Display Estimated Execution Plan", then the first line will be highlighted with an error: Incorrect syntax near ','.
But if you press "Execute" then correct one will be highlighted1 voteThis issue is fixed in the latest product version 5.4 https://www.devart.com/dbforge/sql/studio/download.html
-
Autosize
Last beta version does not autosize the result set (regression). You have to retrieve multiple times to get the results aligned properly.
1 voteThis issue is fixed. Please upgrade to the latest version https://www.devart.com/dbforge/sql/studio/download.html
-
Ao tentar executar consulta na primeira vez
Quando executo uma consulta pela primeira vez, após a carga da aplicação, nada é exibido. Somente após fechar uma das janelas é que consigo voltar a visualizar a saída dos resultados.
1 vote -
Hi. I suggest to add the feature for select only a database, on Connection Properties.
Include the option for to open only the connection with database specified.
1 vote -
DBForge Studio is not handling DATETIME2 in MSSQL Server
CREATE TABLE #Table1 ( c1 int, c2 DATETIME2)
;SELECT * FROM #Table1;
INSERT INTO #Table1 (c1,c2) VALUES (1, SYSUTCDATETIME ());
--dbforge returns: 7/29/2015 8:58:48 AM
--sqlstudio returns: 2015-07-29 09:00:32.5318459-- we are missing the nanoseconds
1 voteThis can be setup as follows:
1. Select ‘Tools → Options’ from the main menu. The ‘Options’ window opens.
2. Navigate to the ‘Data Editor → Formatting’ branch.
3. Select ‘DateTime’ from the ‘Data type’ dropdown menu.
4. In the ‘Predefined Formats’ list, select ‘General date/time (longtime with microseconds)’.
5. Click ‘OK’. -
Profiling mode should use parameter
I can set parameter for my query. But if I use profiling mode, DBForge 5.0.337 ignore the parameters.
0 votesThe Final Release of dbForge Studio for SQL Server, v5.1, where this issue is fixed, is available for downloading https://www.devart.com/dbforge/sql/studio/download.html
Thank you for your help in improving dbForge Studio for SQL Server.
-
Problems with schema refresh
I use version 4.5.60 and do the following: I edit a table (remote connect to SQL2012Express) and add two new columns (one bit, one int) with NOT NULL and Default Value. I click "Script change" and I execute only the two ADD COLUMN statements. It works, I check it with "Retrieve data". I close all tabs and go to again to "Edit table". I get the old schema (without the new two columns). I close your application and start it again: all works fine!
0 votes
- Don't see your idea?