It's all about the answers!

Ask a question

Very large DB2 database sizes for new empty databases

Sean F (1.3k246158) | asked May 06, 12:43 p.m.

When I setup a typical set of 8 databases on DB2 to support a DOORS deployment they are about 4GB each in size (after running create tables) making a startup database size of about 32GB which is a sizeable chunk of disk for an empty DOORS database array.

The same databases on Derby and also on MS SQL Server are negligible in size by comparison

Does anybody know why DB2 has such large database sizes for empty databases compared to other DB providers?

It makes backup process configuration a bit of an overhead

Are empty new Oracle databases large or small? I have never setup using Oracle.

I see this was asked a while ago but there was no definitive answer.

One answer

permanent link
Ian Barnard (1.9k613) | answered May 08, 3:50 a.m.

Hi Sean

This is a question for DB2 really, because ELM just creates emptyish tables and leaves it entirely to DB2 to manage how that translates into disk utilisation. I imagine they don't take so much space just for the heck of it, there will be a reason such as optimising read activity and updates or something like that.


Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.