cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • JMP Security Notice: CVE-2026-109618 and CVE-2026-109619

    JMP promptly initiated a review of its products, services, and relevant infrastructure for exposure to CVE-2026-109618 and CVE-2026-109619.

    Our assessment of JMP products has not identified exposure to these vulnerabilities. Where remediation was required within supporting environments, appropriate security updates and controls have been applied and validated.

    We have identified no evidence of successful exploitation or unauthorized access to JMP systems or customer information associated with these vulnerabilities.

    JMP continues to monitor the issue and relevant vendor guidance. No action is required by JMP customers at this time.

  • Don’t miss your chance to experience Discovery Summit Europe at our best available rate! Early bird registration through 31 Oct.
  • Graph Builder Toolbar streamlines interactive graphing. Creates shortcuts on Report and GraphBuilder Helpers toolbars. Download and install the extension.

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
aharro
Level II

Open Data Base Efficiency/Run Time

Hello,

When you use Open Database() it opens the database and runs the query. Well, when you need to run multiple queries on the same database does it hinder run time performance?

When I run local queries the run time is super quick every time. However,
when I run several queries on JMP with Open DataBase() I seem to get mixed results. I'm thinking I may be losing performance by reconnecting to the db over and over.

Is there a way to stay connected to the db and pass in queries?

for(i=1, i<=N Items(query_list), i++,
Open DataBase(server, query_list[i], "foo");
wait(1);
);




2 REPLIES 2
jthi
Super User

Re: Open Data Base Efficiency/Run Time

I would suggest using New SQL Query() instead of other methods (Which way to go query database? ). It is the most complicated one and has lacking documentation (in my opinion) but it is still the way which will be getting enhancements.

-Jarmo
mmarchandFSLR
Level VI

Re: Open Data Base Efficiency/Run Time

New SQL Query can run multiple queries simultaneously, if you use the <<Run Background message.

 

And you can keep it simple by using Custom SQL.

 

For Each( {v, i}, queries,
			New SQL Query(
				Connection( constring ),
				Custom SQL(
					"SELECT Col1, Col2
FROM Table1
WHERE Col1 = 'Good Data'" ), Query Name( v || " contents" ) ) << Run Background( On Error( Print( "Huh. Didn't work." ) ), On Run Complete( dt = QueryResult...... ) ) ) ) );

Recommended Articles