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

KB310067: Datatypes display as “Unknown” in Warehouse Catalog when using Snowflake on MicroStrategy 10.4


Community Admin

• Strategy


This Technical Note describes an issue that occurs with using tables and columns from a Snowflake database in the Warehouse Catalog in MicroStrategy 10.4. This issue has been classified as a defect by MicroStrategy. A workaround is provided in the current version, and a code fix for this issue is also available in MicroStrategy 10.5.

SUMMARY:
This Technical Note describes an issue that occurs with using tables and columns from a Snowflake database in the Warehouse Catalog in Strategy 10.4. This issue has been classified as a defect by Strategy. A workaround is provided in the current version, and a code fix for this issue is also available in Strategy 10.5.
 
SYMPTOM:
In Strategy 10.4, all column's datatypes display as unknown in the Warehouse Catalog except for columns of the date datatype when using Snowflake as a warehouse.
 
STEPS TO REPRODUCE:
Follow these steps to reproduce the issue in the Strategy Tutorial Project.

  • Create a database instance against a Snowflake database.
  • In warehouse catalog, right click on a table on the left coming from the Snowflake database and select ‘table structure’.
  • Notice the Datatype displays as Unknown as shown below:
ka04W000000ObRNQA0_0EM440000002C1C.jpeg
  • Figure 1: Unknown data type in warehouse catalog

 
CAUSE:
This is an identified defect in Strategy 10.4
 
ACTION:
This issue was supposedly addressed in Strategy 10.5 but many customers are reporting this as still an issue as late as 10.11 CU1. Look for a resolution in future releases
 
WORKAROUNDS:
There are two possible workarounds to deal with this issue. Use the following steps from one of the two options to work around this issue;
Option 1:

  1. Connect to the project source -> administration -> configuration manager -> database instances.
  2. Edit the database instance using the DSN connecting to Snowflake.
  3. Change the ‘database connection type’ from ‘Snowflake 1.0’ to ‘Generic Database’. This will allow the Snowflake Cloud Metadata to correctly read the columns/data types when new tables are added via Warehouse Catalog.
  4. Go to warehouse catalog and add a table, or update the table structure. The table should display the correct data type.
  5. Once the tables have been added, set the database connection type back to Snowflake 1.0.

Option 2: 

  1. Import tables as normal from Snowflake.
  2. When creating attributes or facts go to the column alias tab or option and manually create a column alias with the correct datatype.


3100637


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

November 30, 2018