ACS Index Serverless SQL Pool

Question

We have successfully setup and Azure SQL Data Source and Indexer previously that indexes Synapse Analytics Dedicated SQL pool tables, we were hoping to do the same for views in a Serverless SQL pool. The data source creates successfully, however when we attempt to setup the indexer we get error:

Failed to update indexer "****", error: "Error with data source: NO_BROWSETABLE is not supported for SET. Please adjust your data source definition in order to proceed."

From what I've found it looks like the Azure SQL indexer adds SET NO_BROWSETABLE ON to the script it runs to retrieve the data. Therefore looks as thought this isn't going to work as NO_BROWSETABLE isn't supported for a Serverless SQL Pool. So think our options are is to expose that view somewhere else where the standard indexer will work, or use the API to push the view data into the index from the Serverless SQL Pool.

Is there a way to get the standard indexer to work with a Serverless SQL Pool, or another approach you would recommend?

Thanks

Answer 1

Hi

Thanks for reaching out to Microsoft Q&A.

The NO_BROWSETABLE, though is around for quite a while it is a topic which has been discussed infrequently. As you have pointed out this feature doesn't seem to be supported in synapse serverless. In this situation I would request you to raise a request with microsoft support plan to confirm if there are any other alternatives or workarounds for this. Meanwhile you can raise a feature request for this using the URL below.

[https://feedback.azure.com/d365community/post/01c95528-1225-ec11-b6e6-000d3a4f09d0?page=1&sort=newest

FOR BROWSE
Specifies that updates be allowed while viewing the data in a DB-Library browse mode cursor. A table can be browsed in an application if the table includes a timestamp column, the table has a unique index, and the FOR BROWSE option is at the end of the SELECT statements sent to an instance of SQL Server.

NO_BROWSETABLE When you turn on the NO_BROWSETABLE option, all the SELECT statements behave as if the FOR BROWSE option is appended to the statements. However, the NO_BROWSETABLE option does not create the temporary tables that the FOR BROWSE option generally uses to send the results to your application.

Please Upvote and Accept as answer if the reply was helpful, this will be helpful to other community members.