Comments
Sort by recent activity
I believe this is the setting your looking for: [image] / comments
I believe this is the setting your looking for:
I tried to make an example to show in the most basic way what is going wrong. So the value in the single cell is 2.1 . But when i click 'Show aggregate result' it gives a sum, average, min and max of 21 . It erases the decimal seperator. This also happens when you select multiple rows. In the Netherlands we normally use the comma (,) for the decimal seperator. So maybe my regional settings in combination with SSMS messes things up. Excel for instance uses the regional settings correctly(a comma) but SSMS does not it insists on using a dot (.) for the seperator on decimal values. / comments
I tried to make an example to show in the most basic way what is going wrong. So the value in the single cell is 2.1 . But when i click 'Show aggregate result' it gives a sum, average, min and max ...
Super! I am going to test this out. Thanks for the help! / comments
Super! I am going to test this out. Thanks for the help!
I have found what triggers this problem. Sometimes i leave my workstation running. During the night our servers close all inactive remote desktop sessions. When this happens SSMS starts with the question if i want to recover queries after SSMS was closed expectantly. I click no and then SQL Prompt restores them as i expect but with the red squiggle lines indicating that objects do not exist. Closing and reopening the queries solves this issue. I will log out from now on so for me this problem should go away.
/ comments
I have found what triggers this problem. Sometimes i leave my workstation running. During the night our servers close all inactive remote desktop sessions. When this happens SSMS starts with the qu...
When it occurs it happens on all 3 servers i have open query windows to. They are local servers running SQL version 15.0.4261.1 . Except for one which runs version 13.0.6419.1 . / comments
When it occurs it happens on all 3 servers i have open query windows to. They are local servers running SQL version 15.0.4261.1 . Except for one which runs version 13.0.6419.1 .
We also have this problem. The person who installed the update did not have the issue. But all other users did. Repairing SSMS installation fixed it for that user but broke it for the others. / comments
We also have this problem. The person who installed the update did not have the issue. But all other users did. Repairing SSMS installation fixed it for that user but broke it for the others.
@Kurt_M Yes, sometimes i query the linked servers in the way you describe. / comments
@Kurt_M Yes, sometimes i query the linked servers in the way you describe.
All linked servers are SQL server 2016 or higher. Could the linked server for Active Directory ServiceInterfaces(ADSI) cause this pop-up? / comments
All linked servers are SQL server 2016 or higher. Could the linked server for Active Directory ServiceInterfaces(ADSI) cause this pop-up?
I can cancel the message and continue using SQL prompt. It looks like all functionality keeps working. / comments
I can cancel the message and continue using SQL prompt. It looks like all functionality keeps working.