40128_en-US

liliconcom

Trouble keeping JMP connected to a database

I'll ask this question here before turning to Tech Support channels...

 

I was on the phone with a client today who mentioned that they were having some trouble with JMP accessing a database.  Turns out they could connect to the database and run queries just fine.  But (as I understand it) if they left JMP open, then came back to it later and tried to connect, it was as if the database no longer recognized their credentials.  

 

Has anyone else heard of this kind of behavior?  Is it likely a JMP problem or (my vote) a database issue (timeout due to inactivity, etc.)?  Is there an easy way to get JMP to reset the connection?

 

Thanks,

Jerry

Re: Trouble keeping JMP connected to a database

Jerry,

My understanding after confirming with our developers is JMP does not hold onto connections, that is we close them.  This is a best practice and a standard for ODBC connections.

Can you confirm if they are using a SQL Server 13 driver?  This particular source has SSL capabilities which can lead to a stale state. However, this driver is not intended to be used with JMP.  

If this is the case I would suggest they use the native SQL Server ODBC driver.  

This would also ensure correct datatypes for timestamps.

Stan

Re: Trouble keeping JMP connected to a databaseYeah, apparently pictures don’t go through when you reply from an email…
Re: Trouble keeping JMP connected to a database

Thank you Mike!  I'll pass this along.

 

I don't see the screenshot that you referenced from my browser.  I assume it is the disconnect button on the query builder screen?

Re: Trouble keeping JMP connected to a databaseI think it’s probably a database issue. In JMP you can terminate a connection by using the disconnect button on this screen:

[cid:E9447FE9-D02E-4EB5-AF53-17BB89BD6FAE]

I recall hearing somewhere that it’s actually good database etiquette to do this regardless of the JMP connectivity issues.

Best,

M