04-07-2014 05:19 AM - edited 03-18-2019 02:50 AM
Hi All;
We use TMS 13.1.2v. 255 GB Hard Disc capacitiy on the Win2008 server . I see below disk space errors about the TMS. Our HDD space is full. How to delete the old log file. How to fix problem. I couldn't delete old log file. I took the backup of the system log files.
An error has occurred while getting disk space information from the database. This may be caused by the fact that under SQL Server default settings, OLE Automation procedures are not enabled. Please refer to help for information on how to enable this option. |
Drive | Total Disk Space | Free Disk Space | Percent Free | |
---|---|---|---|---|
C | 262040 MB | 29 MB | 0% |
Database Name | Database Server | Database File Name and Path | Size | Max Size | Growth | Usage |
---|---|---|---|---|---|---|
tmsng | (local) | C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\tmsng.mdf | 1044 MB | Unlimited | 1 MB | data only |
tmsng_log | (local) | C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\tmsng_log.LDF | 218848 MB | 2097152 MB | 10% | log only |
Table | Number of Entries in Database | Number of Days To Keep Data | Enabled | |||
---|---|---|---|---|---|---|
Endpoint/MCU Call Log | 16387 | 90 | Edit | |||
Gateway/GateKeeper Call Log | 16321 | 90 | Edit | |||
Trap Log | 16327 | 5 | Edit | |||
Scheduled Conference Cache | 0 | 1 | Edit | |||
LiveSnapshot | 0 | 1 | Edit | |||
Audit Log | 0 | 180 | Edit | |||
Packet Loss Log | 0 | 90 | Edit | |||
Scheduler Events | 28 | 30 | Edit | |||
Scheduled Calls | 18420 | 90 | Edit | |||
Ticket Log | 10288 | 60 | Edit |
04-08-2014 08:58 AM
The "An error has occurred while getting disk space information from the database. This may be caused by the fact that under SQL Server default settings, OLE Automation procedures are not enabled. Please refer to help for information on how to enable this option."
Message simply means TMS can not read the diskspace available from the SQL Server. This method is no longer enabled by default on SQL Servers and this message is simply telling you that it can't do it unless you enable the OLE Automation procedures. This in itself isn't a problem, it just means TMS can't report on the database server's diskspace.
Your database files tho show that you have a very big log file. This means your database was probably installed to be in 'full recovery' mode and no one has been managing the log file. When in 'full recovery' mode you can restore to any point in time in the transaction history (cool..) but the transaction log will continually grow unless you manage it (bad..). The alternative is to use 'simple recovery mode', in this mode you can only restore to where you have backups (reasonable..) but the transaction log will stay a reasonable size without upkeep (cool).
In full recovery mode, you can reduce the size of the transaction log by doing a backup, followed by a 'shrink files' operation. Normally if you do regular backups, the transaction log will stay a reasonable size. The filesize itself will not reduce until you do a shrink. think of the filesize as a big box.. the database will fill that box as needed and empty it when you do backups, but if the box will ever become full, that's when it auto-expands. It never auto-shrinks the box.. so once it grows, it stays big. Shrink operations is how you reduce the size of the box.
This page tells you how to view/change recovery modes - http://msdn.microsoft.com/en-us/library/ms189272.aspx
I would recommend changing to simple recovery model, then doing a shrink operation on your database log file. See http://msdn.microsoft.com/en-us/library/ms190757(v=sql.120).aspx for more help on shrinking.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide