Meridian Newsletter Prolog Tip

Product Tip of the Month - Prolog

Identifying SQL and Drive Space Limitations through Prolog Error Messages
By Brad Anger, Meridian Support Analyst

This Prolog Tip will help identify when SQL or drive space limits have been met. Have you ever received a message similar to the following?

Error Message:
Could not allocate space for object "DataGroup" in database ‘Prolog Database' because the "PRIMARY" filegroup is full. # -2147217900

("DataGroup " may be any form in Prolog where you are saving data, and "Prolog Database" would show your own database name, but this issue would have either of two root causes.)

Or

Cause 1:
You are using a limited version of Microsoft SQL, such as MSDE 7, MSDE 2000 or SQL 2005 Express, and have hit the database size limitation for this no-cost version of Microsoft SQL. MSDE 7 and 2000 both have a 2GB size limit, whereas the newer SQL 2005 Express has an increased 4GB size limit. To verify if the database where this message is encountered is at the size limit, go to Prolog Manager Administrator and look at the database size. This size is the combination of the SQL Database and Log files. If using MSDE 7/2000, you can look for a size near 2000MB or 1.9GB where the SQL server will not be able to allocate further space towards the 2GB size limit. If using SQL 2005, this limit will be reached near 4GB in size.

Resolution 1:
There are a number of ways to bypass this limitation if upgrading to the full version of SQL is not possible, such as:

Change the SQL file properties in the Prolog Manager Administrator to reflect either a smaller percentage, or a set MB size.

With or without step 1, you can Compact the database within Prolog Manager Administrator to release any additional unused space.

Split the projects in your database into separate Prolog Portfolio Database(s) by:

a. Archiving one or more projects using Archive to Access within Prolog Manager Administrator. Create a new, blank database, and then use the Import functionality within Prolog Manager Administrator. Once the project(s) are verified in the new database using Prolog Manager, they can be deleted from the original database.

b. Archiving one or more projects directly to a separate database within Prolog Manager Administrator using Archive To SQL (Prolog 2008 and newer only. Any projects added after initial creation would need to use Archive to Access to create a .PMB file, then Import). Once the project(s) are verified in the new database using Prolog Manager, they can be deleted from the original database.

c. Archive one or more completed project(s) to Access, then backup/store the archived projects for safe-keeping, then delete the project(s) from Prolog Manager. NOTE: The Archive (.PMB file) would remain at the Prolog version that it was archived at. This Project Archive file would need to be imported into a compatible version of Prolog in order to be upgraded to a later version.

Cause 2:
Whether using MSDE/SQL Express, or an edition of Microsoft SQL that does not have a limitation on the SQL database size, the storage drive(s) that the database(s) are stored on may be filled to capacity.

Resolution 2:
Meridian Systems cannot make specific recommendations on how to configure your storage medium. If this physical HDD (or SSD if you are fortunate) is at capacity, you will need to reconfigure either the data on the drive, or the physical drive itself. Common sense possibilities for increasing available storage space include, but are not limited to:

Delete unneeded or temporary files on the drive or partition.

Move non-SQL files to another drive or partition.

Reduce File size properties or Compact the Prolog Portfolio Database(s) as referenced in Resolution 1, steps 1 and 2.

Move SQL database(s) to a dedicated or larger drive/partition.

Consult your server administrator, or your server documentation for assistance in re-claiming available space for Prolog Manager Database usage.