Database Sizing
CostOS Database Size Overview
Summary: The total size of a CostOS database is mainly driven by three areas: estimating data, attached BIM/design files, and accumulated action/history logs.
Estimating data: BOQ items and assigned resources.
Design storage: BIM models, drawings, and PDF files stored in SQL Server.
Logs and history: User actions and project changes that grow over time.
Project Estimating Data (BOQ)
The table below shows the approximate database size based on the number of BOQ items per project. Each BOQ item includes one assigned resource.
BOQ Items per Project | Data File | Log File |
|---|---|---|
3,000 items | 32 MB | 16 MB |
10,000 items | 92 MB | 42 MB |
50,000 items | 436 MB | 290 MB |
100,000 items | 858 MB | 290 MB |
BIM and Design File Storage
3D and 2D design files attached to projects are stored directly in the database using SQL Server. These files can significantly increase total database size depending on the complexity and number of models. The table below provides approximate size ranges per file type.
File Type | Typical Size per File |
|---|---|
IFC (3D model) | 10 MB — 500 MB |
Revit RVT (3D model) | 50 MB — 500 MB |
DWFx / DWG / DXF (2D drawing) | 1 MB — 50 MB |
PDF Drawing | 1 MB — 20 MB |
These are indicative ranges. Actual sizes depend on model complexity and the number of elements.
Action Logs and History
CostOS keeps a full log of all user actions, changes and project history. This data grows continuously over time based on the number of active users and the frequency of changes made in the system. For large teams working daily over several years, log data can become a significant portion of the total database size. It is recommended to monitor log growth and archive older logs periodically.