EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB16779: Database instance table prefix is not used in the creation of a datamart table in MicroStrategy Developer 9.x and 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Database instance table prefix is not used in the creation of a datamart table in MicroStrategy Developer 9.x and 10.x

SYMPTOM:
In Strategy Developer 9.x and 10.x, database instance table prefix is not used in the creation of datamart tables. Table prefix in a database instance can be set by going to Database Instance editor and then going to the Advanced tab as shown below:
 

ka02R000000kVdOQAU_0EM440000002F8w.jpeg

 
After setting the database instance table prefix, if the user creates a datamart report, the datamart table that is created in the process does not use the above table prefix as seen in the following SQL below:
 
create table DatamartTable (
COUNTRY_ID BYTE,
CUST_COUNTRY_DESC TEXT)
insert into DatamartTable
select a11. AS COUNTRY_ID,
a11. AS CUST_COUNTRY_DESC
from a11
CAUSE:
This is working as designed. Datamart tables have their own table prefix which can be specified in the Report Editor under Data > Configure Data Mart > Advanced, as shown below:
 

ka02R000000kVdOQAU_0EM440000002F8n.jpeg

 
The database instance table prefix is only used when jobs such as report execution and element requests are run for projects associated with that particular database instance.
 
Notice when the datamart table prefix is used the SQL changes to the following:
 
create table TestDatamartTable (
COUNTRY_ID BYTE,
CUST_COUNTRY_DESC TEXT)
insert into TestDatamartTable
select a11. AS COUNTRY_ID,
a11. AS CUST_COUNTRY_DESC
from a11


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017