Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is the output for Database Sizes and Transaction Logs sizes different from Sybase stored procedures like sp_helpdb and sp_spaceused?

0
Posted

Why is the output for Database Sizes and Transaction Logs sizes different from Sybase stored procedures like sp_helpdb and sp_spaceused?

0

In these two tables, the space for data and logs is separated as much as possible to allow a clearer picture of your database. For the Sybase stored procedure sp_spaceused, the ‘database_size’ field is the sum of all devices allocated for the database, and the ‘data’ field is the sum of the sizes of all data objects in the database, including transaction logs. For the stored procedure sp_helpdb, the ‘size’ field is the size of each device allocated for the database, and the ‘free kbytes’ field is the amount of space left unreserved on that device. In the PrimeAlert for Sybase module, the ‘Total’ field in the Database Sizes table is the sum of all devices specifically allocated for data (devices that sp_helpdb would report as being ‘data only’ and ‘data and log’). The ‘Total’ field in the Transaction Logs table is the sum of all devices allocated for logs (devices that sp_helpdb would report as being ‘log only’ or ‘data and log’. The procedure sp_spaceused reports the sum of sizes of al

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123