No, you won't. AMD_STORAGE_PERIOD is the property to change in this scenario. AMD_DAILY_TRENDS_LEN is for determining how long daily trends are stored (those with one day resolution).
However, please rethink the idea of extending the storage period. It will cause database grow (maybe even 10 times) and what is more important such report would be extremely slow as we do not have hourly aggregates and it would require to fetch raw data meaning NAM would have to go thru all the data in the database. Probably it will not be usable at all.
Although in theory you could keep raw data measurements for up to 90 days, I believe that calculating 1 hour aggregates would seriously affect performance of your reporting server. Not to mention disk space required to handle that.
One way do what you are looking for is to export hourly stats to external engine like Splunk or Elastic. Though our partner export API used for such integration was not meant for resolutions other than 1 monitoring interval, I checked that we could help you to give you hourly aggregates. Please let me know if that would be something that could work for you.
Thanks for the follow up. As the solution is sold to customer without additional tools, so we won't be that keen to look into using elastic search or splunk due to cost reason and effort.
You mention that it is possible to have hourly aggregate ? I like to hear more. Currently, this deployment is using DCRUM 2017 SP5.
What I meant was that you can extend storage period up to 90 days - and then you will be able request reports with 1h resolution, however, the results will be generated out of the single monitoring interval measurements, which will cause the report to be slower and in case you use a farm - might cause problems with limits of maximum data allowed to be transferred between (CAS) Server nodes.
Btw Elastic is a free software.