Hi, We're running Essential Business Server 2008. On the management server that is preconfigured with SCE and SQL Express 2005 I'm experiencing the following issue(s): -Eventviewer says this every minute or so : 1827 - CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database. 1105 - Could not allocate space for object 'dbo.AlertHistory'.'idxc_AlertHistory_TimeAdded_AlertHistoryId' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. -When I run SCE or the EBS console a lot of stuff doesn't work properly or crashes (all related to SQL queries that don't execute properly). With stuff I mean things like monitoring clients, viewing/closing alerts and discovering new devices. It seems kind of obvious that the SQL Express 2005 db has reached the 4 GB limit. But how is this possible ? and how do I fix this ?

Hello,There is a limitation of 4GB for SQL Express 2005. Do you have a large number of management packs, or many language versions of management packs? How many agents have been managed?Please follow the article below to tell us which tables are extremely large so we can move furhther.Determing SQL Server Table Sizehttp://www.mitchelsellers.com/blogs/articletype/articleview/articleid/121/determing-sql-server-table-size.aspxThanks,Yog Li - MSFT

Hi Yog Li, Just to inform you that the problem is now solved. I did a query on the SQL server to determin which database was extremely large and it turned out that OperationsManager > dbo.LocalizedText was the culprit. It contained data with a timestamp of over 9 months old. Apparently this database was never automatically cleaned up (eventhough database grooming is set to 7 days by default in SCE). I've seen other EBS admins with the same issue. I cleaned up the old data using another SQL statement/script and the issue is gone. However I do think this is a bug in EBS 2008 / SCE and I think this needs patching. Thanks !

Hello,Glad to hear the issue resolved. And thanks for sharing the information, which could be very useful for the community members.If you have any further concerns, please do not hesitate to let us know and we are happy to be of further assistance.Thanks,Yog Li - MSFT

Is there any way possible that you can provide the script for this. Thanks,

Eddie, Take a look at the link below for steps : http://blogs.technet.com/essentialbusinessserver/archive/2010/05/03/how-to-maintain-and-reduce-the-amount-of-data-stored-in-the-systems-center-essentials-databases.aspx

Hi, We have had the same problem - however, SQL Studio express has essentially dropped the operations manager db because it exceeded the 4 gig limit, so we cannot load it back in to run any queries/reduce the size. It just tells us it's too big to load back in. Is there a way around this?