Comments
Sort by recent activity
Thanks David. / comments
Thanks David.
I had the same experience as Mark. Restarted the SQL Monitor services and the other servers came back into a monitored state. / comments
I had the same experience as Mark. Restarted the SQL Monitor services and the other servers came back into a monitored state.
Alex, I installed the release and I was able to restart one of the updated SQL Servers with the MS update and SQL Monitor went right back to monitoring the server as soon as it restarted. Thanks to the development team for getting this fixed so quickly! -Tom / comments
Alex,I installed the release and I was able to restart one of the updated SQL Servers with the MS update and SQL Monitor went right back to monitoring the server as soon as it restarted. Thanks to ...
The cumulative update we had to roll back was Microsoft KB#5009557 / comments
The cumulative update we had to roll back was Microsoft KB#5009557
ATurner said:
Hi Tom I believe this to be related to a known bug. I shall let you know once there is a fix available.
Any progress on this? Adding some screen shots. As you can see, the login for this server is sysadmin so there should be no issue with master being read-only. [image] [image] [image] / comments
ATurner said:
Hi TomI believe this to be related to a known bug. I shall let you know once there is a fix available.
Any progress on this?Adding some screen shots. As you can see, the login...
ATurner - Any progress on this? I can monitor my QA instance but not my production instance. Really do need this. / comments
ATurner - Any progress on this? I can monitor my QA instance but not my production instance. Really do need this.
Thank you for checking. I look forward to the bug fix. / comments
Thank you for checking. I look forward to the bug fix.
It is in Business Critical Gen5. / comments
It is in Business Critical Gen5.
Thanks Owen. The 10.6.5 fixed work. I'm back to being able to update SQL Prompt. / comments
Thanks Owen. The 10.6.5 fixed work. I'm back to being able to update SQL Prompt.
I have SSDT installed in Visual Studio 2019 and 2017. I don't use VS 2015. It's probably only on my machine because of SSMS 17.x which is still installed on my machine. This has never been an issue for any previous update to SQL Prompt. P.S. I don't even use SQL Prompt in Visual Studio. / comments
I have SSDT installed in Visual Studio 2019 and 2017. I don't use VS 2015. It's probably only on my machine because of SSMS 17.x which is still installed on my machine. This has never been an issue...