Atlassian Stash for PLSQL (40.000+ objects)

[Ersin İnce]

Hi, 

We want to use git for SCM of our database codes. However, our whole database objects count is around 40000 objects.

Do we need to create a Stash repository for each object? (I think so, since every object can be versioned separately)

How Stash will perform with more than 40.000 repositories performance-wise?

[Roger Barnes]

Hi Ersin,

I'd suggest you group your PLSQL objects in some way. Managing 40,000 repositories doesn't sound at all appealing, irrespective of the performance impact.

The most extreme, but probably viable, case would be to put everything into one repository, just as you would any other coherent set of files. You can change, commit and track changes to each object (or sets of them) using git.

The Stash codebase, as a comparison I have to hand, tracks over 8,000 files and it's by no means the largest repository around.

[Timothy]

I assume that you are talking about 40 thousand repositories. You'd probably be looking at Enterprise grade Stash Data Center to handle that many repositories.