As for multiple contrary opinions, welcome to the internet :-D. Guess you'll have to research and see who's opinion you would trust.
over the last few years, you provided many good advises, so I have no reason to doubt you 😉
there are other reasons one might spilt
I am aware of the other reasons
There's also no performance degradation for large files. If you're taking about files on the same LUN, 1 file of 10 TB is the same as 10 files of 1 TB.
That is the information I was looking for :w00t:
I will stick to the plan and separate the years in different tables and different filegroups. Within the years I have paritions on the date but they will all go into the same filegroup (24 Files/ 1 per LUN).
The Paritioning within the table helps on queries and if I want to delete a whole date I can switch the partitions out of the table.
The different tables leave me the posibility to move older years to other LUNs. On Recovery/Restoring I will have some advantages to as I will not have to restore the whole table with all years if I have a recovery reason.
Constrains and Partitioning will do the magic on eliminating everything that is not relevant for the queries.
Thanks