[QODBC-Online] Accessing Multiple QuickBooks Online Entities via Linked Servers

Problem Description:

A company has multiple QuickBooks Online (QBO) entities and needs to pull data from all of them into separate SQL Server databases via Linked Servers using the QODBC driver. The challenge is configuring multiple DSNs correctly - each entity requires its own connection path, and the bitness (32-bit vs. 64-bit) of each DSN type matters critically.

Affected products: QODBC Online, SQL Server Management Studio (SSMS), QuickBooks Online
Expected outcome: Each QBO entity has a dedicated connection path (User DSN → System/Remote DSN) enabling separate Linked Servers in SSMS to pull data from each entity independently.

Symptoms:

• Multiple QBO company files need to be queried from SQL Server via Linked Servers.
• A single DSN setup works for one entity, but additional entities fail to appear in the DSN dropdown or do not connect.
• Customer is unsure whether a unique DSN pair (User + System) is needed per QBO entity.
• Confusion about licensing requirements - whether a separate QODBC Server license is needed for multi-entity access.

Cause:

Each QuickBooks Online entity requires its own dedicated DSN connection path to establish a separate Linked Server connection.

A single DSN can only point to one QBO company at a time. To access multiple entities, you must create a separate chain of DSNs for each:

1. QODBC Online Driver (32-bit) DSN - points to the specific QBO company's data stream. This can be a User DSN or a System DSN.
2. QRemote Driver DSN - points to the corresponding QODBC Online DSN. The QRemote DSN should be created as 32-bit or 64-bit depending on the bitness of the application that will use the QRemote DSN.

Critical gotcha: The QODBC Online Driver must be a 32-bit DSN. The QODBC Online DSN can be either a User DSN or a System DSN. A User DSN is visible only to the Windows user who created it and is not visible to other Windows users. A System DSN is visible to all Windows users on the machine, and those users can use the DSN to connect to the corresponding QBO company.

Environment:

Solution:

1. Create a QODBC Online Driver DSN for each QBO entity (32-bit User DSN or System DSN).
   1. Open ODBC Data Source Administrator (32-Bit): C:\Windows\SysWOW64\odbcad32.exe
   2. Create a new User DSN or System DSN using the "QODBC Online Driver for QuickBooks" driver.
   3. If the QBO connection should be visible only to a specific Windows user, create a User DSN. A User DSN is not visible to other Windows users. If the QBO connection should be visible to all Windows users on the machine, create a System DSN. A System DSN is visible to all Windows users, and they can use it to connect to the corresponding QBO company.
   4. Name it descriptively, e.g., CompanyABC, CompanyPQR, etc. - one per QBO entity.
   5. Do NOT create this in the 64-bit ODBC tool - it will not be visible to the QRemote client.
2. Create a corresponding QRemote DSN for each QODBC Online DSN.
   1. Open the ODBC Data Source Administrator that matches the bitness of the application that will use the QRemote DSN.
   2. Create a new System DSN using the "QRemote Driver" (not the QODBC Online driver).
   3. If the application is 32-bit, create the QRemote DSN using the 32-bit ODBC Data Source Administrator.
   4. If the application is 64-bit, create the QRemote DSN using the 64-bit ODBC Data Source Administrator.
   5. Create a new User DSN or System DSN using the "QRemote Driver", depending on the required user/application access.
   6. Name it descriptively, e.g., QRemoteCompanyABC, QRemoteCompanyPQR, etc.
   7. In the Remote DSN field, point to the matching User DSN name from Step 1 (e.g., QRemoteCompanyABC → / Remote DSN = CompanyABC).
   8. This MUST be a 64-bit System DSN - it will not function as a 32-bit User DSN for SQL Server.
3. Create a SQL Server Linked Server for each QRemote DSN.
   1. In SSMS, open Linked Servers → New Linked Server.
   2. Set the provider to "Microsoft OLE DB Provider for ODBC Drivers."
   3. Select the corresponding QRemote System DSN (e.g., QRemoteCompanyABC) as the data source.
   4. Repeat for each entity - one Linked Server per QRemote DSN.
4. Test connections independently. Query each Linked Server separately to verify it pulls from the correct QBO entity before setting up any automated data pipelines.

SQL Examples:

Create a linked server via T-SQL:

EXEC sp_addlinkedserver
    @server = 'OrangeRemot',
    @srvproduct = 'QODBC',
    @provider = 'MSDASQL',
    @datasrc = 'QRemoteCompanyABC';

Query across the linked server:

SELECT * FROM OrangeRemot...Invoice

Example Scenarios:

Scenario 1 - Multi-entity consolidated reporting:

A company has 7 QBO entities (each named by a color, e.g., Orange, Blue, Green). They create 7 User DSNs (QODBC Online Driver, 32-bit) and 7 System DSNs (QRemote Driver, 64-bit), one pair per entity. In SSMS they create 7 Linked Servers, each pointing to its corresponding QRemote DSN. A consolidated report queries all 7 linked servers and unions the results into a single data mart database.

Scenario 2 - Separate databases per entity:

A company needs each QBO entity's data in a separate SQL Server database for isolation. They follow the same DSN pairing pattern but direct each Linked Server to its own SQL Server database instead of a shared data mart.

Additional Notes:

• Licensing: One QODBC Online license per machine is sufficient for all entities. QODBC Online is server-edition licensed - no per-entity fee. You do NOT need a separate QODBC Server license for multi-entity access.
• The DSN pairing is strict: 32-bit User DSN → 64-bit System QRemote DSN. Mixing bitness (e.g., 64-bit to 64-bit or 32-bit to 32-bit) will cause the DSNs to not appear in the expected dropdown menus and connections to fail.
• The QODBC Online evaluation version is available for testing. After the trial, a paid subscription is required for continued use.
• Each QRemote wrapper DSN acts as a tunnel from SQL Server → ODBC → QuickBooks Online. The actual QBO authentication happens within the 32-bit User DSN; the 64-bit System DSN only forwards queries and results.

Related Articles:

QODBC and QXL for QuickBooks Online - Products, Trials, and Data Availability QODBC QBOnline Connection Key - Export/Import How to create Link Server with MS SQL 2005/2008/2012 64-bit Using QODBC Online/QRemote

Keywords: