New answers tagged filegroups
Maybe you have forgotten that a file can have 100% free space? In that case you need DECIMAL(5,2), not DECIMAL(4,2).
Database schema for all objects is stored in the PRIMARY filegroup although user data may optionally be stored in a different filegroup. A piecemeal of individual filegroups is not intended to be used to create a new database, but rather to restore critical data before less frequently used data. That technique allows a database to be partial available for ...
All of them had at least one file with auto-growth enabled and disks hosting them had enough free space available. So then why my index maintenance failed? As it says in the product documentation Reorganize and Rebuild Indexes: (emphasis added) The ALTER INDEX REORGANIZE statement requires the data file containing the index to have space ...
The rebuild isn't necessarily going to move your index to a new file, it essentially drops and recreates the index, and it will be spread across the files in the file group per the Proportional fill round robin algorithm If one of the files needs to grow, it can do that. If you want to do the REORG, manually grow the file that is low on space and do the ...
I found this script which lists LOB objects in each filegroup. Based on the results I was able to find the table still using the SECONDARY filegroup. SELECT au.*, ds.name AS [data_space_name], ds.type AS [data_space_type], p.rows, o.name AS [object_name] FROM sys.allocation_units au INNER JOIN sys.data_spaces ds ON ...
I was able to drop the filegroups after dropping partition schema and then dropping partition function. DROP PARTITION SCHEME <<PartitionSchemeName>>; DROP PARTITION FUNCTION <<PartitoinFunctionName>>; ALTER DATABASE DBNAME REMOVE FILEGROUP PartitionFG
Top 50 recent answers are included