You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thank you so very much for this wonderful utility. I just want to share my experience.
I downloaded and installed the script in one of our test AWS RDS SQL Server (Microsoft SQL Server 2016 (SP3) (KB5003279) - 13.0.6300.2 (X64) ); and when I ran it, it gives me an error "The SELECT permission was denied on the object 'dm_db_stats_properties_internal"
The user ID I used to execute the stored proc have db_owner role and does not have "deny" role selected.
After some online research and discussion with colleague, I modified the stored proc and replace "dm_db_stats_properties_internal" with "dm_db_stats_properties".
And voila it worked.
maybe this specific version of AWS RDS does not support dm_db_stats_properties_internal? not sure. but thought I would share here, if it might help others or someone can actually shed some light. thanks.
The text was updated successfully, but these errors were encountered:
First of all, thank you so very much for this wonderful utility. I just want to share my experience.
I downloaded and installed the script in one of our test AWS RDS SQL Server (Microsoft SQL Server 2016 (SP3) (KB5003279) - 13.0.6300.2 (X64) ); and when I ran it, it gives me an error "The SELECT permission was denied on the object 'dm_db_stats_properties_internal"
The user ID I used to execute the stored proc have db_owner role and does not have "deny" role selected.
After some online research and discussion with colleague, I modified the stored proc and replace "dm_db_stats_properties_internal" with "dm_db_stats_properties".
And voila it worked.
maybe this specific version of AWS RDS does not support dm_db_stats_properties_internal? not sure. but thought I would share here, if it might help others or someone can actually shed some light. thanks.
The text was updated successfully, but these errors were encountered: