Comments
Sort by recent activity
Thanks for your post.
I think that you're most likely seeing this problem as 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:
- to display the 'blue blob' next to an altered object
- to display the name of the user who made the change, if you're working in shared mode.
It sounds like in your case you've either got a fair few users on a single instance, or maybe several databases that are source controlled. Unfortunately, once a user clicks on a linked DB, the poller will continue to run for that DB until SSMS is closed.
We are looking to improve the performance of the polling query (and I'll alert the development team to this post) but in the meantime, things you can try are: 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. Logging changes to a dedicated database - this won't stop the problem altogether, but will reduce the impact on tempdb. / comments
Thanks for your post.
I think that you're most likely seeing this problem as a result of our polling query, which regularly runs for each user to look for changes to your database objects. This run...
Hi, thanks for your post.
For the second part of your query, the commit as far as SVN is concerned will always be listed against whoever actually ran the commit operation. The person that changed the object in the database is irrelevant.
Some things to check for the 'changed by' showing unknown:
- ensure the other user has made the config file change to point to the changelog DB you set up, the same as you did.
- when they change an object, wait a minute or so before refreshing your commit tab (the polling query to track changes runs at intervals, you may have refreshed and seen unknown as the query hadn't run for the other user yet)
- ensure the change is one that we are able to track. The last part of the article you probably saw earlier lists some of these (see here) - that doesn't sound like the problem in this case though. / comments
Hi, thanks for your post.
For the second part of your query, the commit as far as SVN is concerned will always be listed against whoever actually ran the commit operation. The person that changed t...
Yep, that'll do it too.
To stop it using tempdb, you can force it to use a database you create specifically for the purpose: http://documentation.red-gate.com/display/SOC3/Logging+changes+to+shared+databases# / comments
Yep, that'll do it too.
To stop it using tempdb, you can force it to use a database you create specifically for the purpose: http://documentation.red-gate.com/display/SOC3/Logging+changes+to+shared...
Hi,
Sorry to hear you're running into this. If it's suddenly started happening then it's possible that one user has a stuck lock on our change-tracking table. The quickest way to fix that is to usually get everyone to restart SSMS, although in some rare cases it seems to require the SQL instance to be restarted instead.
If you've actually been experiencing the problem more and more frequently over time, it may indicate a different issue happening though, so let us know if that's the case. / comments
Hi,
Sorry to hear you're running into this. If it's suddenly started happening then it's possible that one user has a stuck lock on our change-tracking table. The quickest way to fix that is to usu...
Hi Stephen,
This isn't one we've been asked about before I'm afraid, so it sounds like one for Uservoice... / comments
Hi Stephen,
This isn't one we've been asked about before I'm afraid, so it sounds like one for Uservoice...
Unfortunately not, the commit/get tabs will only show objects relevant to the database currently selected in the Object Explorer. / comments
Unfortunately not, the commit/get tabs will only show objects relevant to the database currently selected in the Object Explorer.
I don't have a MySQL instance handy to test with I'm afraid, but what's the comparison key set up as? I see that some of the columns listed in your "last 5 rows" have similar values.
I'm not familiar with the MySQL version of the tool, but our SQL Server data compare does need to uniquely identify the rows in each table via some sort of PK / Unique Index- perhaps whatever is being picked up as the comparison key in your case is not returning unique values? / comments
I don't have a MySQL instance handy to test with I'm afraid, but what's the comparison key set up as? I see that some of the columns listed in your "last 5 rows" have similar values.
I'm not famili...
We don't currently support 7.1 I'm afraid. We're aiming to add this, but I don't have a precise date. It's likely to be once we've completed TFS 2013 support.
If you need to upgrade Vault right now, then an alternative would be to link SQL Source Control using the Working Folder option, and then use the Vault client tools to perform the commits etc. / comments
We don't currently support 7.1 I'm afraid. We're aiming to add this, but I don't have a precise date. It's likely to be once we've completed TFS 2013 support.
If you need to upgrade Vault right now...
Thanks for the feedback on the merge feature- I've alerted the development team so they can consider this. / comments
Thanks for the feedback on the merge feature- I've alerted the development team so they can consider this.
Ah, makes more sense, I think in my quick test the subsequent object was indeed a table.
I did definitely observe the missing separator though. I'll let the team have a look over this thread. I think with the way V2 works (albeit my limited knowledge at this point!) it shouldn't be an issue either way, but they can verify that. / comments
Ah, makes more sense, I think in my quick test the subsequent object was indeed a table.
I did definitely observe the missing separator though. I'll let the team have a look over this thread. I thi...