You don't give us much to go on regarding:
- The types of queries during daytime. Analytical queries, that accesses lots of data and does GROUP BY and similar?
- How the modifications are being performed night-time.
Possibly having a clustered columnstore index can be beneficial.
It might help your day time queries due to compression and ability for the execution plans to go batch mode. (Batch mode is a possibility also without columnstore indexes in 2019 with database compatibility level 2019 and Enterprise Edition, however.)
How it will affect your nightly load is difficult to say without any insights. Perhaps a compression delay for the columnstore index can be beneficial if you after the load will modify the rows. (I.e., after the load with compression delay the data will stay row-based for the time period specified. Else, if you do an UPDATE, the before-image compressed row will stay in there, and flagged in a delete bitmap and the after-image will be in the row based delta-store until approx 1 million rows have been inserted/updated and that delta-store is converted to a compressed rowgroup.)
Columnstore indexes - Data loading guidance