Question on ODBC Output
- jim wood
- Site Admin
- Posts: 3951
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Question on ODBC Output
Guys,
I got in to a debate with a guy that I'm on site with. He was saying that he always exports to flat file rather than use odbc for 3 reasons:
1) Sychronus actions in the ODBC (hmmm)
2) ODBC Output is slow as it generates a log (Tiny data packet so I wan't buying)
3) A DB pulling is faster than being pushed to. (Again tiny data packet)
What do you guys use and why? Do you stick one method and why?
Jim.
I got in to a debate with a guy that I'm on site with. He was saying that he always exports to flat file rather than use odbc for 3 reasons:
1) Sychronus actions in the ODBC (hmmm)
2) ODBC Output is slow as it generates a log (Tiny data packet so I wan't buying)
3) A DB pulling is faster than being pushed to. (Again tiny data packet)
What do you guys use and why? Do you stick one method and why?
Jim.
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
-
- MVP
- Posts: 1815
- Joined: Mon Dec 05, 2011 11:51 am
- OLAP Product: Cognos TM1
- Version: PA2.0 and most of the old ones
- Excel Version: All of em
- Location: Manchester, United Kingdom
- Contact:
Re: Question on ODBC Output
I prefer having data in a database as a medium but agree that individual updates are slow using ODBCoutput, as such I do asciiouputs followed by a single ODBCOutput to run a bulk insert, then delete the flat file.
So my answer is yes and no but that wasn't an option.
So my answer is yes and no but that wasn't an option.
Declan Rodger
-
- MVP
- Posts: 2832
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Question on ODBC Output
My answer is it depends. If I am doing minor updates, like setting a flag or doing an incremental extract, then I might use ODBCOutput and write directly to the database. If I am writing thousands of records to a DB then I would most likely dump to a flat file and use some other tool to import that into the database.
- jim wood
- Site Admin
- Posts: 3951
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Question on ODBC Output
Good point Declan. The post and the poll are kind of the same but seperate. My post was more an aswering of my friends point. The poll is to find out how many people use it. I (as usual) didn't explain myself very well.
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
- Alan Kirk
- Site Admin
- Posts: 6606
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: Question on ODBC Output
I'm glad that it's there and if I was writing to a small, localised database I would (and indeed have on some occasions) use it; essentially the same kind of thing as Tomok described. However the feed that we do to our BW system at present is flat file based. That was at their request since their own ETL tool needs to do some redirecting of the various fields, but even if it wasn't I would be reluctant to use a direct connection to feed something like an ERP because you end up losing control over your server's performance. If something is happening on the ERP side that is causing updates in general to run.... really.... slowly.... then you can end up with an effectively hung server for an indefinite amount of time. Granted the risk is small (assuming that the ERP back end is well designed and maintained), but it's there, and unless the updates are time critical I don't see the need to take it.
I therefore voted no, but it's a qualified no.
I therefore voted no, but it's a qualified no.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-
- MVP
- Posts: 3654
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Question on ODBC Output
Also same as Declan and Tom. I use it all the time but usually for small DBs that I'm in control of. For large inserts (10s of K records) or to an external DB that I don't have any control over, then a bulk upsert is much more preferable.
Last edited by lotsaram on Tue Sep 23, 2014 4:08 pm, edited 1 time in total.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
-
- MVP
- Posts: 3120
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.0.9.18
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Question on ODBC Output
Me too.
Best regards,
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- MVP
- Posts: 2832
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Question on ODBC Output
Let me just add that IF you decide to use the ODBCOutput command you REALLY should create a stored procedure on your database server and then call that, instead of issuing a direct INSERT INTO type command. When you call stored procedures instead of direct SQL calls then the syntax checking portion of the SQL workload can be skipped, saving you a few processing cycles. When you processing a lot of records the syntax checking time can add up fast.
-
- MVP
- Posts: 170
- Joined: Fri Dec 10, 2010 4:07 pm
- OLAP Product: TM1
- Version: [2.x ...] 11.x / PAL 2.0.9
- Excel Version: Excel 2013-2016
- Location: Germany
Re: Question on ODBC Output
I typically use it to set and remove flags in control tables of source DB and run optimization commands like DBMS_STATS.GATHER_TABLE_STATS to boost subsequent SQL queries.