convert XFM to SQL Server 2008 spatial

I would like to know how to convet Bentley Map (dgn) to SQL server 2008 R2 database, is there any batch files are available, please give the guidance.

Parents
  • Sorry for the late reply.  You can move XMF or DGN-RDBMS data to SQL Server Spatial by using FME.  One method is to export the DGN-MSLinks data to ESRI File Geodatabase using Bentley Map SS4 and then translating to SQL Server Spatial.  The other is to go directly from DGN-MSLinks to SQL Server Spatial.  In either case, it's FME that will translate the data to SQL Server Spatial.

    My preference is to use ESRI File Geodatabase since it will populate a new table with the geometry as well as the attributes and minimizes the amount of housekeeping required. 

     

    My limited testing on linear elements shows the following:

     

    ESRI File Geodatabase to SQL Server - Pros:

    Can be used on MicroStation DGN data with MSLinks or XFM features.

    Export multiple features with ease.

    Exporter reads the contents of attached references.

    Exporter uses inferred and native feature names not levels.

    Resulting database tables are named from the feature.

    Resulting database tables only requires primary key to be added – All properties are extracted and populated to the new table(s).

      

    ESRI File Geodatabase to SQL Server – Cons:

    The MSLink is not extracted and pushed to the database.

     

     

    DGN-MSLinks Elements to SQL Server – Pros:

    DGN Elements to SQL Server – Cons:

    Requires the content of the design files to be clean and correct.

    Ideally requires one feature per level.

    Resulting database tables are named for the level, not feature.

    Only the MSLink and geometry are extracted.

    Post-translation housekeeping tasks requires attribute data to be copied from originating tables to new spatial tables.

    Requires DBA knowledge and access.

Reply
  • Sorry for the late reply.  You can move XMF or DGN-RDBMS data to SQL Server Spatial by using FME.  One method is to export the DGN-MSLinks data to ESRI File Geodatabase using Bentley Map SS4 and then translating to SQL Server Spatial.  The other is to go directly from DGN-MSLinks to SQL Server Spatial.  In either case, it's FME that will translate the data to SQL Server Spatial.

    My preference is to use ESRI File Geodatabase since it will populate a new table with the geometry as well as the attributes and minimizes the amount of housekeeping required. 

     

    My limited testing on linear elements shows the following:

     

    ESRI File Geodatabase to SQL Server - Pros:

    Can be used on MicroStation DGN data with MSLinks or XFM features.

    Export multiple features with ease.

    Exporter reads the contents of attached references.

    Exporter uses inferred and native feature names not levels.

    Resulting database tables are named from the feature.

    Resulting database tables only requires primary key to be added – All properties are extracted and populated to the new table(s).

      

    ESRI File Geodatabase to SQL Server – Cons:

    The MSLink is not extracted and pushed to the database.

     

     

    DGN-MSLinks Elements to SQL Server – Pros:

    DGN Elements to SQL Server – Cons:

    Requires the content of the design files to be clean and correct.

    Ideally requires one feature per level.

    Resulting database tables are named for the level, not feature.

    Only the MSLink and geometry are extracted.

    Post-translation housekeeping tasks requires attribute data to be copied from originating tables to new spatial tables.

    Requires DBA knowledge and access.

Children
No Data