New in the Community? Get started here

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Knowledge Base
Showing results for 
Search instead for 
Did you mean: 

- Who are the top users of September? Discover them here!

- Check out the ESS Active Energy Management Blog now! 

- Join us on October 23rd for a live Panel session to discuss The Power of a Sustainable Ecosystem with Hervé Coureil, Chief Digital Officer of Schneider Electric and other great speakers. Register here!

Continuum Database .MDF file is growing rapidly due to the file’s Autogrowth setting


Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance.


The Continuum database mdf file’s autogrowth setting is set to 12800 % causing the file to grow quickly. 

AutoGrowset too high.JPG 

When attempting to change the value in SQL Server Management Studio (SSMS) you receive the error below and the value cannot be changed.

Autogrowth error.JPG

Product Line

Andover Continuum.


  • Continuum Cyberstation
  • Microsoft SQL Server 2005 sp1


There is a known bug within SQL Server 2005 sp1 which causes the autogrowth setting for a database file to be set to 12800% with no user interaction.


Since you cannot use the dropdown box to change the autogrowth function you will need to open a new query and execute the following two sql statements:

Alter Database ContinuumDB

Modify File (Name=’ContinuumDev’,Filegrowth = 10MB)

It may be necessary to change the Name of the database file that is being modified.  The autogrowth setting of 10 MB is the default for Continuum.

Note: Upgrading to SQL Server Service Pack2 or high should also resolve the issue.  Care should be taken to follow the Compatibility Matrix Update - Andover Continuum PA-00503  and Compatibility Matrix Update - Andover Continuum PA-00369   for service pack compatibility.

Tags (1)
Labels (1)
No ratings