Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: sp_execute_remote / Elastic Query fails in sqldb-dev-edition image due to missing RemoteQueryExecutor.dll

未关闭
  • 哪里不对？
#172 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
shell
领域
database

调研方向

The report identifies the sqldb-dev-edition image and the missing C:\binn\GlobalQuery\RemoteQueryExecutor.dll, but it does not name repository files or tests. First check how the image is built and whether this component is included or configured, then reproduce the separate External Table and sp_execute_remote cases in the report. Done means confirming whether the image supports these features and documenting or correcting the missing component or configuration.

由索引模型根据 Issue 内容生成。

描述

bug User-filled
Container image tag

sqldbpreview-dpgaeqhmgphzd4bk.azurecr.io/mssql-server/sqldb-dev-edition

Host OS

Linux (x86_64)

Container runtime and version

latest

What happened

Hi,

Can you confirm whether sp_execute_remote / Elastic Query is expected to be supported in the sqldb-dev-edition image?

We successfully imported the BACPACs and verified that sys.sp_execute_remote exists, but an actual execution fails with:

Error 15804:
Could not load external library 'C:\binn\GlobalQuery\RemoteQueryExecutor.dll'

We couldn't find RemoteQueryExecutor.dll in the image.

Is this expected, does it require additional configuration, or is the image missing a component required for remote query execution?

The same Happen if I tye using the external reference table

Thanks.

Steps to reproduce

Titolo

Verificare External Tables e sp_execute_remote in Azure SQL Database Dev

Obiettivo

Verificare separatamente la lettura tramite External Table e l’esecuzione di una query tramite sp_execute_remote in Azure SQL Database Dev. I due test sono indipendenti: il risultato di uno non determina quello dell’altro.

Prerequisiti

  • Un’istanza Azure SQL Database Dev avviata e raggiungibile.
  • Due database di prova, uno chiamante e uno remoto.
  • Nel database chiamante, un’External Data Source configurato verso il database remoto e un’External Table che lo espone.
  • Permessi sufficienti per eseguire le query di test.

Test A: External Table

Connettersi al database chiamante ed eseguire:

SELECT TOP (1) *
FROM [schema].[external_table];

Annotare query, risultato o errore completo e identificativo del database.

Test B: sp_execute_remote

Connettersi allo stesso database chiamante ed eseguire:

EXEC sys.sp_execute_remote
    @data_source_name = N'<external_data_source_name>',
    @stmt = N'SELECT 73129 AS Marker;';

Annotare query, risultato o errore completo e identificativo del database.

Risultato da riportare

Per ciascun test indicare separatamente:

  • esito: riuscito o fallito;
  • output o messaggio d’errore completo;
  • versione e stato di Azure SQL Database Dev;
  • configurazione rilevante della sorgente esterna, senza includere credenziali.

Non interpretare un errore dell’External Table come prova del comportamento di sp_execute_remote, né viceversa.

Additional context

No response

Confirmation
  • I scanned open issues and Known limitations for a duplicate.
主要语言
Shell
星标
18
派生
7
平均合并
7 天 4 小时
30 天内合并 PR
4

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/azure-sql-database-container 的其他 Issue

查看 microsoft/azure-sql-database-container 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。