Comments
Sort by recent activity
Hi @amit987
This problem is a result of our polling query, which regularly runs for each user to look for changes to your database objects. This runs for two purposes:
1- to display the 'blue blob' next to an altered object
2- to display the name of the user who made the change, if you're working in shared mode.
Unfortunately, once a user clicks on a linked DB, the poller will continue to run for that DB until SSMS is closed.
There are couple of things you can try: Reducing the polling interval - this will mean the blue blobs will take longer to appear but a refresh of the commit tab will bring them right up; Also if you don't check changes to static data will also help. To change the settings, you'll need to go to global options:
[image]
Also making sure only people that need rights to the commit history have rights to the trace DB could also limit the amount of deadlocks. / comments
Hi @amit987
This problem is a result of our polling query, which regularly runs for each user to look for changes to your database objects. This runs for two purposes:
1- to display the 'blue blob'...
Hi @anotaro and @twurm Thanks for posting and sorry for the inconvenience caused. We are not aware of this issue and couldn't reproduce it with the latest version. Can you please upgrade to the latest version and test again? / comments
Hi @anotaro and @twurm Thanks for posting and sorry for the inconvenience caused.We are not aware of this issue and couldn't reproduce it with the latest version.Can you please upgrade to the lates...
Hi @DX_Frank ,
Thanks for the style file.
However I still couldn't reproduce the issue with it. Can you please upgrade to the latest version (9.0.8.3873 - January 31st 2018) and test again?
If problem persists, can you copy the style file from your co-worker or recreate a new one and try again? / comments
Hi @DX_Frank ,
Thanks for the style file.
However I still couldn't reproduce the issue with it. Can you please upgrade to the latest version (9.0.8.3873 - January 31st 2018) and test again?
If prob...
Hi @DX_Frank
I'm afraid we still couldn't reproduce the issue given the information you have supplied.
Can you please format it using the default format style? Does the issue still occur?
So sorry for the inconvenience caused. / comments
Hi @DX_Frank
I'm afraid we still couldn't reproduce the issue given the information you have supplied.
Can you please format it using the default format style? Does the issue still occur?
So sorry ...
Hi @torsten.strauss I'm pleased to let you know it's fixed now and please upgrade to the latest version. You can also see TABLERESULTS in the intellisense after typing WITH. / comments
Hi @torsten.strauss I'm pleased to let you know it's fixed now and please upgrade to the latest version.You can also see TABLERESULTS in the intellisense after typing WITH.
Hi @torsten.strauss
Thanks for reporting it!
We've logged it as SP-6795 in our internal bug tracking system. Please keep an eye on the release note!
Thanks. / comments
Hi @torsten.strauss
Thanks for reporting it!
We've logged it as SP-6795 in our internal bug tracking system. Please keep an eye on the release note!
Thanks.
Hi @tconrad ,
We are not aware of this error caused by SQL Prompt. It may be worth trying the suggestions mentioned here? / comments
Hi @tconrad ,
We are not aware of this error caused by SQL Prompt. It may be worth trying the suggestions mentioned here?
Hi @tonywaddle
Thanks for posting and so sorry to hear you are having this issue.
If not already, can you please upgrade to the latest version (6.0.8.7147 - January 23rd 2018) and test again?
If problem persists, would you be able to share the script for FUNCTION dbo.fn_SpidFilter so I can try a full reproduction? It's worth trying unlink and relink firstly though. / comments
Hi @tonywaddle
Thanks for posting and so sorry to hear you are having this issue.
If not already, can you please upgrade to the latest version (6.0.8.7147 - January 23rd 2018) and test again?
If pr...
Hi @kalo
Can you please confirm the full version number of your SQL Source Control? If not already, can you upgrade to the latest version (6.0.7.7122 - January 9th 2018) and test again? / comments
Hi @kalo
Can you please confirm the full version number of your SQL Source Control? If not already, can you upgrade to the latest version (6.0.7.7122 - January 9th 2018) and test again?
Can you please turn on Frequent update (Help- Configure Frequent Updates) and try again? / comments
Can you please turn on Frequent update (Help- Configure Frequent Updates) and try again?