Very Old Segments of a Deleted Table Still Present in Servers
See original GitHub issueI had deleted someTableName
long time back but was surprised to see its segments inside the data directory on servers. One such segment that I see issomeTableName__0__248__20210212T1915Z
, which is almost a year old. We have also configured the retention period to be 1 day, so not really sure why this segment is still hanging around.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Recover deleted table from the database - DBA Stack Exchange
Right click on new restored database and select Task --> Export data; select --Source server and database ---> destination server and database ...
Read more >Database size bigger after delete from table - Stack Overflow
A temporary transaction log is often the reason for a notable increase of size after a huge delete. It will eventually disappear on...
Read more >Data Blocks, Extents, and Segments
All extents allocated to an index segment remain allocated as long as the index exists. When you drop the index or associated table...
Read more >Fastest way to Delete Large Number of Records in SQL Server
Deleting large portions of a table isn't always the only answer. If you are deleting 95% of a table and keeping 5%, it...
Read more >CREATE PROCEDURE (Transact-SQL) - Microsoft Learn
A procedure can reference tables that don't yet exist. At creation time, only syntax checking is performed. The procedure isn't compiled until ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@walterddr This query isn’t working as the table has been deleted. I get a
@walterddr Can you please take a look at this issue? We might need to change the order of segment deletion to ensure the segment from the deep store is deleted before removing the segment metadata, or the segment will become an orphan.