This content has been marked as final. Show 4 replies
this is for 3.6.1 but is generally applicableand may be of some help:
Identifying why the ePO database is very large - KB52452
Thanks tonyb99, but that KB article and the linked articles doesn't seem to address the "EPOProductSettings" table.
I was able to determine that the indexes were taking up the majority of the space, so I did the following:
1) Stop EPO services
2) Rebuild Indexes on EPOProductSettings table
3) dbcc shrinkdatabase
4) Start EPO services
That brought the DB size from 79GB to just under 80MB!
That was on Wednesday. Today is Monday, and the DB is back up to 72GB! And the SQL data drive is only 100GB :(
So now I'm wondering what's going on with those indexes that's causing them to grow so rapidly.
Can I disable the indexes on that table without totally breaking EPO? I imagine not, because they're probably there for a reason, but I thought I'd ask anyway in case someone knows.
Im am having a similar issue:
Event ID: 1105
Could not allocate space for object 'dbo.EPOProductSettings'.'IX_EPOProductSettings_SettingName' in database 'ePO4_xxxxxxxxxxxx' 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.
Event ID: 1827
CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.
What was the syntax used to rebuild indexes on EPOProductSettings table?
syntax for the dbcc shrinkdatabasecommand?