# IFC for relational databases - ifcSQL

**URL:** <https://forums.buildingsmart.org/t/ifc-for-relational-databases-ifcsql/1524>\
**Category:** Serializations\
**Created:** [June 20, 2019, 2:09pm UTC](https://forums.buildingsmart.org/t/ifc-for-relational-databases-ifcsql/1524 "2019-06-20T14:09:31Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![bsbock](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.buildingsmart.org/bsbock/32/435_2.png) [@bsbock](https://forums.buildingsmart.org/u/bsbock)\
**Post date:** [June 26, 2019, 6:16pm UTC](https://forums.buildingsmart.org/t/ifc-for-relational-databases-ifcsql/1524/13 "2019-06-26T18:16:19Z")

</div>

> [@ylcnky](#):
>
> Is there a particular reason for why you want to store in a relational database? Have you reviewed NoSQL alternatives?

My reasons are described here:

> [@IFC SQLite Project](https://forums.buildingsmart.org/t/ifc-sqlite-project/1359/2):
>
> ok, let’s start with IFC for relational databases. First of all: why to do this? For me the benefits of sql based working are well known data-access (like XML too), no parser required integrated referencial integrity (not by a seperate test) typesave in base-types multiuser functionality (many users can work on the same datapool at the same time) The points 3) and 4) are - as far as I know - not capabilities of SQLite. But SQLite could be a possible target for IFC-Data. It is not only a S…

But most of all: Leaving the world of a thousand files. Growing up from Luggage to Wardrobe  
as shown in the picture in [IFC for relational databases - ifcSQL](https://forums.buildingsmart.org/t/ifc-for-relational-databases-ifcsql/1524)

---

_[View the full topic](https://forums.buildingsmart.org/t/ifc-for-relational-databases-ifcsql/1524)._