TM1 9.5.2 vs TM1 10.1.1 SQL query

Post Reply
EvgenyT
Community Contributor
Posts: 324
Joined: Mon Jul 02, 2012 9:39 pm
OLAP Product: TM1
Version: PAL 2.0.8
Excel Version: 2016
Location: Sydney, Australia

TM1 9.5.2 vs TM1 10.1.1 SQL query

Post by EvgenyT »

Hi Guys,

New to the forum. I have encountered a strange issue while working on a model using TM1 9.5.2 and TM1 10.1.1. I have development model running on a test server under 9.5.2 and live model on production server under 10.1.1. Both point to the same SQL DB using exactly the same query. Problem I have is that on 9.5.2 query extracts date from sql e.g 01/01/2010 00:00:00 subsequently I have a code in TI to convert to my dimension convention year/month/date and it works fine. On the other hand the same query on under 10.1.1 get interpreted as 2010-01-01 00:00:00, which obviously fails during conversion. Now, I have no problem with adjusting my TI to convert to year/month/date, but just something odd that I found today and thought maybe someone can shine some light on it....


Looking forward to you suggestions.

Thank you,

Evgeny
BigG
Community Contributor
Posts: 211
Joined: Tue Sep 15, 2009 11:13 pm
OLAP Product: IBMPA
Version: PA 2.0 Cloud
Excel Version: 2010

Re: TM1 9.5.2 vs TM1 10.1.1 SQL query

Post by BigG »

Hi, welcome..

Strange behaviour ...is it because 10.1.1 is supporting different languages now and the date format is different for the language setting...?
GG
David Usherwood
Site Admin
Posts: 1458
Joined: Wed May 28, 2008 9:09 am

Re: TM1 9.5.2 vs TM1 10.1.1 SQL query

Post by David Usherwood »

Suggest you check the settings on your ODBC DSNs - perhaps they have different collations or whatever.
EvgenyT
Community Contributor
Posts: 324
Joined: Mon Jul 02, 2012 9:39 pm
OLAP Product: TM1
Version: PAL 2.0.8
Excel Version: 2016
Location: Sydney, Australia

Re: TM1 9.5.2 vs TM1 10.1.1 SQL query

Post by EvgenyT »

David Usherwood wrote:Suggest you check the settings on your ODBC DSNs - perhaps they have different collations or whatever.
Hi David,

It was ODBC problem indeed. Thanks for pointing that out!

"Use regional settings when outputting currency, numbers, dates and times" button was not checked for one of them.

Regards,

Evgeny
Post Reply