I don't know what you mean with too much diskspace? Perhaps you can post the sizes here and the number of entries in your system so we can evaluate if it's normal or not.
Most of the tables you list should not be touched and if you truncate link and entry you will delete all your assignments and entry data, and you would possibly be looking for a new job the next day.
The log tables should be maintained by the housekeeping as mentioned, but
mc_exec_stat
MC_LOGS
MC_SYSLOG
can be cleaned but neither should have that much data, but large amounts of transactions cause logs to grow. Have you checked that your backup is cleaning the transaction logs? Also reduce loglevels to ERROR to reduce the amount logged here.
MXP_Audit_Variables should not contain audits that are not in the provisioning queue, if you delete those workflows will fail.
MXP_Ext_Audit can probably be cleaned without affecting operations (reports might be affected though) but you'll loose the detailed execution history on the entries, perhaps you can do partials, delete entries older than 3 years or similar.
For future reference:
List transaction log sizes (SQL Server):
DBCC SQLPERF(LOGSPACE)
List table siszes (SQL Server):
DECLARE @SpaceUsed TABLE( TableName VARCHAR(100) ,No_Of_Rows BIGINT ,ReservedSpace VARCHAR(15) ,DataSpace VARCHAR(15) ,Index_Size VARCHAR(15) ,UnUsed_Space VARCHAR(15) ) DECLARE @str VARCHAR(500) SET @str = 'exec sp_spaceused ''?''' INSERT INTO @SpaceUsed EXEC sp_msforeachtable @command1=@str SELECT * FROM @SpaceUsed order by CAST(REPLACE(ReservedSpace,' KB','') as INT) desc
Oracle undo, user and redofiles:
select * from dba_data_files where tablespace_name LIKE 'UNDOTB%1' OR tablespace_name LIKE 'USERS%';
select l.group#,f.member,l.archived,l.bytes/1078576 bytes,l.status,f.type from v$log l, v$logfile f where l.group# = f.group#
-
C
Message was edited by: Per Krabsetsve
