Comments
2 comments
-
Hi Torsten
Thanks for reporting this. We've reproduced the issue here. We'll let you know when we release a fix.
Cheers
Harry -
Hi Torsten
We believe we've fixed this issue in the latest release (7.3.598). Please give it a try and let us know if you have any more problems.
Also:torsten.strauss wrote:BTW It would be helpful to allow to copy the version number from the about SQL Prompt window!
Cheers
Harry
Add comment
Please sign in to leave a comment.
Version 7.3.0.587
BTW It would be helpful to allow to copy the version number from the about SQL Prompt window!
--one in_row_data allocation unit and one additional row_overflow_page
SELECT
OBJECT_NAME(object_id) AS name
, partition_id
, partition_number
, rows
, allocation_unit_id
, type_desc AS page_type_desc
, total_pages AS pages
, used_pages
, data_pages
FROM sys.partitions p
JOIN
sys.allocation_units a
ON
p.partition_id = a.container_id
WHERE object_id = OBJECT_ID('dbo.BigTable');
GO
leads to
--one in_row_data allocation unit and one additional row_overflow_page
SELECT
OBJECT_NAME(object_id) AS name
, partition_id
, partition_number
, rows
, allocation_unit_id
, type_desc AS page_type_desc
, total_pages AS pages
, used_pages
, data_pages
FROM
sys.partitions p
JOIN
sys.allocation_units a
ON
--tab between p and the column name
p .partition_id = a.container_id
WHERE object_id = OBJECT_ID('dbo.BigTable');
GO