Using the big decimal data type

With the Big Decimal data type, MicroStrategy preserves the precision of attribute ID values and attribute ID forms when displaying IDs and performing operations such as filtering, drilling, and page-by. Data recovery from external hard drive For more information about these operations, see the Basic Reporting Guide.

You can define attributes that are identified by numeric columns in the database. Database join types These numeric columns can have more than 15 digits of precision, such as account numbers and other long integers.


Section 8 database You must use the Big Decimal data type to handle these values, because these data values have higher precision and cannot be stored in normal numeric data types.

If you do not associate high-precision database fields with the Big Decimal data type, you may see numbers truncated starting with the 16th digit. Icd 9 database The WHERE clause in the report SQL statement in drill reports may truncate numbers starting from the 16th digit, and page-by may not return results.

Constant: You can force a constant to be stored as a Big Decimal value by enclosing it in hash marks. Database xampp For example, you can define a filter as “Customer@ID exactly #12345678#”, even though 12345678 does not necessarily require the Big Decimal data type.

Attribute form: If you change the column data type to Big Decimal on the Column Alias tab in the Attribute Editor, you must also select Big Decimal as the form format type in the Form format: Type drop-down menu in the Definition tab.

Attribute ID: Follow the steps in the topic Defining attributes with high-precision ID forms in the MicroStrategy Developer Help (formerly the MicroStrategy Desktop Help).

Precision is lost when any Analytical Engine calculation is performed, the metric is used in a data field in a document, the metric is subtotaled, or metric values are displayed in Graph view.

Numeric formatting strings supported in MicroStrategy can have a different effect when applied to the Big Decimal data type. Database administrator jobs For numeric formatting descriptions and examples when using the Big Decimal data type, see Numeric data formatting.

When qualifying on a Big Decimal metric, you must explicitly identify high-precision constants by enclosing the value within hash (#) symbols. Data recovery joondalup For example, #1234567890123456#.

Note that the Warehouse Catalog does not automatically map DECIMAL(p, s) or NUMERIC(p, s) columns to the Big Decimal MicroStrategy data type even when the precision is greater than 15. Database of genomic variants This is because Big Decimal should only be used when the column is used as an attribute ID form. Database viewer Numeric data formatting

If there are more digits to the right of the decimal point than the placeholders in the format, the decimal portion is rounded to the number of places specified by the placeholders.

If the format contains zeros to the left of the decimal point, numbers less than one are displayed with zeros to the left of the decimal point.

If there are more digits to the right of the decimal point than the placeholders in the format, the decimal portion is rounded to the number of places specified by the placeholders.

If the format contains commas separated by #’s or 0’s, commas separate the thousands. H data recovery registration code free download Note that the actual thousands separator used depends on the session locale.

The following table lists examples of custom numeric formats. Database hardware It includes the formatting symbols, the report data, and how that data is displayed after applying the formatting to a Big Decimal data type.

banner