390 results found

1. SQL Editor - add word wrap option

   I would suggest that the possibility of having in the editor the features of "Word Wrap" and "Show visual glyphs for word wrap" as they exist in the editor of Visual Studio be added.

   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…)
   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

2. Existence logic needed for triggers

   When a new trigger is created, the script tests for existence first. So if the trigger does not exist, it will not create it. It should not test for existence as it will never create the trigger. It's unnecessary to check the object's existence if the product is using CREATE OR ALTER trigger.

   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…)
   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

3. 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. This is a show-stopper for me using the 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.… 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…)
   1 comment  ·  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

4. formating Value and Numbers in result of Query Like show numbers separated by separators

   There is an option to change the way Date and Date-Time shown is the result of Query if you add other thing like show numbers separated by separators etc.

   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…)
   1 comment  ·  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. Clear google sheet before exporting

   Would be great if before exporting data into from SQL Server to google sheets the sheet is cleared, that way if in a second export less rows are exported there are no risk in export duplicates records.

   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…)
   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

6. Executing a query across multiple servers

   The only thing that prevents me from using DBForge is the inability to run a single sql query on 10 different SERVERS simultaneously and see the aggregated resultset. In SSMS you can simply create a folder and put all of your server connections into that folder and then when you right click on the folder it allows you to connect to all X servers in that folder simultaneously. If you run a top10 query and you have 10 servers configured in that folder you get back a single 100 record resultset. Without a feature like this I can't leave SSMS because we have our system sharded across multiple servers. Thank you!

   The only thing that prevents me from using DBForge is the inability to run a single sql query on 10 different SERVERS simultaneously and see the aggregated resultset. In SSMS you can simply create a folder and put all of your server connections into that folder and then when you right click on the folder it allows you to connect to all X servers in that folder simultaneously. If you run a top10 query and you have 10 servers configured in that folder you get back a single 100 record resultset. Without a feature like this I can't leave SSMS… 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…)
   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. Data Pump pass through imported file name

   When it comes to bulk Data Pump imports from multiple files (e.g. Excel, *.csv), I'd really appreciate the ability to pass through the source import file name (as text) to a dedicated column within the destination SQL Server data table against each imported record.

   Personally, I use the DevOps PowerShell Automation import pathway and would find it a really handy addition for basic audits if it was accessible as a parameter on Invoke-DevartDataImport

   Thanks!

   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…)
   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. Orderly Fashion Data Pump (From parent to children + referential integrity)

   I am trying to do a data pump but once it is finished the data is almost useless because I don't need 1,000 records per-table, but as many as meaningful are, the children records derived from smaller amounts of records in its corresponding Mater or Parent tables

   So If have for instance ... let's say Businesses (1) and Stores (2) so I'd like to pump data just for these entities not 1,000 business and 1,000 stores but 1,000 billing records, 10,000 stock count records, 8,000 items catalog for each store ... derived from previous node ... like a tree structure of data-pumps (data-pump01, data-pump02, data-pump03, ... , data-pump99 ... and so on

   It would be good if we could go increasingly seeding data to the master tables and later going on adding non-initially-added-tables so the newest data-pump will pump data into the newly selected tables using the values alredy stored in the database via the initial data-pump and in that way using the data stored in those previous records to create the children-ones

   Just an idea !!!

   P.S.: FOREIGN LANGUAGE DICTIONARIES WILL BE GREAT TOO (Caps just for distinguishing the 2 different ideas written here)

   I am trying to do a data pump but once it is finished the data is almost useless because I don't need 1,000 records per-table, but as many as meaningful are, the children records derived from smaller amounts of records in its corresponding Mater or Parent tables

   So If have for instance ... let's say Businesses (1) and Stores (2) so I'd like to pump data just for these entities not 1,000 business and 1,000 stores but 1,000 billing records, 10,000 stock count records, 8,000 items catalog for each store ... derived from previous node ... like a tree structure… 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…)
   2 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

9. As a developer, I'd like to be able to check in custom data generator configurations...

   As a developer, I'd like to be able to check in custom data generator configurations with the rest of my project's configuration into source control.

   Currently, the xml configuration files are stored in a separate far-off location /Users/Public/... and this makes it not ideal if you want to version your generator configurations to share with the rest of the team through Git, as an example.

   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…)
   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. I'd like to be able to edit or delete user defined (custom) data generation configurations directly from the GUI

    I'd like to be able to delete user defined (custom) data generation configurations directly from the GUI.

    Currently, you can create (but not delete, nor edit) user defined custom data generator configurations easily.

    Often it is necessary to delete these custom configs because you've created new ones...or saved it too many times...or for other reasons. However, there's no option to delete from the GUI. In order to delete them, you have to find their location and delete xml files found under C:\Users\Public\Public Documents\Devart\dbForge...\Data Generators... there you're presented with only timestamped files with no naming that indicates which user defined generation this is.... because of this you have to open each one in a text editor (there may be, as in my case, more than a couple dozen) to see if that file is the right one you want to delete. This is tedious and error prone. Here is an example of the list of files you need to sort through to determine what you want to delete:

    "C:\Users\Public\Documents\Devart\dbForge Studio for SQL Server\Data Generators\UserDefined_2024-02-27-205254863.xml"

    I'd like to be able to delete user defined (custom) data generation configurations directly from the GUI.

    Currently, you can create (but not delete, nor edit) user defined custom data generator configurations easily.

    Often it is necessary to delete these custom configs because you've created new ones...or saved it too many times...or for other reasons. However, there's no option to delete from the GUI. In order to delete them, you have to find their location and delete xml files found under C:\Users\Public\Public Documents\Devart\dbForge...\Data Generators... there you're presented with only timestamped files with no naming that indicates which user defined generation… 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…)
    2 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

11. 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 new databases connection properties, you have to create a brand new database generation file for the new database and take it from that.

    ...Kris

    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… 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…)
    1 comment  ·  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

12. Is it possible to change the default location of .dgen files?

    The default location for custom data generation configs is:

    C:\Users\Public\Documents\Devart\dbForge Studio for SQL Server\Data Generators

    This is different than the location for the other project-related files and this makes it tough to check in and share, etc.

    Is it possible to change this default location?

    I have a feature request in about this, but maybe there's a hack or even something I'm missing to set this location?

    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…)
    2 comments  ·  Questions  ·  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. Autocomplete Improvement Suggestion

    Dear Devart Team,

    I suggest enhancing your autocomplete feature by making the first option selectable with the tab key. This would reduce the current two-step process (typing additional letters or using the mouse) to a single action, improving efficiency and user experience.

    Thank you for considering this improvement.

    Best regards,

    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…)
    1 comment  ·  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. Block Selection in Editor with Paste is broken

    When you do a Block Selection (ALT + Drag Mouse) to select a block of text then you paste into that, the results are corrupt.

    I can provide video or pictures for additional Details.

    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

15. Easier Way to change the database category

    It would be helpful to have an easier way to change the Category of a database other than in the Tool > Options menu as a server could contain a production database and a sandbox database for example. I suggest either adding it to the right click menu when right clicking on a database, or to the properties.

    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  ·  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. Add option to disable drag and drop in text editor

    In Tools, Options dialog on the Text Editor, Advanced tab, add a checkmark "Allow text to be dragged and dropped". See MS Word for an example on their Advanced options tab.

    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  ·  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. synonym

    It would be great if in Database Explorer objects (i.e. tables/views/SPs/functions), the context menu contained an option "Generate Script As/Synonym", which would create a "create synonym" script for the selected object(s). That way, this script could be executed in another database to create synonyms to the original DB's objects.

    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  ·  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

18. 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…)
    1 comment  ·  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

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

20. "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