Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


This article describes the files SAP2000 creates during modeling and analysis, and which files should be saved for archiving.

Input files

The binary input file .SDB file is the main SAP2000 input file. Additional input files may be created, depending on the load cases defined, to store specific information about the model. These separate input files are listed as follows:

  • Response-spectrum, time-history, power-spectral-density, and steady-state functions, defined through Define > Functions, are sometimes stored in separate function input files when the From File function type is selected. Users have the option to convert the data stored in these external input files into user-defined data where function data is stored directly within the binary .SDB file.
  • Construction-scheduler data, created through Bridge > Construction Scheduler, are stored in separate input files with a .BCS extension.

Further, .SBK binary backup files and .S$K text backup files are automatically saved in the model directory. We recommend archiving the .S2K text backup file and the binary .SDB model file.

Analysis files

  • Binary analysis files are created during analysis to store intermediate and final analysis results. When the model is unlocked, these binary intermediate files are deleted, and analysis must be re-run to re-create these files.
  • To archive analysis results, the best approach is to export using Text, Excel, or Access format, the process for which is described in the next section.
  • The analysis log file with the .LOG extension contains useful information associated with completed analysis, such as numerical problems, convergence problems, total analysis time, etc.

Exporting results

  • Archived input files may be run to obtain analysis results.
  • It may also be a good idea to export and archive analysis results using Text, Excel, Access, or another common file format. Results may be exported through File > Export > SAP2000 .mdb, .xls, or .s2k. Some conditions where archiving may be appropriate include:

    • When analysis results take a significant amount of time to generate.

    • When results will be reviewed on a computer without SAP2000.

    • When results are archived for a particular software version. Then results from an upgraded version may be compared with those from the current version.

Summary

Backup should involve all relevant input files, and all exported results which should be easily accessible for convenient review.

See Also

  • [Backups and troubleshooting corrupted models]
  • [File format and settings files]
Unknown macro: {related-incident}
Unknown macro: {related-incident}
  • No labels