SQL Database Too Large?

[Manu_Narayan]

I've been killing myself trying to figure out why no jobs have been running.  They show in the job monitor "ready" (not ready, no idle devices found) but haven't been running.  I assumed communication error to the device and went through some server restarts, device resets, changing SCSI IDs.  I then checked my event viewer (what I should have done at first!) and saw I had 3 errors, all relating to 'available space.'  The issue isn't disk space as I have about 10GB free on the partition that BUE is installed on, however it seems that I may have hit the limit of SQL Express databases?

I installed the SQL Express Management Studio in hopes that I could do a shrink operation on the DB, but unfortunately it appears that there's no white space in the DB.  What can I do to shrink this database?  (i had been wanting to look into that anyways since it had been so large.  The DB + bak take up 1/3 of my disk space on my C partition!) 

Does anyone ahve any suggestions?  What gets stored in this DB other than my configuration values?  What can I truncate?

Thanks!

Manu

Event Type: Error
Event Source: MSSQL$BKUPEXEC
Event Category: (2)
Event ID: 1827
Date:  11/7/2008
Time:  12:42:18 AM
User:  CIMGROUP\manu
Computer: 
Description:
CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 23 07 00 00 10 00 00 00   #.......
0008: 0d 00 00 00 44 00 43 00   ....D.C.
0010: 31 00 5c 00 42 00 4b 00   1.\.B.K.
0018: 55 00 50 00 45 00 58 00   U.P.E.X.
0020: 45 00 43 00 00 00 05 00   E.C.....
0028: 00 00 42 00 45 00 44 00   ..B.E.D.
0030: 42 00 00 00               B...   

Event Type: Error
Event Source: MSSQL$BKUPEXEC
Event Category: (2)
Event ID: 1105
Date:  11/7/2008
Time:  12:30:49 AM
User:  CIMGROUP\veritas
Computer: DC1
Description:
Could not allocate space for object 'DBO.JobHistorySummary'.'cidx_jhs_originalstarttime' in database 'BEDB' 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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 51 04 00 00 11 00 00 00   Q.......
0008: 0d 00 00 00 44 00 43 00   ....D.C.
0010: 31 00 5c 00 42 00 4b 00   1.\.B.K.
0018: 55 00 50 00 45 00 58 00   U.P.E.X.
0020: 45 00 43 00 00 00 05 00   E.C.....
0028: 00 00 42 00 45 00 44 00   ..B.E.D.
0030: 42 00 00 00               B...   

[Manu_Narayan]

So, it appears my issue is the size of my Job History.  I probably had history that went back a year and a half.  In the BEDB my JobHistoryDetailInfo table was 2.8GB.  I am going to remove 1/4 or 1/2 of the job history and see if I can then do a shrink on the DB. 

Will update everyone with results.

[milad]

check this url:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008022616103648

[teiva-boy]

 You should point to a full SQL installation, and migrate the database over.

[Colin_Weaver]

Usually the BE database in SQL Express does not run into this issue - unless you have something like CASO or SSO installed in which case installing to a Full SQL instance is a good idea.

A few things to stop the BEDB increasing in size:

Make sure database maintenance is enabled and that your "Delete Aged Data" settings are approproriate in BE. 
Tools --> Options --> Settings --> Database Maintenance

Make sure the database maintenace does actually run - if it is failing this needs troubleshooting.

Also I believe Symantec Support do have a document detailing some SQL commands to run, if you are already running into problems because of the database size exceeding 4GB. - The document itself is probably not public because it discusses manual modifications within the database that should probably be done under Symantec supervision.