pbradshaw

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw commented  · 

    This is fixed in version 18.3.1+

    pbradshaw commented  · 

    This has just been getting worse and worse. I just installed SSMS 18.0, and now clicking "..." to select the *.bak file has been hanging for 12 minutes. This isn't usable.

    pbradshaw supported this idea  · 
  2. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw shared this idea  · 
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 37

    <=-=Apr 5 2010 2:21PM=-=>

    Thanks for filing this request. Please note that according to the XML 1.0 spec, the characters you have identified are not allowed inside an XML document, even as numeric character references. See

    http://www.w3.org/TR/xml/#charsets

    in particular:

    Character Range
    2 Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] /* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */

    We are very relucant to change this aspect of our XML parser without an official support from the W3C (XML 1.1 has not fully addressed the above issue and added other issues that we do not want to have to grand-father in).

    I would like to give the community the opportunity to file more up and down votes to see how you all feel about this issue. If you feel that we should add an option to accept…

    pbradshaw supported this idea  · 
  4. 28 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  7 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
  5. 266 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    87 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks everybody for providing the list. I’ve passed the info to the Visual Studio Team.

    In the meanwhile, I have 2 more requests:
    1) If you happen to have Visual Studio 2017 (version 15.9.11 or greater), could you check and see if it shows the same behavior?
    2) If you happen to have SSMS 17.9.1 on the same machine, could you check and see if it shows the same behavior?

    I’m hearing from folks here that “changing SSMS such that it disables h/w acceleration by default” is not a recommended thing to do… However, quite honestly, at this point, it may be the only option I can think about.. :-(

    -Matteo

    pbradshaw commented  · 

    I do NOT experience the problem in Visual Studio 2017, which I use every day. Version 15.9.14 with .NET 4.8.03752. I've never experienced this problem in any product other than SSMS 18.x

    SSMS 17.9.1 has never exhibited this problem for me. It's what I use on a daily basis, since I found SSMS 18.x just too buggy and problematic to work with.

    While I've seen reports from other people experiencing this problem with SSMS 16.x and up, I never have. This is all brand new to 18.x, and it happens so often it's impossible to use.

    pbradshaw commented  · 

    AMD FirePro W4100 on a Dell desktop, four monitors.
    This happens on every desktop on our development department. Not all use the AMD FireProW4100, but they're all Dell Inspiron desktops between 2 and 5 years old.

    pbradshaw commented  · 

    Here's the thing: I never experienced the problem in SSMS 16.x or SSMS 17.x … even though I have "user hardware graphics acceleration if available" set in those, just like in SSMS 18.x.

    So, without changing anything locally, the experience is significantly worse on 18.x … to the point 18.x is nearly unusable (between this and the hang when clicking "..." to try and restore a database, I've had to abandon it). This is seriously unusable and unacceptable.

    The problem also doesn't seem to happen with Ctrl-Tab, only when clicking on the tabs.

    pbradshaw commented  · 

    Interestingly, I don't see the problem nearly as frequently (or at all so far) when using Ctrl-Tab to switch tabs, but see it VERY frequently when switching by clicking on tabs with the mouse.

    pbradshaw supported this idea  · 
  6. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw shared this idea  · 
  7. 14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
  8. 86 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
  9. 87 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 176

    <=-=Nov 13 2007 12:37AM=-=>

    Hello

    Thank you for your feedback. We’re certainly considering row value constructors for a future release of SQL Server.

    - Sara Tahir
    Microsoft SQL Server

    <=-=Aug 11 2010 8:03AM=-=>

    I think row constructors would be a great and important addition to T-SQL. Just wanted to point out a few more cases that I’d love to see implemented:


    - Assignment
    -
    —————————————————————————————————-

    UPDATE dbo.T1
    SET (c1, c2, c3) = (@p1, @p2, @p3)
    WHERE keycol = @key;

    — Logically equivalent to:

    UPDATE dbo.T1
    SET c1 = @p1,
    c2 = @p2,
    c3 = @p3
    WHERE keycol = @key;

    — Or with a subquery:

    UPDATE dbo.T1
    SET (c1, c2, c3) = (SELECT T2.c1, T2.c2, T2.c3
    FROM T2
    WHERE T2.keycol = T1.keycol)
    WHERE keycol = @key;

    — Logically equivalent to:
    UPDATE dbo.T1
    SET c1 = (SELECT T2.c1
    FROM T2
    WHERE T2.keycol = T1.keycol),
    c2 =…

    pbradshaw supported this idea  · 
  10. 973 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  70 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
  11. 44 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
  12. 36 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
  13. 35 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
  14. 292 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 72

    <=-=Mar 10 2016 11:26AM=-=>

    It’s a shame that this was submitted as just a “suggestion”. It should actually be listed as a “bug” because there’s only a comparatively small set of use cases where enumeration of the result set of elements is not important.

    <=-=Mar 11 2016 12:47PM=-=>

    I agree that an order column is required; one example use case is where two lists are passed in, and ordinal positions in one list correspond to positions in the other.

    <=-=Mar 11 2016 3:12PM=-=>

    Please see the related suggestion: STRING_SPLIT needs “RemoveEmptyEntries” option, like String.Split in .NET ( https://connect.microsoft.com/SQLServer/feedback/details/2462002/ ).

    <=-=Mar 12 2016 12:02PM=-=>

    This kind of function is primarily needed for de-serializing previously serialized arrays of values of any type format-able as text.
    I therefore recommend to have the result set of this function work excellent with this use-case.

    With de-serialized arrays there is a need to…

    pbradshaw supported this idea  · 
  15. 14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw supported this idea  · 
    pbradshaw commented  · 

    I'd also like a way of retrieving the sever local time zone name (which is necessary for several functions including AT TIME ZONE) without having to resort to unsupported calls to the OS.

  16. 33 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw commented  · 

    Also seems similar to this issue, reported back on "Connect", about versions 16.x

    https://feedback.azure.com/forums/908035-sql-server/suggestions/32900263-ssms-screen-is-not-correctly-redrawn-when-switchin

    The main issue is that I have versions of SSMS from 2008R2 through 18.0 installed, and the 18.0 version is the ONLY one I'm experiencing this issue with.

    pbradshaw commented  · 

    Interestingly, if I Ctrl-Tab, the problem doesn't seem to happen. But it happens constantly when clicking the tabs. I never had this issue in previous versions (though it was reported in previous versions).

    Additionally, one time when switching between tabs with a short amount of text, and a full window of text, sometimes clicking to the short file would repaint just the short file, leaving the bottom half of the window still showing the contents of the other, larger file. That was truly disturbing.

    pbradshaw shared this idea  · 
  17. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Other  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw shared this idea  · 
  18. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw commented  · 

    I can't use SQL2017's STRING_AGG function, because this code has to work on SQL2016.

    This really needs to work this way. I consider it a bug that it doesn't.

    pbradshaw shared this idea  · 
  19. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    pbradshaw commented  · 

    This is even worse in 18.0 … in 17.x, at least it would EVENTUALLY come back and I could continue with selecting the *.bak file. I've been waiting 12 minutes now in 18.0 (just installed) and it's still "Not Responding". This bug has been around for far too long. It's EASILY reproduceable. It makes SSMS almost unusable for restoring databases.

    pbradshaw supported this idea  · 
  20. 23 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    12 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 6

    <=-=Dec 12 2016 1:42AM=-=>

    This has been reported more times than you have used SSMS. MS are too incompetent and lazy to fix it.

    <=-=Dec 12 2016 1:46AM=-=>

    Here is the link to another which also has a link to another report

    https://connect.microsoft.com/SQLServer/Feedback/Details/3109897

    please click on the I CAN TOO in the repros section

    <=-=Dec 21 2016 7:39AM=-=>

    I can replicate this on multiple different computers, each with freshly installed Windows (either 8.1 or 10) and latest of all drivers. It happens both with Intel integrated graphics (for me is HD 4600) and NVidia cards. It’s clearly a bug in how you’re using the Visual Studio shell.

    This is absolutely HORRIBLE!! When closing a tab, then attempting to execute the query in a tab that was already open and is now focused (because you just closed one), you see the wrong text in the tab, and…

    pbradshaw commented  · 

    I can reproduce this at will with a fresh install of 18.0

    Open a sql file. Now click "new query". Click back and forth on the tabs. The window contents fail to refresh at least half the time. It's very confusing and very disturbing.

    How does a bug this obvious, major, and easy to reproduce get released?

    pbradshaw commented  · 

    I can reproduce at will, constantly. Open a a tab, paste some SQL into it. Now click the "New Query" button. Switch between the two tabs by clicking on the tab headers with the mouse. At least half the time, the contents of the window will not update to reflect the tab you clicked on. About half the time it does. It's really bizarre, and really disturbing. How can a bug this big make it out to the field? It's so easy to reproduce! Happen ALL the time!

    pbradshaw supported this idea  · 
← Previous 1

Feedback and Knowledge Base