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.

JMP Wish List

We want to hear your ideas for improving JMP. Share them here.
Choose Language Hide Translation Bar
0 Kudos

Proper information in Log window when executing SQL query

What inspired this wish list request?

 

JMP expects an actual table to be returned in a SQL query. So, if the SQL query contains create temp table, we must add "SET NOCOUNT ON" so the Transact-SQL statement does not try to return the rows impacted by the query. If there is not this line in the beginning of the SQL query, JMP just can't return any result and there is not any meaningful feedback in GUI or Log window.

 

 

What is the improvement you would like to see? 

Add meaningful feedback in GUI or Log window.

 

Why is this idea important? 

We need to have a proper response for any implementation, right?

 

 

1 Comment
Sarah-Sylvestre
Level V
Status changed to: Acknowledged

Thank you for taking the time to share this feedback!