What does ODBC Data Source Administrator mean?ODBC Data Source Administrator 是什么意思？
ODBC Data Source Administrator identifies a specific part of the path applications use to reach ODBC Data Source Administrator. A successful low-level test proves only that one stage responded. A usable database session also requires correct name resolution, route, the database port configured inside the selected DSN, the ODBC driver registered for the matching Windows architecture, compatible client software, TLS trust, authentication, database selection and permission for the intended operation.ODBC Data Source Administrator 标识应用程序访问 ODBC Data Source Administrator 连接路径中的特定组成部分。低层测试成功只证明一个阶段有响应。可用数据库会话还需要正确的名称解析、路由、the database port configured inside the selected DSN、协议、兼容客户端、TLS 信任、认证、数据库选择以及目标操作权限。
Treat ODBC Data Source Administrator as a Windows configuration tool, not as the database connection itself. Open the 32-bit or 64-bit executable that matches the consuming process, verify the driver on its Drivers tab, identify whether the DSN is User, System or File scoped, and repeat the test under the account that will run the application.应把 ODBC Data Source Administrator 视为 Windows 配置工具，而不是数据库连接本身。打开与消费进程匹配的 32 位或 64 位程序，在 Drivers 选项卡确认驱动，识别 DSN 属于 User、System 还是 File 范围，并使用实际运行应用的账户重新测试。
Open the ODBC administrator that matches the application打开与应用位数匹配的 ODBC 管理器
On 64-bit Windows, two executables share the ODBC Data Source
Administrator interface but manage different driver and DSN
views. The 64-bit administrator is in
%windir%\System32\odbcad32.exe; the 32-bit
administrator is in %windir%\SysWOW64\odbcad32.exe.
The directory names are counterintuitive, so verify the
executable path rather than relying on the window title.在 64 位 Windows 上，两个程序使用相同的 ODBC Data Source
Administrator 界面，但管理不同驱动和 DSN 视图。64 位管理器位于
%windir%\System32\odbcad32.exe，32 位管理器位于
%windir%\SysWOW64\odbcad32.exe。目录名称容易产生误解，因此应核对可执行文件路径，而不是只看窗口标题。
Match the tool to the consuming process, not to the operating system alone. A 32-bit desktop application running on 64-bit Windows needs a 32-bit ODBC driver and the DSN visible in the 32-bit view. A 64-bit service needs the 64-bit equivalents. If a DSN appears in one administrator but not the application, record the application architecture, account and DSN type before recreating it; otherwise duplicate names can hide the actual mismatch.工具应与消费进程匹配，而不只是与操作系统匹配。运行在 64 位 Windows 上的 32 位桌面应用，需要 32 位 ODBC 驱动以及在 32 位视图中可见的 DSN；64 位服务则需要对应的 64 位组件。如果 DSN 在某个管理器中可见而应用看不到，应先记录应用位数、账户和 DSN 类型，再决定是否重建，否则重复名称可能掩盖真实不匹配。
| Consumer消费者 | Administrator to inspect应检查的管理器 | Driver requirement驱动要求 |
|---|---|---|
| 64-bit application or service64 位应用或服务 |
System32\odbcad32.exeSystem32\odbcad32.exe
|
64-bit ODBC driver.64 位 ODBC 驱动。 |
| 32-bit application on 64-bit Windows64 位 Windows 上的 32 位应用 |
SysWOW64\odbcad32.exeSysWOW64\odbcad32.exe
|
32-bit ODBC driver.32 位 ODBC 驱动。 |
| Unknown executable未知可执行程序 | Determine process architecture first.先确定进程位数。 | Do not install both blindly; identify the supported driver package.不要盲目同时安装；先识别受支持驱动包。 |
Use each ODBC Data Source Administrator tab correctly正确使用 ODBC Data Source Administrator 各选项卡
The administrator combines several functions that should not be confused. User DSN, System DSN and File DSN tabs define connection configurations with different scopes. The Drivers tab inventories installed ODBC drivers and versions; it does not prove a driver can reach a database. Connection Pooling controls Driver Manager pooling behavior for supported drivers, while Tracing captures diagnostic activity and can add overhead or expose sensitive values if used carelessly.管理器集合了多个不应混淆的功能。User DSN、System DSN 和 File DSN 选项卡定义不同范围的连接配置；Drivers 选项卡列出已安装 ODBC 驱动及版本，但不能证明驱动能够到达数据库；Connection Pooling 控制受支持驱动的 Driver Manager 池化行为；Tracing 则捕获诊断活动，使用不当可能增加开销或暴露敏感值。
| Tab选项卡 | Use it to用途 | Do not infer不能据此推断 |
|---|---|---|
| User DSNUser DSN | Manage data sources for the current user profile.管理当前用户配置文件的数据源。 | That a Windows service or another user can see them.Windows 服务或其他用户也能看到。 |
| System DSNSystem DSN | Manage machine-scoped data sources in this architecture view.管理当前位数视图中的机器范围数据源。 | That both 32- and 64-bit applications resolve the same entry.32 位和 64 位应用都会解析同一条目。 |
| DriversDrivers | Confirm driver name, platform view and version metadata.确认驱动名称、平台视图和版本信息。 | That the driver is supported by the target database or application.驱动一定受目标数据库或应用支持。 |
| TracingTracing | Run a short, approved diagnostic capture.执行短时、获准的诊断捕获。 | That tracing is safe to leave enabled in production.可以在生产中长期启用。 |
Create a DSN with a reproducible test record创建带有可复现测试记录的 DSN
Before selecting Add, write down the consuming application, architecture, account, intended DSN scope, approved driver and target environment. Select the exact vendor driver rather than a similarly named legacy driver. Enter server, database, encryption, certificate and authentication settings from an approved configuration source. Driver dialogs vary, so capture a sanitized export or structured record instead of relying on screenshots alone.选择 Add 之前，应记录消费应用、位数、账户、目标 DSN 范围、获准驱动和目标环境。选择准确供应商驱动，不要选择名称相似的旧驱动。服务器、数据库、加密、证书和认证设置应来自获准配置来源。不同驱动对话框差异很大，因此应保存脱敏导出或结构化记录，而不是只依靠截图。
- Match context匹配上下文Launch the correct administrator under an account that represents the deployment task.使用代表部署任务的账户启动正确管理器。
- Select scope and driver选择范围和驱动Choose User, System or File DSN deliberately and record the exact driver version.明确选择 User、System 或 File DSN，并记录准确驱动版本。
- Configure without embedding secrets配置但不嵌入密钥Set endpoint and security properties while using approved runtime identity or secret delivery.设置端点和安全属性，同时使用获准的运行时身份或密钥交付。
- Run the driver test运行驱动测试Treat success as evidence for this administrator process, driver and account only.测试成功只证明当前管理器进程、驱动和账户可用。
- Run the real consumer运行真实消费者Verify from the actual application or service with a bounded read-only operation.从真实应用或服务执行有界只读操作进行验证。
Why two tests? The driver’s Test button validates its own process context. The application test validates the real executable, account, architecture, configuration lookup and data operation. Keep both results and do not substitute one for the other.为什么需要两次测试？驱动的 Test 按钮验证自身进程上下文；应用测试验证真实可执行程序、账户、位数、配置查找和数据操作。两种结果都要保留，不能相互替代。
Use ODBC tracing and pooling as controlled changes把 ODBC 跟踪与池化作为受控变更
ODBC tracing can reveal API calls, return codes and diagnostic records when an application hides the original error, but it may materially affect performance and write connection details to disk. Obtain approval, choose a protected output location, reproduce one bounded scenario, stop tracing immediately and review the file for secrets before sharing. Delete or retain the trace according to the incident’s data-handling policy.当应用隐藏原始错误时，ODBC 跟踪可以揭示 API 调用、返回码和诊断记录，但它可能显著影响性能，并把连接细节写入磁盘。应先获得批准，选择受保护输出位置，只复现一个有界场景，随后立即停止跟踪；共享前检查文件中的密钥，并根据事件数据处理政策删除或保留。
Driver Manager connection pooling can reuse an established connection across compatible requests, changing both performance and failure behavior. A new DSN setting may not appear to take effect while an old pooled connection remains alive. During a controlled test, compare a fresh process with normal pooled reuse and record pool timeout behavior. Do not disable pooling globally to fix one application without measuring the capacity and latency impact on other consumers.Driver Manager 连接池可以在兼容请求之间复用已建立连接，从而改变性能和故障行为。当旧池连接仍然存活时，新 DSN 设置可能看似没有生效。受控测试中，应比较新进程与正常池复用，并记录池超时行为。不要为了修复一个应用就全局关闭池化，而不评估对其他消费者容量和延迟的影响。
| Change变更 | Precondition前置条件 | Exit condition结束条件 |
|---|---|---|
| Enable tracing启用跟踪 | Approved window, protected file and bounded reproduction.获准窗口、受保护文件和有界复现。 | Trace stopped, file secured and sensitive data reviewed.跟踪已停止、文件已保护且敏感数据已审查。 |
| Change pooling修改池化 | Known consumers, baseline latency and rollback plan.已知消费者、延迟基线和回滚计划。 | Fresh and reused sessions validated under representative load.在代表性负载下验证新会话和复用会话。 |
| Upgrade a driver升级驱动 | Compatibility matrix for applications, data types, TLS and authentication.应用、数据类型、TLS 和认证兼容性矩阵。 | Canary passes, rollback preserved and old package removal scheduled.灰度通过、保留回滚并安排删除旧包。 |
Handoff ODBC administrator changes with evidence使用证据交接 ODBC 管理器变更
A screenshot of the Test successful dialog is not a complete handoff. Record the administrator executable path, Windows version, account used for configuration, DSN type, DSN name, driver name and version, sanitized non-secret attributes, target environment and test timestamp. Attach the change owner, approval, rollback method and applications expected to consume the definition. This lets another operator reproduce the result without guessing which ODBC view was edited.“Test successful”对话框截图并不是完整交接。应记录管理器可执行文件路径、Windows 版本、配置账户、DSN 类型、DSN 名称、驱动名称与版本、脱敏非密钥属性、目标环境和测试时间，并附上变更负责人、批准记录、回滚方法及预期消费应用。这样另一位运维人员无需猜测所编辑的 ODBC 视图即可复现结果。
Include two verification results: the driver dialog test and an application-level read-only test under the real service identity. If they differ, preserve both and investigate architecture, account scope, configuration lookup and pooling before changing the database. After rollout, inventory hosts for duplicate or stale definitions and remove temporary traces. A clean handoff states what was not tested, such as production load, write transactions, failover or certificate rotation.交接中应包含两种验证结果：驱动对话框测试，以及真实服务身份下的应用级只读测试。如果结果不同，应同时保留并优先调查位数、账户范围、配置查找和池化，而不是先修改数据库。上线后扫描主机中的重复或陈旧定义并删除临时跟踪文件。规范交接还应明确未测试事项，例如生产负载、写事务、故障切换或证书轮换。
A repeatable ODBC Data Source Administrator diagnostic workflow可重复的 ODBC Data Source Administrator 诊断流程
Move from observed runtime context to the first failing stage, then validate the smallest safe correction.从实际运行上下文定位首个失败阶段，再验证最小安全修正。
- Capture the exact context捕获准确上下文Record time, runtime identity, source network, driver/version, sanitized configuration, endpoint, database and error.记录时间、运行身份、来源网络、驱动/版本、脱敏配置、端点、数据库和错误。
- Resolve the effective destination解析实际目标Verify DNS answers, route, proxy and the exact the database port configured inside the selected DSN used by the process.验证 DNS 答案、路由、代理以及进程实际使用的 the database port configured inside the selected DSN。
- Test transport and TLS测试传输与 TLSMeasure socket and handshake stages separately; verify trust chain and server identity.分别测量套接字与握手阶段，验证信任链和服务器身份。
- Test identity and target scope测试身份与目标范围Validate the credentials or integrated identity used by the application account that opens the DSN, database or service selection and effective permissions.验证 the credentials or integrated identity used by the application account that opens the DSN、数据库或服务选择以及有效权限。
- Run a minimal safe operation运行最小安全操作Use a deterministic, bounded, read-only operation before representative workload testing.先运行确定性、有界、只读操作，再进行代表性工作负载测试。
- Correct, retest and monitor修正、重测与监控Change one controlled variable, preserve rollback, retest from the failing context and watch recurrence.一次只改变一个受控变量，保留回滚，从失败上下文重测并观察复发。
Prepare ODBC Data Source Administrator evidence for compatibility review为兼容性审查准备 ODBC Data Source Administrator 证据
Prepare sanitized engine and version, client runtime, driver and version, source environment, endpoint, the database port configured inside the selected DSN, database or service, TLS mode, authentication method, effective non-secret properties, exact error, first failing stage and recent changes. Never include passwords, tokens, private keys or unredacted production strings.准备脱敏后的引擎与版本、客户端运行时、驱动与版本、来源环境、端点、the database port configured inside the selected DSN、数据库或服务、TLS 模式、认证方法、有效非密钥属性、准确错误、首个失败阶段和近期变更。不要包含密码、令牌、私钥或未脱敏生产字符串。
Review ODBC Data Source Administrator compatibility审查 ODBC Data Source Administrator 兼容性
Use the InfiniSynapse DB Compatibility Checker to confirm that the selected database and ODBC driver family are plausible before creating a DSN. Then return to the matching Windows administrator, confirm bitness and DSN scope, and validate the DSN from the real service or application; the checker cannot inspect local registry views or account visibility.在创建 DSN 前，可使用 InfiniSynapse DB Compatibility Checker 确认所选数据库与 ODBC 驱动系列是否合理。随后回到位数匹配的 Windows 管理器，确认架构与 DSN 范围，并从真实服务或应用验证；该工具无法检查本机注册表视图或账户可见性。
Open DB Compatibility Checker打开 DB Compatibility CheckerODBC Data Source Administrator FAQODBC Data Source Administrator 常见问题
What does ODBC Data Source Administrator configure?ODBC Data Source Administrator 配置什么？
It is a Windows tool for viewing installed ODBC drivers and creating, changing or removing User, System and File DSNs. It stores driver-specific connection settings; it is not a database server and does not keep an application session open.它是 Windows 中用于查看已安装 ODBC 驱动，以及创建、修改或删除 User、System 和 File DSN 的工具。它保存驱动相关连接设置，但不是数据库服务器，也不会持续保持应用会话。
How do I test the correct 32-bit or 64-bit DSN?如何测试正确的 32 位或 64 位 DSN？
Match the administrator to the application architecture: System32 contains the 64-bit odbcad32.exe, while SysWOW64 contains the 32-bit version. Confirm the driver and DSN in that tool, then test again from the actual application account.管理器必须与应用架构匹配：System32 中是 64 位 odbcad32.exe，SysWOW64 中是 32 位版本。在相应工具中确认驱动和 DSN，再使用实际应用账户重新测试。
Why can Test Connection succeed while the application still fails?为什么“测试连接”成功而应用仍然失败？
The application may run with different bitness, a service identity that cannot see a User DSN, another working directory for a File DSN, or different pooling and authentication settings. Compare the process architecture, account, DSN scope and effective attributes rather than trusting the interactive test alone.应用可能采用不同位数，使用看不到 User DSN 的服务身份，File DSN 的工作目录不同，或连接池与认证设置不同。应比较进程架构、运行账户、DSN 范围和实际生效属性，不能只依赖交互式测试。
Does ODBC Data Source Administrator open a network port?ODBC Data Source Administrator 会开放网络端口吗？
No. The tool only stores configuration and invokes a selected driver when you run a test. Network exposure is controlled by the database listener, host firewall and surrounding network policy; creating a DSN does not create a server or firewall rule.不会。该工具只保存配置，并在执行测试时调用所选驱动。网络暴露由数据库监听器、主机防火墙和周边网络策略控制；创建 DSN 不会创建服务器或防火墙规则。
What can I show in an ODBC Administrator screenshot?ODBC 管理器截图中可以展示哪些内容？
A sanitized screenshot may show the administrator architecture, DSN tab, anonymized DSN name, driver name and version, and a redacted error. Hide host names when sensitive, user names, passwords, tokens, certificate-key paths and any driver dialog fields marked as secrets.脱敏截图可以展示管理器架构、DSN 选项卡、匿名化 DSN 名称、驱动名称与版本以及已遮盖错误。应隐藏敏感主机名、用户名、密码、令牌、证书密钥路径和驱动对话框中所有含密字段。
How do I change a DSN without breaking applications?如何修改 DSN 而不影响应用？
Create a separately named DSN with the intended driver and attributes instead of overwriting the active one. Test it with the service account and application architecture, switch a canary consumer, preserve the old DSN for rollback, and retire it after all scheduled jobs and pools have moved.应使用目标驱动和属性创建一个单独命名的 DSN，而不是直接覆盖现有项。先用服务账户和应用架构测试，再灰度切换一个消费者；保留旧 DSN 用于回滚，待所有计划任务和连接池迁移后再下线。