Activity overview
Latest activity by mioconnor
Thanks for the reply James.
We are using 3.0.11.
Cheers,
Mike / comments
Thanks for the reply James.
We are using 3.0.11.
Cheers,
Mike
The database is not local but the repository is. Times seem to be a lot longer when more than one person does the refresh. If there are no changes to commit, it will refresh in about 4 seconds - no problem here. But if more than one person refreshes it will rise to 30s or more. However, if there are objects to commit this will hit minutes. It seems the more changes the longer it takes and the more people that try to refresh the longer.
One easy win you could do, is not keep refreshing the tab when ever you click on commit tab. Numerous times I have been frustrated as I move from the tab to another tab to check something only to move back and it refreshes again. Let the user do the refresh manually. This would lower the conflicts.
Regarding the data rows, when do you think you will have a release for this improvement? I understand that 27000 is lot, but it would be amazing if you could increase the timeout maybe with a warning or something. To literally break it with a .net timeout is not great and makes it impossible to use. Increase the timeout and at least we can work with it in the background...
Thoughts? / comments
The database is not local but the repository is. Times seem to be a lot longer when more than one person does the refresh. If there are no changes to commit, it will refresh in about 4 seconds - no...
General performance
Hi,
We have SQL Source Control applied to a fairly large database 200 procs, 100 tables etc.
I have 6 developers working on a central copy, but the performance is extremely slow when committing cha...