After it's finished, instance will go back to previous state. e.g. if instance state is running before resizing, then it will go back to running afterwards.
IntermediateNoRunning, StoppedRebootingThe instance is rebooting.IntermediateNoStarting, Running Cloudera CDH 4.x with Hive 32-bit Cloudera ODBC driver for Apache Hive v2.5 Certified Cloudera CDH 4.x with Impala 1.x 32-bit Cloudera ODBC driver for Apache Impala v 2.5 CertifiedStrategy Function NameImpala 1.xImpala 2.xCoalesceFunction COALESCE(#0, 0)StdevPFunction stddev_pop(#0#< #*#>) BetweenOperator#0 BETWEEN #1 and #2#0 BETWEEN #1 and #2ProductFunction (CASE WHEN SUM(CASE WHEN #0=0 THEN 1 ELSE 0 END) > 0 THEN 0 ELSE POWER(-1,SUM(CASE WHEN #0<0 THEN 1 ELSE 0 END))*EXP(SUM(LN(ABS(CASE WHEN #0<>0 THEN #0 ELSE NULL END)))) END)StdevFunction STDDEV(#0#< #*#>) VarFunction VARIANCE(#0#< #*#>)GeoMeanFunctionEXP(AVG(LN(#0)))EXP(AVG(LN(#0)))NotLikeOperator #0 NOT LIKE '#1' IsNullFunction #0 IS NULLIsNotNullFunction #0 IS NOT NULLNotInOperatornot (#0 in (#1#<, #*#>))#/#0 = #1#<#,#0=#*#>#|#<(#>#0#< and #*#>#<)#>#|not #<(#>#0#< or #*#>#<)#> not (#0 in (#1#<, #*#>))#/#0 = #1#<#,#0=#*#>#|#<(#>#0#< and #*#>#<)#>#|not #<(#>#0#< or #*#>#<)#>GreatestFunctionMAX(#0)MAX(#0)LeastFunctionMIN(#0)MIN(#0)FirstFunctionMIN(#0)MIN(#0)LastFunctionMAX(#0)MAX(#0)IFOperator(Case when #0 then #1 else #2 end)(Case when #0 then #1 else #2 end) VarPFunction VARIANCE_POP(#0#< #*#>)Strategy Function NameImpala 1.xImpala 2.xDaysBetweenFunctionDATEDIFF(#1,#0) DATEDIFF(#1,#0) YearEndDateFunction DATE_SUB(ADD_MONTHS(#0, (13 - MONTH(#0))), DAY(#0)) CurrentDateFunctionTO_DATE(FROM_UNIXTIME(UNIX_TIMESTAMP())) TO_DATE(FROM_UNIXTIME(UNIX_TIMESTAMP())) DayOfMonthFunctionDAYOFMONTH(#0)DAYOFMONTH(#0)DayOfWeekFunction DAYOFWEEK(#0) DayOfYearFunction DAYOFYEAR(#0)WeekFunctionWEEKOFYEAR(#0) WEEKOFYEAR(#0)MonthFunctionMONTH(#0)MONTH(#0)YearFunctionYEAR(#0)YEAR(#0)CurrentDateTimeFunctionFROM_UNIXTIME(UNIX_TIMESTAMP())FROM_UNIXTIME(UNIX_TIMESTAMP())CurrentTimeFunctionFROM_UNIXTIME(UNIX_TIMESTAMP())FROM_UNIXTIME(UNIX_TIMESTAMP())HourFunctionHOUR(#0)HOUR(#0)MinuteFunctionMINUTE(#0)MINUTE(#0)SecondFunctionSECOND(#0)SECOND(#0)MilliSecondFunction EXTRACT(MILLISECOND FROM #0) MonthStartDateFunction DATE_ADD(#0,1-DAYOFMONTH(#0))YearStartDateFunction ADD_MONTHS(date_add(date_sub(#0 ,DAY(#0) ), 1), 1 - Month(#0))AddMonthsFunction ADD_MONTHS(#0, #1)MonthsBetweenFunction (12*(YEAR(#1) - YEAR(#0)) + MONTH(#1) - MONTH(#0) - (CASE WHEN DAY(#0) > DAY(#1) THEN 1 ELSE 0 END))AddDaysFunctionDATE_ADD(#0,#1)DATE_ADD(#0,#1)MonthEndDateFunction DATE_ADD((ADD_MONTHS(#0, 1)), -DAYOFMONTH((ADD_MONTHS(#0, 1))))DateFunctionTO_DATE(#0)TO_DATE(#0)Strategy Function NameImpala 1.xImpala 2.xRunningSumFunction sum(#0) over(#1)RunningAvgFunction avg(#0) over(#1)MovingAvgFunction avg(#0) over(#1)MovingSumFunction sum(#0) over(#1)MovingCountFunction count(#0) over(#1)RunningMaxFunction max(#0) over(#1)RunningMinFunction min(#0) over(#1)RunningCountFunction count(#0) over(#1)FirstInRangeFunction first_value(#0) over(#1)LastInRangeFunction last_value(#0) over(#1)OLAPSumFunction sum(#0#< #*#>) over ([#P] [#O] [#W]) OLAPAvgFunction avg(#0#< #*#>) over ([#P] [#O] [#W])OLAPCountFunction count(#0#< #*#>) over ([#P] [#O] [#W])LagFunction lag(#0#<, #*#>) over ([#P] [#O])LeadFunction lead(#0#<, #*#>) over ([#P] [#O])OLAPRankFunction rank() over ([#P] [#O])Strategy Function NameImpala 1.xImpala 2.xRound2FunctionROUND(#0, #1)ROUND(#0, #1)RankFunction #0#,#<partition by#>#<#, #*#>#|rank () over(#1#2#<, #*#> order by #0)AbsFunctionABS(#0)ABS(#0)AcosFunctionACOS(#0)ACOS(#0)AcoshFunctionLN(#0+SQRT(#0-1)*SQRT(#0+1))LN(#0+SQRT(#0-1)*SQRT(#0+1))AsinFunctionASIN(#0)ASIN(#0)AtanFunctionATAN(#0)ATAN(#0)AtanhFunction((LN(1+#0)-LN(1- #0))/2)((LN(1+#0)-LN(1- #0))/2)CeilingFunctionCEIL(#0)CEIL(#0)CosFunctionCOS(#0)COS(#0)CoshFunction((EXP(#0)-EXP(#0*(-1)))/2) ((EXP(#0)-EXP(#0*(-1)))/2)DegreesFunctionDEGREES(#0)DEGREES(#0)ExpFunctionEXP(#0)EXP(#0)FloorFunctionFLOOR(#0)FLOOR(#0)IntFunction FLOOR(#0)LnFunctionLN(#0)LN(#0)LogFunctionLOG(#1, #0)LOG(#1, #0)Log10FunctionLOG10(#0)LOG10(#0)PowerFunctionPOWER(#0, #1) POWER(#0, #1)QuotientFunctionCAST(#0/#1 AS INT)CAST(#0/#1 AS INT)RadiansFunctionRADIANS(#0)RADIANS(#0)RandbetweenFunction ((#1- #0)*RAND()+#0)RoundFunctionROUND(#0)ROUND(#0)SinFunctionSIN(#0)SIN(#0)SinhFunction((EXP(#0)+EXP(#0*(-1)))/2)((EXP(#0)+EXP(#0*(-1)))/2)SqrtFunctionSQRT(#0)SQRT(#0)TanFunctionTAN(#0)TAN(#0)TanhFunction(-1+(2/(1+EXP(-2*#0))))(-1+(2/(1+EXP(-2*#0))))TruncFunctionCAST(#0 AS INT)CAST(#0 AS INT)AsinhFunctionLN(#0+SQRT(POW(#0, 2)+1))LN(#0+SQRT(POW(#0, 2)+1))ModFunctionSIGN(#0)*PMOD(ABS(#0), #1)SIGN(#0)*PMOD(ABS(#0), #1)Strategy Function NameImpala 1.xImpala 2.xStandardizeFunctioncase when (#2 > 0) then (#0 - #1)/(#2) else NULL endcase when (#2 > 0) then (#0 - #1)/(#2) else NULL end •Make sure your database supports the character set(s) that are required by the various languages you intend to support in your Strategy project. Strategy recommends using a Unicode database to ensure all your languages are supported. For details, see Adding or removing a language in the system. •If you will be supporting double-byte languages (such as Japanese or Korean), make sure that appropriate fonts are available for graph labels, text fields in documents, and so on. Appropriate fonts to support double-byte languages are generally Unicode fonts. An example of an effective Unicode font for double-byte languages is Arial Unicode MS. Most Unicode fonts ensure that all characters can be displayed correctly when a report or document is displayed in a double-byte language. •All SQL-based qualifications contained in a given report should be in a single language. SQL-based qualifications include such things as report filters, metrics, and prompts. •If you have old projects with metadata objects that have been previously translated, it is recommended that you merge your translated strings from your old metadata into the newly upgraded metadata using Strategy Project Merge. For steps, see Translating already translated pre-9.x projects. •It is recommended for Developer internationalization that you use a unified locale. For example, if French is the language selected for the interface, the metadata objects language preference and report data language preference, as well as number and date preferences, should also be in French. •If you are using or plan to use Strategy Intelligent Cubes, and you plan to implement data internationalization, it is recommended that you use a SQL-based DI model. The SQL-based DI model is described in Providing data internationalization. Because a single Intelligent Cube cannot connect to more than one data warehouse, using a connection-based DI model requires a separate Intelligent Cube to be created for each language, which can be resource-intensive. Details on this cost-benefit analysis as well as background information on Intelligent Cubes are in the Strategy In-memory Analytics Guide. | After it's finished, instance will go back to previous state. e.g. if instance state is running before resizing, then it will go back to running afterwards.
IntermediateNoRunning, StoppedRebootingThe instance is rebooting.IntermediateNoStarting, Running Cloudera CDH 4.x with Hive 32-bit Cloudera ODBC driver for Apache Hive v2.5 Certified Cloudera CDH 4.x with Impala 1.x 32-bit Cloudera ODBC driver for Apache Impala v 2.5 CertifiedStrategy Function NameImpala 1.xImpala 2.xCoalesceFunction COALESCE(#0, 0)StdevPFunction stddev_pop(#0#< #*#>) BetweenOperator#0 BETWEEN #1 and #2#0 BETWEEN #1 and #2ProductFunction (CASE WHEN SUM(CASE WHEN #0=0 THEN 1 ELSE 0 END) > 0 THEN 0 ELSE POWER(-1,SUM(CASE WHEN #0<0 THEN 1 ELSE 0 END))*EXP(SUM(LN(ABS(CASE WHEN #0<>0 THEN #0 ELSE NULL END)))) END)StdevFunction STDDEV(#0#< #*#>) VarFunction VARIANCE(#0#< #*#>)GeoMeanFunctionEXP(AVG(LN(#0)))EXP(AVG(LN(#0)))NotLikeOperator #0 NOT LIKE '#1' IsNullFunction #0 IS NULLIsNotNullFunction #0 IS NOT NULLNotInOperatornot (#0 in (#1#<, #*#>))#/#0 = #1#<#,#0=#*#>#|#<(#>#0#< and #*#>#<)#>#|not #<(#>#0#< or #*#>#<)#> not (#0 in (#1#<, #*#>))#/#0 = #1#<#,#0=#*#>#|#<(#>#0#< and #*#>#<)#>#|not #<(#>#0#< or #*#>#<)#>GreatestFunctionMAX(#0)MAX(#0)LeastFunctionMIN(#0)MIN(#0)FirstFunctionMIN(#0)MIN(#0)LastFunctionMAX(#0)MAX(#0)IFOperator(Case when #0 then #1 else #2 end)(Case when #0 then #1 else #2 end) VarPFunction VARIANCE_POP(#0#< #*#>)Strategy Function NameImpala 1.xImpala 2.xDaysBetweenFunctionDATEDIFF(#1,#0) DATEDIFF(#1,#0) YearEndDateFunction DATE_SUB(ADD_MONTHS(#0, (13 - MONTH(#0))), DAY(#0)) CurrentDateFunctionTO_DATE(FROM_UNIXTIME(UNIX_TIMESTAMP())) TO_DATE(FROM_UNIXTIME(UNIX_TIMESTAMP())) DayOfMonthFunctionDAYOFMONTH(#0)DAYOFMONTH(#0)DayOfWeekFunction DAYOFWEEK(#0) DayOfYearFunction DAYOFYEAR(#0)WeekFunctionWEEKOFYEAR(#0) WEEKOFYEAR(#0)MonthFunctionMONTH(#0)MONTH(#0)YearFunctionYEAR(#0)YEAR(#0)CurrentDateTimeFunctionFROM_UNIXTIME(UNIX_TIMESTAMP())FROM_UNIXTIME(UNIX_TIMESTAMP())CurrentTimeFunctionFROM_UNIXTIME(UNIX_TIMESTAMP())FROM_UNIXTIME(UNIX_TIMESTAMP())HourFunctionHOUR(#0)HOUR(#0)MinuteFunctionMINUTE(#0)MINUTE(#0)SecondFunctionSECOND(#0)SECOND(#0)MilliSecondFunction EXTRACT(MILLISECOND FROM #0) MonthStartDateFunction DATE_ADD(#0,1-DAYOFMONTH(#0))YearStartDateFunction ADD_MONTHS(date_add(date_sub(#0 ,DAY(#0) ), 1), 1 - Month(#0))AddMonthsFunction ADD_MONTHS(#0, #1)MonthsBetweenFunction (12*(YEAR(#1) - YEAR(#0)) + MONTH(#1) - MONTH(#0) - (CASE WHEN DAY(#0) > DAY(#1) THEN 1 ELSE 0 END))AddDaysFunctionDATE_ADD(#0,#1)DATE_ADD(#0,#1)MonthEndDateFunction DATE_ADD((ADD_MONTHS(#0, 1)), -DAYOFMONTH((ADD_MONTHS(#0, 1))))DateFunctionTO_DATE(#0)TO_DATE(#0)Strategy Function NameImpala 1.xImpala 2.xRunningSumFunction sum(#0) over(#1)RunningAvgFunction avg(#0) over(#1)MovingAvgFunction avg(#0) over(#1)MovingSumFunction sum(#0) over(#1)MovingCountFunction count(#0) over(#1)RunningMaxFunction max(#0) over(#1)RunningMinFunction min(#0) over(#1)RunningCountFunction count(#0) over(#1)FirstInRangeFunction first_value(#0) over(#1)LastInRangeFunction last_value(#0) over(#1)OLAPSumFunction sum(#0#< #*#>) over ([#P] [#O] [#W]) OLAPAvgFunction avg(#0#< #*#>) over ([#P] [#O] [#W])OLAPCountFunction count(#0#< #*#>) over ([#P] [#O] [#W])LagFunction lag(#0#<, #*#>) over ([#P] [#O])LeadFunction lead(#0#<, #*#>) over ([#P] [#O])OLAPRankFunction rank() over ([#P] [#O])Strategy Function NameImpala 1.xImpala 2.xRound2FunctionROUND(#0, #1)ROUND(#0, #1)RankFunction #0#,#<partition by#>#<#, #*#>#|rank () over(#1#2#<, #*#> order by #0)AbsFunctionABS(#0)ABS(#0)AcosFunctionACOS(#0)ACOS(#0)AcoshFunctionLN(#0+SQRT(#0-1)*SQRT(#0+1))LN(#0+SQRT(#0-1)*SQRT(#0+1))AsinFunctionASIN(#0)ASIN(#0)AtanFunctionATAN(#0)ATAN(#0)AtanhFunction((LN(1+#0)-LN(1- #0))/2)((LN(1+#0)-LN(1- #0))/2)CeilingFunctionCEIL(#0)CEIL(#0)CosFunctionCOS(#0)COS(#0)CoshFunction((EXP(#0)-EXP(#0*(-1)))/2) ((EXP(#0)-EXP(#0*(-1)))/2)DegreesFunctionDEGREES(#0)DEGREES(#0)ExpFunctionEXP(#0)EXP(#0)FloorFunctionFLOOR(#0)FLOOR(#0)IntFunction FLOOR(#0)LnFunctionLN(#0)LN(#0)LogFunctionLOG(#1, #0)LOG(#1, #0)Log10FunctionLOG10(#0)LOG10(#0)PowerFunctionPOWER(#0, #1) POWER(#0, #1)QuotientFunctionCAST(#0/#1 AS INT)CAST(#0/#1 AS INT)RadiansFunctionRADIANS(#0)RADIANS(#0)RandbetweenFunction ((#1- #0)*RAND()+#0)RoundFunctionROUND(#0)ROUND(#0)SinFunctionSIN(#0)SIN(#0)SinhFunction((EXP(#0)+EXP(#0*(-1)))/2)((EXP(#0)+EXP(#0*(-1)))/2)SqrtFunctionSQRT(#0)SQRT(#0)TanFunctionTAN(#0)TAN(#0)TanhFunction(-1+(2/(1+EXP(-2*#0))))(-1+(2/(1+EXP(-2*#0))))TruncFunctionCAST(#0 AS INT)CAST(#0 AS INT)AsinhFunctionLN(#0+SQRT(POW(#0, 2)+1))LN(#0+SQRT(POW(#0, 2)+1))ModFunctionSIGN(#0)*PMOD(ABS(#0), #1)SIGN(#0)*PMOD(ABS(#0), #1)Strategy Function NameImpala 1.xImpala 2.xStandardizeFunctioncase when (#2 > 0) then (#0 - #1)/(#2) else NULL endcase when (#2 > 0) then (#0 - #1)/(#2) else NULL end •Make sure your database supports the character set(s) that are required by the various languages you intend to support in your Strategy project. Strategy recommends using a Unicode database to ensure all your languages are supported. For details, see Adding or removing a language in the system. •If you will be supporting double-byte languages (such as Japanese or Korean), make sure that appropriate fonts are available for graph labels, text fields in documents, and so on. Appropriate fonts to support double-byte languages are generally Unicode fonts. An example of an effective Unicode font for double-byte languages is Arial Unicode MS. Most Unicode fonts ensure that all characters can be displayed correctly when a report or document is displayed in a double-byte language. •All SQL-based qualifications contained in a given report should be in a single language. SQL-based qualifications include such things as report filters, metrics, and prompts. •If you have old projects with metadata objects that have been previously translated, it is recommended that you merge your translated strings from your old metadata into the newly upgraded metadata using Strategy Project Merge. For steps, see Translating already translated pre-9.x projects. •It is recommended for Developer internationalization that you use a unified locale. For example, if French is the language selected for the interface, the metadata objects language preference and report data language preference, as well as number and date preferences, should also be in French. •If you are using or plan to use Strategy Intelligent Cubes, and you plan to implement data internationalization, it is recommended that you use a SQL-based DI model. The SQL-based DI model is described in Providing data internationalization. Because a single Intelligent Cube cannot connect to more than one data warehouse, using a connection-based DI model requires a separate Intelligent Cube to be created for each language, which can be resource-intensive. Details on this cost-benefit analysis as well as background information on Intelligent Cubes are in the Strategy In-memory Analytics Guide. | After it's finished, instance will go back to previous state. e.g. if instance state is running before resizing, then it will go back to running afterwards.
IntermediateNoRunning, StoppedRebootingThe instance is rebooting.IntermediateNoStarting, Running Cloudera CDH 4.x with Hive 32-bit Cloudera ODBC driver for Apache Hive v2.5 Certified Cloudera CDH 4.x with Impala 1.x 32-bit Cloudera ODBC driver for Apache Impala v 2.5 CertifiedStrategy Function NameImpala 1.xImpala 2.xCoalesceFunction COALESCE(#0, 0)StdevPFunction stddev_pop(#0#< #*#>) BetweenOperator#0 BETWEEN #1 and #2#0 BETWEEN #1 and #2ProductFunction (CASE WHEN SUM(CASE WHEN #0=0 THEN 1 ELSE 0 END) > 0 THEN 0 ELSE POWER(-1,SUM(CASE WHEN #0<0 THEN 1 ELSE 0 END))*EXP(SUM(LN(ABS(CASE WHEN #0<>0 THEN #0 ELSE NULL END)))) END)StdevFunction STDDEV(#0#< #*#>) VarFunction VARIANCE(#0#< #*#>)GeoMeanFunctionEXP(AVG(LN(#0)))EXP(AVG(LN(#0)))NotLikeOperator #0 NOT LIKE '#1' IsNullFunction #0 IS NULLIsNotNullFunction #0 IS NOT NULLNotInOperatornot (#0 in (#1#<, #*#>))#/#0 = #1#<#,#0=#*#>#|#<(#>#0#< and #*#>#<)#>#|not #<(#>#0#< or #*#>#<)#> not (#0 in (#1#<, #*#>))#/#0 = #1#<#,#0=#*#>#|#<(#>#0#< and #*#>#<)#>#|not #<(#>#0#< or #*#>#<)#>GreatestFunctionMAX(#0)MAX(#0)LeastFunctionMIN(#0)MIN(#0)FirstFunctionMIN(#0)MIN(#0)LastFunctionMAX(#0)MAX(#0)IFOperator(Case when #0 then #1 else #2 end)(Case when #0 then #1 else #2 end) VarPFunction VARIANCE_POP(#0#< #*#>)Strategy Function NameImpala 1.xImpala 2.xDaysBetweenFunctionDATEDIFF(#1,#0) DATEDIFF(#1,#0) YearEndDateFunction DATE_SUB(ADD_MONTHS(#0, (13 - MONTH(#0))), DAY(#0)) CurrentDateFunctionTO_DATE(FROM_UNIXTIME(UNIX_TIMESTAMP())) TO_DATE(FROM_UNIXTIME(UNIX_TIMESTAMP())) DayOfMonthFunctionDAYOFMONTH(#0)DAYOFMONTH(#0)DayOfWeekFunction DAYOFWEEK(#0) DayOfYearFunction DAYOFYEAR(#0)WeekFunctionWEEKOFYEAR(#0) WEEKOFYEAR(#0)MonthFunctionMONTH(#0)MONTH(#0)YearFunctionYEAR(#0)YEAR(#0)CurrentDateTimeFunctionFROM_UNIXTIME(UNIX_TIMESTAMP())FROM_UNIXTIME(UNIX_TIMESTAMP())CurrentTimeFunctionFROM_UNIXTIME(UNIX_TIMESTAMP())FROM_UNIXTIME(UNIX_TIMESTAMP())HourFunctionHOUR(#0)HOUR(#0)MinuteFunctionMINUTE(#0)MINUTE(#0)SecondFunctionSECOND(#0)SECOND(#0)MilliSecondFunction EXTRACT(MILLISECOND FROM #0) MonthStartDateFunction DATE_ADD(#0,1-DAYOFMONTH(#0))YearStartDateFunction ADD_MONTHS(date_add(date_sub(#0 ,DAY(#0) ), 1), 1 - Month(#0))AddMonthsFunction ADD_MONTHS(#0, #1)MonthsBetweenFunction (12*(YEAR(#1) - YEAR(#0)) + MONTH(#1) - MONTH(#0) - (CASE WHEN DAY(#0) > DAY(#1) THEN 1 ELSE 0 END))AddDaysFunctionDATE_ADD(#0,#1)DATE_ADD(#0,#1)MonthEndDateFunction DATE_ADD((ADD_MONTHS(#0, 1)), -DAYOFMONTH((ADD_MONTHS(#0, 1))))DateFunctionTO_DATE(#0)TO_DATE(#0)Strategy Function NameImpala 1.xImpala 2.xRunningSumFunction sum(#0) over(#1)RunningAvgFunction avg(#0) over(#1)MovingAvgFunction avg(#0) over(#1)MovingSumFunction sum(#0) over(#1)MovingCountFunction count(#0) over(#1)RunningMaxFunction max(#0) over(#1)RunningMinFunction min(#0) over(#1)RunningCountFunction count(#0) over(#1)FirstInRangeFunction first_value(#0) over(#1)LastInRangeFunction last_value(#0) over(#1)OLAPSumFunction sum(#0#< #*#>) over ([#P] [#O] [#W]) OLAPAvgFunction avg(#0#< #*#>) over ([#P] [#O] [#W])OLAPCountFunction count(#0#< #*#>) over ([#P] [#O] [#W])LagFunction lag(#0#<, #*#>) over ([#P] [#O])LeadFunction lead(#0#<, #*#>) over ([#P] [#O])OLAPRankFunction rank() over ([#P] [#O])Strategy Function NameImpala 1.xImpala 2.xRound2FunctionROUND(#0, #1)ROUND(#0, #1)RankFunction #0#,#<partition by#>#<#, #*#>#|rank () over(#1#2#<, #*#> order by #0)AbsFunctionABS(#0)ABS(#0)AcosFunctionACOS(#0)ACOS(#0)AcoshFunctionLN(#0+SQRT(#0-1)*SQRT(#0+1))LN(#0+SQRT(#0-1)*SQRT(#0+1))AsinFunctionASIN(#0)ASIN(#0)AtanFunctionATAN(#0)ATAN(#0)AtanhFunction((LN(1+#0)-LN(1- #0))/2)((LN(1+#0)-LN(1- #0))/2)CeilingFunctionCEIL(#0)CEIL(#0)CosFunctionCOS(#0)COS(#0)CoshFunction((EXP(#0)-EXP(#0*(-1)))/2) ((EXP(#0)-EXP(#0*(-1)))/2)DegreesFunctionDEGREES(#0)DEGREES(#0)ExpFunctionEXP(#0)EXP(#0)FloorFunctionFLOOR(#0)FLOOR(#0)IntFunction FLOOR(#0)LnFunctionLN(#0)LN(#0)LogFunctionLOG(#1, #0)LOG(#1, #0)Log10FunctionLOG10(#0)LOG10(#0)PowerFunctionPOWER(#0, #1) POWER(#0, #1)QuotientFunctionCAST(#0/#1 AS INT)CAST(#0/#1 AS INT)RadiansFunctionRADIANS(#0)RADIANS(#0)RandbetweenFunction ((#1- #0)*RAND()+#0)RoundFunctionROUND(#0)ROUND(#0)SinFunctionSIN(#0)SIN(#0)SinhFunction((EXP(#0)+EXP(#0*(-1)))/2)((EXP(#0)+EXP(#0*(-1)))/2)SqrtFunctionSQRT(#0)SQRT(#0)TanFunctionTAN(#0)TAN(#0)TanhFunction(-1+(2/(1+EXP(-2*#0))))(-1+(2/(1+EXP(-2*#0))))TruncFunctionCAST(#0 AS INT)CAST(#0 AS INT)AsinhFunctionLN(#0+SQRT(POW(#0, 2)+1))LN(#0+SQRT(POW(#0, 2)+1))ModFunctionSIGN(#0)*PMOD(ABS(#0), #1)SIGN(#0)*PMOD(ABS(#0), #1)Strategy Function NameImpala 1.xImpala 2.xStandardizeFunctioncase when (#2 > 0) then (#0 - #1)/(#2) else NULL endcase when (#2 > 0) then (#0 - #1)/(#2) else NULL end •Make sure your database supports the character set(s) that are required by the various languages you intend to support in your Strategy project. Strategy recommends using a Unicode database to ensure all your languages are supported. For details, see Adding or removing a language in the system. •If you will be supporting double-byte languages (such as Japanese or Korean), make sure that appropriate fonts are available for graph labels, text fields in documents, and so on. Appropriate fonts to support double-byte languages are generally Unicode fonts. An example of an effective Unicode font for double-byte languages is Arial Unicode MS. Most Unicode fonts ensure that all characters can be displayed correctly when a report or document is displayed in a double-byte language. •All SQL-based qualifications contained in a given report should be in a single language. SQL-based qualifications include such things as report filters, metrics, and prompts. •If you have old projects with metadata objects that have been previously translated, it is recommended that you merge your translated strings from your old metadata into the newly upgraded metadata using Strategy Project Merge. For steps, see Translating already translated pre-9.x projects. •It is recommended for Developer internationalization that you use a unified locale. For example, if French is the language selected for the interface, the metadata objects language preference and report data language preference, as well as number and date preferences, should also be in French. •If you are using or plan to use Strategy Intelligent Cubes, and you plan to implement data internationalization, it is recommended that you use a SQL-based DI model. The SQL-based DI model is described in Providing data internationalization. Because a single Intelligent Cube cannot connect to more than one data warehouse, using a connection-based DI model requires a separate Intelligent Cube to be created for each language, which can be resource-intensive. Details on this cost-benefit analysis as well as background information on Intelligent Cubes are in the Strategy In-memory Analytics Guide. |
