Monitor Free Disk Space on Microsoft SQL Server 2000

  • Created:
  • / Author: tombucci
Solution:

Disk space is a critical issue for Sage Pro ERP when using a Microsoft SQL Server (SQL) database. If disk space is not being monitored and the available disk space is low, program issues will arise. The following errors have been reported as a result of low disk space in SQL:

  • Error 1526 the log file or database is full
  • Error SQL database is suspect (PROTEMP)

This article provides recommendations for maintaining free disk space in a SQL database so that Sage Pro can run efficiently.

The following information should be reviewed and discussed with a qualified Microsoft SQL Server Database Administrator (DBA) before implementing:

  • SQL creates transaction log files associated with Sage Pro system and company databases. These files can become very large, based on the volume of activity in Sage Pro or after a conversion. They should be regularly backed up and shrunk to decrease the amount of storage space required.

    Important
    Please refer to Solution 21290 21290  for additional information on shrinking the log file.

    • To view the location of the Transaction Log, open SQL Enterprise Manager.
    • Right-click the appropriate database and click Properties.
    • Click the Transaction Log tab. The path to the log is located in the Location field in the scroll pane.
  • Databases created for Sage Pro use the default settings for unlimited and automatic growth of tables. It is defined at 10%. This may cause issues with disk space for very large tables. Ensure that the database tables are set to grow efficiently and do not increase beyond the capabilities of the system. However, these settings should only be edited by a certified DBA who is able to determine the possible repercussions of such changes for Sage Pro.
    • To view the disk space used by a database, open SQL Enterprise Manager.
    • Right-click the appropriate database and click Properties.
    • Click the General tab, the size is listed in the database information section.
  • When an ungraceful exit from the program occurs, the Sage Pro temporary database (PROTEMP) may be left with temporary tables that would otherwise be removed automatically by Sage Pro during a proper exit sequence. If there are no users logged into Sage Pro, there should not be any user tables in the temporary database. These can be removed if no one is logged in; however, do not remove any system tables from this database or Sage Pro may not function correctly.

Leave A Comment?