Partitioning of super large tables billions of rows data.Cluster_SqlServer_Database_File_Sighting

DM_111

We have very large (by row count and space used, billions of rows) redgate tables, e.g. [data].[Cluster_SqlServer_Database_File_Sightings] which are impossible to maintain.
Anyone know if these tables can be partitioned?
Additionally, the only way for the partitioning to happen is a migration from source table to the new partitioned table with a different name, then do the sp_rename switch.
Has anyone does something like this?
Is it something that is supported by Redgate?

JoshH

Do you need to maintain a large amount of historical data in your data repository? If not, you can try changing your retention settings to a different length of time to reduce the amount. You can also check to see that Data Compression is enabled. 

DM_111

Thanks For the response.
We need to keep a modest amount of history but the issue is that we have 200 instances and a total of > 8879 databases so we have already optimised our retention period to the minimum we need.
I have had space savings from rebuilding smaller tables as the page fullness was low, but I cannot even begin to think about that on the tables that have multi billions of rows.
And so for maintenance that can aid in managing space, we would like to consider partitioning.

Data compression is currently enabled.