39 results found
-
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 -
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 -
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 -
Default column for datetime added getdate() as default.
It will not save that column. I get an error about the )
1 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 -
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 -
update data in grid when using join updated more than the one row
I changed the grid to update a table, but the update did not use the primary key of the selected row and updated thousands of rows! My expectation is that the PK of the selected "update" table would be used to update one row. This is a terrible bug and makes the update feature unusable when using a join.
1 vote -
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.
1 vote -
Increase UI response and overal performance (SQL Data Compare)
Opening windows takes much time.
I believe the most often used features must work as fast as possible to provide the best experience (including not only processing but opening windows).
See how long it takes to open "New Data Comparison" and moving through tabs "Source and Target", "Options", "Mapping".
The app itself opens slowly as well opening "dcomp"-files.1 vote -
Allow the "=" sign to be part of a keyboard shortcut
Apologies: not sure if this is a bug or a feature, but would love to include the equals sign (=) as part of a keyboard shortcut. It is in SSMS ....
1 vote -
Error on create for existing object
When I have a create statement (without DROP) and the object exists - then SqlStudio should really give an error as SSMS! Currently no indication is made and object remains unchanged!
1 vote -
Improve keyboard support
I click "New Data Comparison" (or "New Schema Comparison"), then ALT-W to open the "Database Connection Properties" dialog, then TAB to get into the "Server" input box. Once there, I type a part of the name of the server and the list of available servers works nicely!
It seems that I must use down DOWN ARROW to select the server from the list and press ENTER before I can get out.
However, if I type the entire server name, I can't get out of that box! Pressing TAB or ENTER does nothing.
1 vote -
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 -
Cannot modify sql login associated with an active directory group
Sql logins associated with an active directory group (windows authentification) are shown in data explorer's security/users node, but not listed in the security manager.
Thus, if you double click on it in the explorer "object does not exits" pop up and the user cannot be edited.Enterprise Edition 5.7.31
1 vote -
Error when adding extended property in unicode
When I add an extended property (eg. description) in unicode, the generated script does not have N prefix for unicode value. As a result, my added property value gets unreadable after save.
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
- Don't see your idea?