Repository Size

[DerekPenning]

Dear Members, does anyone know the average size (MB/GB) of a 30 user repository database?

We are setting one up and want to cater for some growth over the coming years.

Kind regards

Derek Penning

[qwerty]

It does not depend on the number of users but the number of elements.

q.

[Helmut Ortmann]

Hi,

as qwerty said: It depends of what you are doing.

To give you a ballpark figure. We usually start with repository size of 100MB with SQL Server.

Usually size isn't a problem. More important is that you choose the right database on a server. 30 people and eg *.eap file would not look good.

Helmut

[DerekPenning]

Thanks Helmut, we will be using a repository based solution so the user access on a multi user repository should be ok?

Anyway sounds like less than a GB should be ok?

Thanks

Derek

[qwerty]

Again, it depends on the number of elements you're going to model. Only if that is known, you will know the DB size. Nevertheless, a size of 100MB (plus/minus) for a medium project is what one could expect.

q.

[Sunshine]

The old question of how long is a piece of string aye?
Over the last 10 years or so with various organisations I've notice about 100Mb per user on average per year in teams where people use it everyday. But as previously mentioned it really depends on the number of elements. It also depends on embedded documents as well. These can really bloat out the DB. Some people put more in the repository than others.

Remember an EAP file is really an MS access database so you'd be pushing the limits. You probably want to use something better like SQL Server as the repository.

If you use a cloud based DB like SQL Server in Azure then you can start of with 1GB and adjust according to usage.