Define Metric name as Column alias in MIcroStrategy

By Default MicroStrategy uses the  metric name something like  'WJXBFS1' during SQL generation .

MicroStrategy has a Very Large Database (VLDB) setting to allow users to change this default behavior at the project level so that the metric's name can be used as a column alias.

To change the MicroStrategy SQL Engine's default behavior and use the metric's name as a column alias, configure the VLDB setting, 'Default to Metric Name'. 

Lets say your report SQL looks similar to this for report object call center  attribute and revenue metric.

Select a11.CALL_CTR_ID CALL CTR_ID,
max(a12.CENTER_NAME) CENTER_NAME,
sum(a11.TOT_DOLLAR_SALES) WJXBFS1
from CITY_CTR_SLS a11
join LU_CALL_CTS a12
on (a11.CALL_CTR_ID = a12.CALL_CTR_ID)
group by a11.CALL_CTR_ID

To locate the exact setting: 

1. Go to 'Project Configuration' for the specified project (Right-click on the project to open the Project Configuration editor).
2. Under 'Project Definition', choose 'Database instance'. The 'VLDB Properties' button will appear. Click on this button to open the VLDB Properties editor.
3. Open the Metrics folder. Under 'Default to Metric Name', uncheck the 'Use default inherited value' box and click the radio button for 'Use the metric name as the default metric column alias'.
   
   Note: For this setting to take effect in 2-tier, the user must disconnect from the project source. In 3-tier, the MicroStrategy Intelligence Server must be re-started .
4. if you Re-execute the report then report SQL would looks like.

select a11.CALL_CTR_ID CALL CTR_ID,

max(a12.CENTER_NAME) CENTER_NAME,
sum(a11.TOT_DOLLAR_SALES) REVENUE
from CITY_CTR_SLS a11
join LU_CALL_CTS a12
on (a11.CALL_CTR_ID = a12.CALL_CTR_ID)
group by a11.CALL_CTR_ID

now you can notice that report SQL showing the alias name same as metric name. It helps us to identify the exact SQL for metric without any confusion .