Do you want to check which folders are taking up too much space? Do you want to check if there are temporary tables? If yes, then the batch task AHISTO might be your best bet to purge off old data. Check if table sizes are too big and compress them such as STOJOUVAL. Old and unnecessary data in temporary tables, find out and take action.
Submit a task to purge temporary tables
Why compress data?
- Compressing data can reduce the on-disk storage requirements by 50 to 75%; for a large table that might equate to many gigabytes of regained space on your precious SAN or local SSD storage.
- Reduced memory consumption. To read compressed data, SQL Server uncompresses it on-the-fly. This means you might be able to reduce the amount of memory used by SQL Server and get higher utilization if your environment is virtualized. Higher utilization equals lower costs. Sounds like a win to me.
- Increase in Page Life Expectancy (PLE) is how long the average data page will remain in memory. Higher PLE means higher performance, up to a point. If you have a server with 100 second PLE, and compressing data bumps PLE up to 1000, that’s a major win.
- Reduced I/O congestion. Since compressed data occupies less space, reading a compressed table from disk into memory requires less I/O bandwidth than reading an uncompressed table into memory.
- Increased CPU utilization. Assuming you’re on a paid edition of SQL Server, you’re paying for CPU, you may as well use it. Compression does increase CPU utilization, so you’ll probably not want to compress tables on a system that is already CPU bound. Aside from that, you’re golden if you’ve got spare CPU capacity. May as well use it to your advantage!
Check and compress large tables:
How to compress a table in Sage X3
- Open function GESATB, select STOJOUVAL for example.
- Select the index tab configuration file section
$MSSQL_STOJOUVAL
{“WITH (DATA_COMPRESSION=ROW)”}
End - Save and do a forced validation
- Forced validation process will take time and must be done out of business hours in a dedicated maintenance window. Make sure there is enough disk space on the SQL log file.
