TeamCity 8 - Specification for external SQL Server database

We have Team City server with Team City 8.1 installed and are currently using the internal DB option but as recommended we want to move to an external DB.We have the following configuration on the server (everything is on the one virtual server Quad core and 4GBytes, windows server 2008 R2, Intel Xeon CPU E7-4870 @ 2.40GHz 4 Processors)We have 5 active projects with 57 build configurations. Have a maximum of 60 build configurations. So 6 active build agentsWe run all the configs with MSTest/C#We plan to maybe go to maybe 10 build agentsWe are being asked by our DB team what size we need and they want a specific specification for the SQL Server database for this team city database ie number of cores, log space etc etc..Can you give further guidance on what a specification should be roughly so I can guide our DB Ops team internall????I can see this from your documentation....'Allocate sufficient transaction log space. The requirements vary depending on how intensively the server will be used. In the beginning, it's recommended to setup 1Gb for small installations and 2-4Gb for large ones.'
5 comments
Comment actions Permalink

Hi Anthony,

The described configuration is not large, so the database won't be a bottleneck in your case.
Amount of transaction log space depends on number of builds, and especially number of tests. The transaction log space reaches it's maximum when clean-up is performed. We recommend to setup not less then 1Gb.

0
Comment actions Permalink
Thanks for your answer Alina, our number of tests are ~6000 and growing, with 58 build configurations. Each build configuration is approx 11 MBytes in terms of artifacts and current internal DB is approx 438MBytes.Do you think that with this configuration e.g. build configurations, number of agents and SQL Server that this can all reside on our current team city server or should we at least split out the DB to a seperate server?What would be our bottle neck in our case.....even potentially at some point in time ? What do we need to watch for in our case in you opinion?ThanksAnthony
0
Comment actions Permalink

You can have DB and TeamCity server running on one server.
You can find hardware requirements and also some examples based on our experience in this section.
Regarding bottlenecks - please read Slowness, Hangings and Low Performance (refers to large setups), OutOfMemory Problems, "Too many open files" Error. All this problems are not common and probably will never affect you.

0
Comment actions Permalink

One more question from our DB people as follows....

how big is tempdb on the current Teamcity installation?

Where is this defined or how can i determine for our team city installation?

Thanks

0
Comment actions Permalink

There is no tempdb database in HSQLDB. Can you please clariify your question?

0

Please sign in to leave a comment.