ifcSQL is on github

[bsbock]

Here you find some explanations how the stored procedures [app].[ToIfcStepFromProjectId] or [cp].[ToIfcStep] works:

Store, modify and retrieve ifc-data with ifcSQL

These are the secrets of ToIfcStepFromProjectId: Select the project from the Id-argument of ToIfcStepFromProjectId, so the view of the current project retrieves only the entities of this project Fill the step-header with the informations of the current-project-view [cp].[Project] and print it Iterate via CURSOR over all entities and call a function [ToIfcStepLine] für every entity 3.1 Select the local ifc-id from the current entity for this project 3.2 Select the name of the type of the curr…

Creating a Stepfile with the above mentioned stored procedures use a lot of nestet queries. So the time-costs increase exponential with the model size.
Maybe you can speed it up with temporary tables and other methods. If you set some timestamp-outputs, you will find out where the bottle necks are. The point is, that all this methods ends in a procedural way.
The fast procedural way is used in IFC#. See https://github.com/IfcSharp/IfcSharpApps/tree/master/IfcSql/from_ifcSQL

To the importing speed: The IFC#-Api use a bulk-Insert method, wich is much faster than INSERT-statements.
See CurrentModel.ToSql(…) in https://github.com/IfcSharp/IfcSharpApps/tree/master/IfcSharp/hello_project

If this is not fast enough, you can try to work with temporay tables without restrictions and transfer it on server-side to the ifcSQL-tables in a second step.
Hope this helps.