393 results found

1. Need to be able to flag whether to jump to the grid or not after running a query

   Need to be able to flag whether to jump to the grid or not after running a query.

   What happens now with it jumping to the grid...something I don't think I've ever had in my head 'gee wish I could navigate the grid of data'...so now I have to pick up my mouse, put the focus back on the query area because...most of the time I am querying info and changing it.

   Annoying enough, along with several other constant pain points, I am going back to SSMS.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. "Unique key is missing" bug when editing

   Using DbForge Studio for Sql Server Enterprise Edition 2025.3.107 (License Type: Perpetual) :

   My table (FundDocument ) has a PK defined : FundDocumentId INT NOT NULL , unique.
   1) When I run this T-Sql it shows the record normally without problems when I go into edit mode:
   SELECT
   *
   FROM funddocument
   WHERE FundDocumentId = 103741;

   2) But when I run this T-Sql it says "Unique key is missing" when I go into edit mode:
   DECLARE @id INT = 103741;
   SELECT
   *
   FROM funddocument
   WHERE FundDocumentId = @id;

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Text insert with vertical ( HOLD ALT Select Column ) broken in version 2025.3.107

   This worked in the version last version ( 7.x.x? ) of DB ForgeStudio for SQL SERVER prior to the 2025 series... How can I down grade until this is fixed?

   Steps to reproduce.
   - Place Vertical Bar in first column
   - HOLD ALT KEY
   - SELECT TEXT COLUMN UP
   - <ERROR HERE> TYPE ANY CHARACTER ( {COMMA} " , " | {SINGLE QUOTE} " ' " )

   No text inserted

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Right click on a view should give you the option to "Modify via SQL" the "Go to Definition" feature entirely fails with an OpenDataSource

   Right click on a view should give you the option to "Modify via SQL" the "Go to Definition" feature entirely fails with an OpenDataSource.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Bugs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Default column for datetime added getdate() as default.

   It will not save that column. I get an error about the )

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  2 comments  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  1 comment  ·  Features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Tab Labels should reflect something about the object, not fictitious filenames.

   It would be a great help to have the tab labels show the name of the stored procedure or opened table instead of the fictitious filenames used now.
   I often have a bunch of tabs open and have no way of knowing which is which unless I remember the order I opened them. Having the name of the object opened would allow me to know at a glance.
   This would be most helpful with Stored Procedures and Functions.

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  1 comment  ·  Features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Results Grid truncates fractional seconds and ignores SQL Server datetime precision

   Summary
   Data grid does not display fractional seconds in the Results Grid according to the actual precision defined by SQL Server datetime datatypes. The grid appears to default to millisecond display regardless of the underlying column scale.

   Problem Description
   SQL Server supports multiple datetime-related datatypes, each with well-defined precision and storage semantics:

   smalldatetime (minute precision)
   datetime (fixed, ~3.33 ms increments)
   datetime2(p) where p = 0 through 7
   datetimeoffset(p) where p = 0 through 7
   expressions such as AT TIME ZONE, which return datetimeoffset(7)

   In dbForge Studio for SQL Server version 2025.2.138, the Results Grid does not display fractional seconds based on the actual datatype precision. Instead, values are rendered as if they were millisecond-based, even when the underlying column type is datetime2(5), datetime2(7), or datetimeoffset(7).

   As a result, higher precision stored in SQL Server is visually truncated in the grid, which is misleading. All datetime values appear to show only 3 fractional digits. Higher precision values (5 or 7 digits) are not displayed. No visible distinction between datetime2(3) and datetime2(7)

   Expected Behavior
   The Results Grid should display fractional seconds based on the actual SQL Server datatype precision, for example:

   smalldatetime: no fractional seconds
   datetime: SQL Server-defined millisecond resolution
   datetime2(0): no fractional seconds
   datetime2(3): 3 fractional digits
   datetime2(5): 5 fractional digits
   datetime2(7): 7 fractional digits
   datetimeoffset(7): 7 fractional digits plus timezone offset

   This matches the behavior of SQL Server Management Studio and Azure Data Studio and is critical for accurate inspection of time-sensitive data.

   Reproduction Transact-SQL code:

   SET NOCOUNT ON;
   
   IF OBJECT_ID('tempdb..#TestDates') IS NOT NULL
       DROP TABLE #TestDates;
   
   CREATE TABLE #TestDates
   (
       RowId int IDENTITY(1,1) PRIMARY KEY,
       Dt_smalldatetime smalldatetime,
       Dt_datetime datetime,
       Dt_datetime2_0 datetime2(0),
       Dt_datetime2_3 datetime2(3),
       Dt_datetime2_5 datetime2(5),
       Dt_datetime2_7 datetime2(7),
       Dt_datetimeoffset_7 datetimeoffset(7)
   );
   
   INSERT INTO #TestDates
   (
       Dt_smalldatetime,
       Dt_datetime,
       Dt_datetime2_0,
       Dt_datetime2_3,
       Dt_datetime2_5,
       Dt_datetime2_7,
       Dt_datetimeoffset_7
   )
   VALUES
   (
       CAST('2026-02-03T14:32:00' AS smalldatetime),
       CAST('2026-02-03T14:32:10.123' AS datetime),
       CONVERT(datetime2(0), '2026-02-03T14:32:10', 126),
       CONVERT(datetime2(3), '2026-02-03T14:32:10.123', 126),
       CONVERT(datetime2(5), '2026-02-03T14:32:10.12345', 126),
       CONVERT(datetime2(7), '2026-02-03T14:32:10.1234567', 126),
       TODATETIMEOFFSET(CONVERT(datetime2(7), '2026-02-03T14:32:10.1234567', 126), '+00:00')
   );
   
   -- What the data grid displays by default
   SELECT
       RowId,
       Dt_smalldatetime,
       Dt_datetime,
       Dt_datetime2_0,
       Dt_datetime2_3,
       Dt_datetime2_5,
       Dt_datetime2_7,
       Dt_datetimeoffset_7
   FROM #TestDates;
   
   -- what is expected to be shown in the data grid
   SELECT
       RowId,
       CONVERT(varchar(50), Dt_smalldatetime, 126) AS SmallDt_rounded_minute_precision,
       CONVERT(varchar(50), Dt_datetime, 126) AS Dt_datetime_quantized,
       CONVERT(varchar(50), Dt_datetime2_0, 126) AS Dt2_0_expected_0_digits,
       CONVERT(varchar(50), Dt_datetime2_3, 126) AS Dt2_3_expected_3_digits,
       CONVERT(varchar(50), Dt_datetime2_5, 126) AS Dt2_5_expected_5_digits,
       CONVERT(varchar(50), Dt_datetime2_7, 126) AS Dt2_7_expected_7_digits,
       CONVERT(varchar(50), Dt_datetime2_7 AT TIME ZONE 'UTC' AT TIME ZONE 'Central Standard Time', 126) AS Central_expected_iso,
       DATEPART(TZOFFSET, Dt_datetime2_7 AT TIME ZONE 'UTC' AT TIME ZONE 'Central Standard Time') AS Central_expected_tzoffset_minutes
   FROM #TestDates;
   
   -- show precision for each datatype
   SELECT
       RowId,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_smalldatetime), 'Scale') AS Scale_smalldatetime,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime), 'Scale') AS Scale_datetime,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_0), 'Scale') AS Scale_datetime2_0,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_3), 'Scale') AS Scale_datetime2_3,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_5), 'Scale') AS Scale_datetime2_5,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_7), 'Scale') AS Scale_datetime2_7,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetimeoffset_7), 'Scale') AS Scale_datetimeoffset_7
   FROM #TestDates;
   
   -- show basetype and precision for explicit conversions in SELECT
   SELECT
       RowId,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_7), 'BaseType') AS BaseType_dt2_7,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_7), 'Scale')    AS Scale_dt2_7,
   
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_7 AT TIME ZONE 'UTC'), 'BaseType') AS BaseType_utc_as_dto,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_7 AT TIME ZONE 'UTC'), 'Scale')    AS Scale_utc_as_dto,
   
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_7 AT TIME ZONE 'UTC' AT TIME ZONE 'Central Standard Time'), 'BaseType') AS BaseType_central_as_dto,
       SQL_VARIANT_PROPERTY(CONVERT(sql_variant, Dt_datetime2_7 AT TIME ZONE 'UTC' AT TIME ZONE 'Central Standard Time'), 'Scale')    AS Scale_central_as_dto
   FROM #TestDates;
   
   IF OBJECT_ID('tempdb..#TestDates') IS NOT NULL
       DROP TABLE #TestDates;
   

   Why This Matters

   Developers rely on the Results Grid to debug ordering, uniqueness, and event timing
   Truncated display can falsely suggest rounding or data loss
   This is especially problematic for telemetry, logging, and distributed systems
   Displaying fewer fractional digits than are stored is misleading, even if the underlying value is correct

   Request
   Please restore or add functionality so that the Results Grid:

   Displays fractional seconds based on the actual SQL Server datatype precision
   Correctly distinguishes between datetime, datetime2(p), and datetimeoffset(p)
   Applies this behavior consistently to table columns, computed expressions, and AT TIME ZONE results
   Optionally allows overriding the display format, but defaults to datatype-accurate rendering

   Environment
   dbForge Studio for SQL Server: 2025.2.138
   SQL Server version: 2017

   Summary
   Data grid does not display fractional seconds in the Results Grid according to the actual precision defined by SQL Server datetime datatypes. The grid appears to default to millisecond display regardless of the underlying column scale.

   Problem Description
   SQL Server supports multiple datetime-related datatypes, each with well-defined precision and storage semantics:

   smalldatetime (minute precision)
   datetime (fixed, ~3.33 ms increments)
   datetime2(p) where p = 0 through 7
   datetimeoffset(p) where p = 0 through 7
   expressions such as AT TIME ZONE, which return datetimeoffset(7)

   In dbForge Studio for SQL Server version 2025.2.138, the Results Grid does not display fractional seconds based… more

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  2 comments  ·  Bugs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. remote changes source control

   For source control (GIT) at the remote changes tab add a ignore/delete option.

   I started working with the database and deleted/renamed some stored procedures. When I detached and attached my source control (GIT) it wants to add the procedures which I have removed.
   This is fine when someone else changed it, but now I specifically want to delete this procedures. When working with this I can add them again, to delete them afterwards, or I can delete them in the folder and check them in with GIT, bypassing dbForge.

   The easy solution would be to add a ignore/delete/keep local option which would ignore the 'Remote changes' and save my database version to GIT.

   For source control (GIT) at the remote changes tab add a ignore/delete option.

   I started working with the database and deleted/renamed some stored procedures. When I detached and attached my source control (GIT) it wants to add the procedures which I have removed.
   This is fine when someone else changed it, but now I specifically want to delete this procedures. When working with this I can add them again, to delete them afterwards, or I can delete them in the folder and check them in with GIT, bypassing dbForge.

   The easy solution would be to add a ignore/delete/keep local option… more

   1 vote

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   planned  ·  1 comment  ·  Features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Make it possible to seek on Connections in the SQL Servers area (On the left)

    Would like to seek for Connection names on the left SQL Connections/servers names. We have 400-500 Serveres and it will make it a lot faster to find the connections.....

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Integration with Windows Task Scheduler
    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Ability to perform Load Test for query after being modified in Profiler
    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Create a named default constraint when add column
    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add schema comparison option to ignore CLR objects

    Add an option to the Schema Compare feature to ignore CLR objects(CLR Type, CLR Procedure, CLR Function, Aggregate Function).

    Note that the option shouldn't affect usual objects (Function, Procedure, User data type, User table type).

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Duplicate query

    I would like to see an option on tab context menu. Often I need to duplicate (clone) my query. So another useful option in context menu when clicking on Query Tab would be "Duplicate query" or something like that.

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Schema/data comparison user interface

    Hi. I'm currently evaluating studio for sql server. OK, i'm primarily interested in schema and data comparison but evaluating the whole studio product. Here's a couple of things which i think would be useful additions/modifications to the UI of the product(s) (schema and data comparison).

    1. The "recent files" section. I think it would be better if there was a "favorites" section above "recent files" and the user was able to choose whether he wishes to have the "recent files", "favorites" or both sections shown. Also, comparison projects could have an editable title so in the "favorites" section, one could see the title instead of what appears now ("DB (Server1 vs Server2)").
    2. In the results of the schema comparison, tables are grouped depending on whether they are different or only in one of the two servers. I've used other comparison programs and i find the "two trees approach" more useful and clear than the one you are using. Imagine two trees in the screen. The left one shows the source server's items and the right one the destination. There is a top level in the tree containing the names of all items taking place in the comparison (tables, views, functions, procs, etc). Under there, all names (i.e. of the tables) are shown with different colors depending on whether they are the same, different or non-existant. Each table name could also be expandable so one could see its columns, indexes, keys, default values, etc. In front of the tree a checkbox should exist so one would be able to check it and make it a part of any sync script generated. Under the trees, a section exists like the one you have now, showing the left and right "create" scripts of the tables. If you have a visual image of a DB in your mind with all tables sorted alphabetically, it's easier to work with it like this than having all tables/views grouped by "only in source server, different, etc").
    3. Clicking on a "recently used" item (for data comparison only), the "edit comparison" window should appear in the "mapping" section, just in case someone wishes to select a different set of tables to be compared. When you have a local DB and a remote one with a slow connection, you wish to select the comparison items before starting the process which might take several minutes to complete.
    4. The "change sync direction" concept in the data comparison window is a little confusing. It would be much better if the whole window was changed in such a way as if the comparison was made from the beginning with the two servers swapped. Swap the values of the grid columns "only in source" and "only in target" and not the titles. The same with the tabs.

    Hi. I'm currently evaluating studio for sql server. OK, i'm primarily interested in schema and data comparison but evaluating the whole studio product. Here's a couple of things which i think would be useful additions/modifications to the UI of the product(s) (schema and data comparison).

    1. The "recent files" section. I think it would be better if there was a "favorites" section above "recent files" and the user was able to choose whether he wishes to have the "recent files", "favorites" or both sections shown. Also, comparison projects could have an editable title so in the "favorites" section, one could see… more
    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Ability to change schema for existing procedure
    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Open schema/data comparison files

    Opening a saved or recent file (schema or data comparison) should not start comparing directly but instead open the "Edit comparison" dialog in the Mapping tab, just in case the user wishes to change the items being compared. When using slow connections between servers, this would be very helpful. If you feel may users would not like such a change, it could be made configurable in the application options (a "Don't start comparison immediately when opening a comparison file" checkbox).

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Ability to create schema from Database Explorer

    Move the functionality of Security Manager to Database Explorer in order to access it in a more intuitive way.

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Ability to designate connection as Production and define rules

    I should be able to designate a connection as 'Production' and define rules as to which statements are allowed/disallowed.

    Production will not allow any DELETE statements. UPDATE statements will need confirmation before they execute.

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating