Modified Database File Connection

[SLLindleyFX2TW]

I have modified the AstorProfiles.mdf database file to add historic AISC steel shapes. I did the modifications using Microsoft SQL Server Management Studio. When I placed the modified file (with the same name) back into the original file location, I got a message that the database could not connect.  I deleted the ldf file, but I still got the same error.  When I place the original file back into the original file location, it works.  How do I get the modified file to work?

[cristian.udreaBYPDW]

Hi @SLLindleyFX2TW,

Replacing a MDF file within Steel Content with a modified file having the same name is a scenario that normally works and is well supported for Advance Steel.

• First please make sure to edit the database with the apropriate version of SQL Server for compatibility:
  AS 2022 and 2023 use SQL Server 2014 (version 12.0.6024.0)
  AS 2024 and 2025 use SQL Server 2019 (version 15.0.4153.1)
  Avoid upgrading AS 2022 and 2023 databases to a later SQL Server version as this is not reversible.
  
  
• Then, please make sure the MDB file wasn't corrupted. Always remember to disconnect and remove all pending connections to a database file after you're done editing it inside Microsoft SQL Server Management Studio, before closing the Studio environment.
  
  
• Ensure that the instance of SQLLocalDB is stopped before replacing the MDF file, this can be done using the sqllocaldb command line utility.

sqllocaldb i AdvanceSteel[YEAR]   // Example: sqllocaldb i AdvanceSteel2024

•  If it shows up as running, make sure to close all instances of Advance Steel you are working on, then stop it using this command

sqllocaldb stop AdvanceSteel[YEAR]   // Example: sqllocaldb stop AdvanceSteel2024

Another note, the LDF file must be deleted before starting Advance Steel. Replacing the MDB and letting the old LDF file remain on disk has the potential to create inconsistencies in or even corrupt the data contained in the MDF file.

If you're still encountering issues, please attach a sample of a changed MDF file that results in the error.

[SLLindleyFX2TW]

Downloading SQL management studio 2014 and SQLExpress 2014 did the trick.  Advance Steel now recognizes the database file (AstorProfiles.mdf) and the management tools can open the new tables.

[SLLindleyFX2TW]

My next question is how to get the added tables in the database file to show up on the pull down menus for that type of information.  For this case, the AstorProfiles.mdf database was expanded to include AISC Historic Shapes (addition of 7 tables to the AstorProfiles.mdf database.  I have also added the new records in the ProfileMasterTable to point to the added tables, but the tables are not accessible in the pull down menu for specific steel shapes (I-sections).  How do I get the Advance Steel Beam Dialogue box Section tab to show the new database sections in the pull-down menu under "I Sections"?

[cristian.udreaBYPDW]

Hi @SLLindleyFX2TW,

There are 4 requirements to able to add the new profile to the Database apart from the dimensional data.

1. Define the Table in the database which will have the dimensional data.
2. Define the Section Type - ProfileTypeClassDefinition Table
3. If you want to link your new types together, instead of having them spread in the "All" menu, define the Subtype - ProfileSubtypes Table
4. Add a record to the ProfileMaster Table to link all the above 3 together.

This article is a bit older, as Advance Steel no longer uses Microsoft Access, however the rest of the information inside (table names, field names) still applies:
Advance Steel - Add a new Profile type to AstorProfile (System Database for Steel shapes) (autodesk....

There is also a video guide that covers this process:
12. Adding a new section catalogue in AstorProfiles.MDF database (youtube.com)

[SLLindleyFX2TW]

After some of the other posts regarding the database, I found that the database file (.mdf) had to be modified in SQL Server Express 2014 to be able to be seen. I also found that the ProfileMasterTable had to be modified to add the new profile tables to add them to the drop-down menus. Lastly, the ProfileTypeClassDefinition table had to be modified to add the TypeName prefix for any of the new profile records that were added. For example, adding a CB historic beam required that table to have the CB in TypeName and the profile type "I" in TypeClass. When adding large tables to the database, it is much easier to do that in SQL Server Express.

[SLLindleyFX2TW]

I have gotten the database tables added (for all of the historic AISC wide flange and tee shapes), and have also added them to the preferred tables list so that they appear on the initial drop-down menu for input (along with the AISC 15 W Shapes, etc.).  I have been translating through CIS/2 import/export to an analysis program, and the mapping files are complete.  When I export from Advance Steel through the export CIS/2 option, I am able to read the entire structure and the members from the new tables are exported seamlessly into the analysis program.  However, when I translate from the analysis program through the CIS/2 translator, and then import the CIS/2 file, the members that are part of the new tables do not translate.  It does give the capability to look up each of the items and select it from the new tables, but it does not translate the shape directly into the model.  I set up each of the tables with the primary key on the SectionName, which is the same key for all of the current AISC shapes.  I can't seem to find the "trigger" that allows the CIS/2 imported section to be found in my new tables.  My only other thought is that the OwnerText would have to match "DSC" for the tables to read.  I used my own initials for the 16 tables that I added.  Any thoughts?