cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Don’t miss your chance to experience Discovery Summit Europe at our best available rate! Early bird registration through 31 Oct.
  • Image to Table JMP extension imports single or batch images as data tables. Useful to extract curves from pictures or convert image data to curve data to use in analyses like Functional Data Explorer. Download and install the extension.

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
Thierry_S
Super User

Windows Pro 10 > JMP 17.2 > ODBC Connections > Preventing file saving/export?

Hi JMP Community,

 

I am exploring the option of connecting JMP to an ODBC-enabled database that contains sensitive data.

The database administrator asked me if there is a method in JMP to prevent saving or exporting the primary data uploaded via OBDC connections.

 

Sorry for not being more specific. I have zero experience using JMP to connect to databases.

 

Thank you.

 

Best regards,

TS

Thierry R. Sornasse
1 ACCEPTED SOLUTION

Accepted Solutions

Re: Windows Pro 10 > JMP 17.2 > ODBC Connections > Preventing file saving/export?

Hey @Thierry_S 

 

I've run into this question in the past. The customers have generally taken a tiered approach.  Some data is generally available (non-sensitive), other data is available via password (more sensitive and requires training on approved use and storage), and finally putting JMP on a heavily locked down server/vm (most sensitive data - prevents removal from the source, controls access, and logs who is accessing).

 

The first two tiers are still going to allow save/export, but the third would do what you want but requires additional resources. So, it depends a ton on how many people are needing access to the highly sensitive data. 

View solution in original post

1 REPLY 1

Re: Windows Pro 10 > JMP 17.2 > ODBC Connections > Preventing file saving/export?

Hey @Thierry_S 

 

I've run into this question in the past. The customers have generally taken a tiered approach.  Some data is generally available (non-sensitive), other data is available via password (more sensitive and requires training on approved use and storage), and finally putting JMP on a heavily locked down server/vm (most sensitive data - prevents removal from the source, controls access, and logs who is accessing).

 

The first two tiers are still going to allow save/export, but the third would do what you want but requires additional resources. So, it depends a ton on how many people are needing access to the highly sensitive data. 

Recommended Articles