Post reply

understanding behavior [with persist_sample_percent=on] on maintenance process.

  • July 23, 2019 at 7:10 pm

    #3665481

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • July 23, 2019 at 8:25 pm

    #3665506

    You may want to start by checking the persisted_sample_percent in the dmv sys.dm_db_stats_properties to see if the value really was persisted.

    Sue

  • July 25, 2019 at 1:17 pm

    #3666055

    Sue, thanks for your response. Indeed, i checked last_updated,[rows],[rows_sampled], sp.persisted_sample_percent columns by selecting from sys.stats, and using cross apply to sys.dm_db_stats_properties. Because of that, it seems to me that the parameters that i last executed manually are not being persisted. In fact, i just recently run UPDATE STATISTICS WITH SAMPLE 10 ROWS, PERSIST_SAMPLE_PERCENT=ON and i am seeing that rows value is equal to rows_sampled value, and this value is close to total the of rows (67828) from the related table. I was expecting to see rows_sampled=10. The persisted_sample_percent is ~0.014743174 what is ~1000 rows (67828 x 0.0147431739104794). perhaps, i am misunderstanding something? thank you

Viewing 3 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply