Make it faster!!!! Improve Performance!!!
Oog, each commit is like five minutes. Neither standard commits of source code (same SVN server) nor redgate SQL Compare actions (same local database server) take that long!
Keywords: Performance, Speed, Fast
We have been doing a lot of work on SQL Source Control lately. We’ve recently improved performance when you link a database, go to the commit and get latest tabs (especially subsequent visits where we can rely on data being cached), and when selecting/deselecting all on the commit and get latest tabs.
If you are still experiencing performance problems, please make a new suggestion that is very specific to what you would like us to work on. Is it a specific step in the commit process that is taking a long time? Is it viewing history that is taking a long time?
We’ve also started to work on this suggestion, Don’t refresh the commit/get latest automatically, https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/462220-don-t-refresh-the-commit-get-latest-automatically, which will also help with performance.
Contact email@example.com if you can share your database schema with us for performance testing purposes.
If you are experiencing problems with server load, please see http://documentation.red-gate.com/display/SOC33/Changing+or+disabling+the+database+polling+interval. Contact firstname.lastname@example.org if you have any questions about this.
SQL Source Control Product Manager
Pinkesh Jain commented
I have the same problem with a database having 300+ tables and 2200+ procedures.
If you are experiencing performance problems, please comment/vote here. Also, please email SqlSourceControlSupport@red-gate.com with responses to as many of the following questions as possible. This will hopefully give us a better understanding of the problems you are facing so we can address these.
1. How many databases have you linked to source controll?
2. How many objects are in each db linked to source control (# of tables, # of SPs, etc.)?
3. What is the rough specification of your machine where you run SSMS? (OS/SSMS version and service packs, RAM, etc)
4. Is the database server hosted on the same machine as SSMS? If not, what’s the network like between your machine and the DB?
5. How many other people use the DB server?
6. Where is SVN hosted? What’s the network like between your machine and the SVN server?
7. Do you want to source control all the objects in your database?
8. Can you include the SQL Source Control product log in your email?
This can be found at C:\Documents and Settings\<username>\Local Settings\Application Data\Red Gate\Logs\SQL Source Control 0
Please change <username> to your windows login.
8. Do you have SQL Compare? Could you send us a snapshot of your database?
Where exactly are the performance problems? Is the problem that:
- It takes a long time for the commit tab to display the list of changes? If so,
- How long does it take?
- Is it CPU load that’s high, IO, Memory, etc.?
- Load is high all the time SSMS is open. If so,
- Is it CPU load that’s high, IO, Memory, etc.?
- Do you see other SQL processes being killed?
- Which process is the load from (in task manager/perfmon)?
Thanks for your help! This is an early access release and we're hoping to improve performance before the final release.
We have almost 1000 SPs over almost 200 tables and have to keep the database unlinked as the performance impact when checking for modifications etc causes problems when testing.
In my experience 200 to 2000 SPs is typical.
1) We currently don’t have filtering, but you can sort on the column headers. You can then use your mouse to highlight multiple rows and then click on the checkbox. This will check or uncheck all of the objects that are highlighted. I hope this makes your selection a little easier.
To exclude objects, vote/comment at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/458708-exclude-objects-from-versioning
To vote/comment on filtering, see http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/462211-allow-me-to-filter-the-objects-on-the-commit-get-l
2) We are working on CPU performance. There is a workaround. If this is stopping you from evaluating SQL Source Control. Please email SqlSourceControlSupport@red-gate.com for details.
3) Please vote/comment on this at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/462220-don-t-refresh-the-commit-get-latest-automatically
4) We are currently working on performance issues when talking to SVN.
AdminPhil (Admin, Redgate) commented
We're trying to improve our understanding of the sizes of databases that people are using to hone our Performance testing and hopefully give you guys a quicker SQL Source Control experience. Is 5000 SP's a typical number of objects that you place under source control or were you performance testing SQL Source Control? Why do you have 5000 SP's, is this typical?