We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
change the specification of SPSS Modeler 18.1 around the SQL statement syntax check while accessing to Azure SQL Data Warehouse.
We’d like you to change the specification of SPSS Modeler 18.1 around the SQL statement syntax check while accessing to Azure SQL Data Warehouse. Currently Modeler uses the stored procedure called “sp_prepare “ which has big overhead because of generating an execution plan on SQL Data Warehouse. So it is necessary to change to “SET PARSEONLY ON” + SQL statement that is only for syntax check.
Tens of our staffs deeply use SPSS Modeler and most of SQL statements which it generates are commonly very large. When we did performance test using Modeler with Azure SQL Data Warehouse, we found “sp_prepare” was called several times before executing a SQL statement and it took a long time to call the stored procedure. So we asked Microsoft to suggest us and they said below.
You should not use “sp_prepare” only for syntax check because it makes an execution plan and should change to use “SET PARSEONLY ON” + SQL statement. This “SET PARSEONLY” statement has been supported since SQL Server 2008. And it is also supported to both Azure SQL Database and Azure SQL Data Warehouse.
This issue also impacts the performance of short SQL statements which Modeler generates. The overhead of “sp_prepare” stands out since those SQL statements perform quickly.
Do not place IBM confidential, company confidential, or personal information into any field.