44 results found

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

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

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

4. search does not remember 'look in' settings

   Search does not remember 'look in' settings. The default is 'all open documents' which causes user to jump out of document (quickly enough it's easy to miss) when practically every other editor there is defaults to current document.
   This is a major issue when it comes to search/replace accidentally being triggered across documents which is almost never what you want to do.
   Either allow the default to be changed or remember the previous setting.

   3 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  ·  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. Executing SQL with named parameters causes a dialog to show up asking for the parameters.

   If I have the following SQL:

   EXEC sp_rename @objname='ardbPcbRelatedGames.PcbRelatedGamesID', @newname='PcbRelatedGameID', @objtype='COLUMN'

   A dialog will pop up asking for the values for @objname, @newname and @objtype. Those already have values provided and it doesn't need to ask me for them.

   3 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…)
   under review  ·  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

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

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

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

   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

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

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

11. bug:Bug in table editing

    SELECT * FROM BaseProfile A
    JOIN BaseProfile_Trl A1 ON A.ID = A1.ID WHERE A1.id=20200215

    edit table:BaseProfileTrl,After editing one row of data, I found that the entire table got updated.

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

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

13. 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 checkbox or similar to cause only the name, sans schema, to be displayed.

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

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

    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

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

    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

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

    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

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

    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

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

    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

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

    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

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

    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