Article ID: 122482, created on Jul 26, 2014, last review on Jul 26, 2014

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4

Symptoms

When opening a MS SQL database in CP, following error is shown:

The system was unable to set data size limit for this database.
The system was unable to set transaction log size limit for this 
database.You can try to increase the size limits. If this does not 
resolve the problem, contact your vendor.

Operations with the DB size and transaction log size are not propagated to backend.

Cause

The logical names of the Rows Data and Log were changed on backend.

Resolution

  1. Log into the MS SQL server,
  2. Locate the problematic datbase in MS SQL management studio,
  3. Right-click it, click Properties
  4. Navigate to Files,
  5. Rename logical name field's value to "data1" where the filegroup is PRIMARY
  6. Rename logical name field's value to "log1" where the filegroup is Not Applicable

Search Words

Failed to set size limits The system was unable to set data size limit for this database.

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF