Usage Based Optimisation: Zero Value in Estimated Count

Today I needed to update our cube aggregation designs using the Usage-Based Optimisation Wizard but I got stuck on an error I;d not seen before

“Estimated Count or Partition Count must be specified for cube objects that require counting.”

Ok, not too helpful. I highlighted each dimension and clicked the “count” button for each one, but it still did not fix. I then looked a little closer and noticed that one of the dimensions had a red squiggle underneath it. I expanded the list and noticed that several of the attributes counts also had red squiggles underneath them, and that the counts were 0. I updated the counts to 1 and sure enough the squiggles disappeared. It’s probably not a good idea to update each one to 1 but rather to the correct or at least the anticipated value.



Author: Richie Lee

Full time computer guy, part time runner. Full time Dad, part time blogger. Pokémon Nut. Writer of fractured sentences. Maker of the best damn macaroni cheese you've ever tasted.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s