50320_en-US

liliconcom

Good ways to manage ODBC?

I got the following comment from a ATMEL (Microchip technologies) a semiconductor customer in our patch.

 

I find that JMP is really good an analysis, but getting data into JMP is not easy for many process and device engineers.  I hope to hold a class to show folks how we have integrated data extracts into our system.  Making it trivial to get data into JMP usually determines whether or not folks will use it, in my experience.

 

The problem (IMO) with the JMP data sources is the dependence on ODBC.   We have a half dozen or so databases to access, and to ensure >100 users on 3 continents all have the correct ODBC data sources defined, current drivers, etc., is a logistical difficulty. 

 

Does anyone have a good test case or best practices for rolling out ODBC drivers for multiple database types to a large group of users?

 

 

Re: Good ways to manage ODBC?I guess another option is presentation server licensing. ODBC only needs to be set up for the server machine then.

Phil
Re: Good ways to manage ODBC?

Thanks Phil,

 

That is a great discovery talk to share with the customer it is even from the same industry.  I also like your point that it should be a priority for IT to get the engineers to access the data.

Re: Good ways to manage ODBC?https://community.jmp.com/t5/Discovery-Summit-Europe-2017/jClick-Revolutionizing-Data-Analysis-and-Delivery-in/ta-p/36702

Hi Pete,
I think this is largely a challenge for their IT people. They have invested in collecting the data and the engineers clearly see value in the data. IT need to step-up to support them getting the data.
Having said that there are ways around this. Intel presented at Discovery and they told us how they do the SQL query as a separate step:

1. Schedule an SQL query to run at a required frequency.
2. Send the output of that query, as a csv, to a shared location accessible by anyone who needs it.
3. Create a JSL script that calls that csv file and performs an analysis. The key in creating these scripts is to let JMP do the vast majority of the scripting for you.
4. Save the JSL script in the same shared location. Embed a script that calls this JSL script (using Include) in a button on a journal.
5. Distribute the Journal
BTW, this is a great presentation and story to share with customers about how JMP can become the standard analysis tool.
Regards,
Phil