Is anyone using the new Suite Analytics instance <...
# general
l
Is anyone using the new Suite Analytics instance NetSuite2.com? I am in charge of moving from the old one (netsuite.com) to the new and facing lots of performance issues. Also found multiple lines for the same id when querying specific tables (i.e. transactionline). Any experience sorting out those issues? Thanks yoy in advance
d
You might already know that 'tables' in Suite Analytics are actually 'views' projected as tables. So one of the biggest issues with some 'tables' is that some have a huge number of joins. For example, one of the tables I was dealing with had 27 joins if you did a SELECT *. The solution from NS was don't use SELECT *.
I've also found tables where the primary key doesn't work due to duplicate id's or null values. Only option is to work around it.
l
Thanks @dynamicl I didn't have these kind of issues working with netsuite.com. It would be nice if Oracle could provide us with access to the source tables instead or any option to exclude the columns provided by the joins with other tables.
In terms of BI, it is a very poor design as does not allow to extract the data correctly in an incremental way as Oracle does not have [EXCEPT] instruction in the statements and, in any case, it forces us to run a distinct on the data once extracted
d
Same experience really, netsuite.com was easier to work with with far less 'tables'. We sync everything, so for netsuite.com it was 600-700 tables, and now for netsuite2.com its around 1700-1800 tables (like for like bundles\modules).
Again, you might already know, but setup > records catalog will show you all the joins and cardinality. So for example, if you just do a select on non-joined fields you will notice the response times are much better.
l
Thanks again @dynamicl I didn't know about Records Catalog. I have requested access to the Admins