|
[QODBC-Online] How to create Link Server with MS SQL 2005/2008/2012 32-bit Using QODBC Online/QRemote
Posted by Jack - QODBC Support on 19 August 2015 02:24 PM
|
|
|
How to create a Link Server with MS SQL 2005/2008/2012 32-bit Using QODBC Online/QRemote For 64-bit Refer: How to create Link Server with MS SQL 2005/2008/2012 64-bit Using QODBC Online/QRemote Start your "SQL Server Management Studio" Login to your SQL Server. On the left-hand side panel, you will find the Server, Right Click on the "SQL Server" and Select Properties.
Please Verify that your SQL Server is 32-bit.
64 and 32-bit words are kept separate in the Microsoft Windows Operating System. QuickBooks 2021 and older versions are 32-bit applications, so a 32-bit ODBC driver is required to communicate with it. All versions of QuickBooks from 2002 through 2021 are built on a 32-bit architecture. In contrast, many modern applications—such as Microsoft Excel, Microsoft Access, and Microsoft SQL Server are commonly deployed in 64-bit environments. For users running QuickBooks 2021 or earlier, this architectural difference creates a compatibility challenge: 64-bit applications cannot directly communicate with 32-bit drivers. To address this limitation, we provide QRemote. For the users of QuickBooks 2021 or eariler, since a 64-Bit application cannot talk to a 32-bit driver, we have to do a bit of magic to get the worlds to connect, and we call it QRemote. QRemote works as a bridge (only for QuickBooks 2022 or lower) between 64-Bit Applications and the 32-Bit QODBC Driver by communicating data calls between the two worlds using TCP/IP protocol. QRemote allows 64-Bit Web Servers and 64-Bit applications to talk to QuickBooks Live for the first time via the QODBC Driver. For users running QuickBooks 2022 and later, this additional layer is no longer required. These versions of QuickBooks are native 64-bit applications, and the latest release of the QODBC Driver includes a fully compatible 64-bit driver. As a result, 64-bit applications can connect directly to QuickBooks (using the DSN "QuickBooks Data" ) without the need for QRemote. QRemote Server is designed to enable connectivity and compatibility across different environments and application types. Its primary use cases include:
QRemote has two components: "QRemote Client Driver for QODBC Online" and "QRemote Server for QODBC Online." QRemote Client Driver: Allows service-based applications & 64-bit applications to connect to the QRemote Server and sends the Request to the QRemote Server for Processing. QRemote Server: Processes requested instruction from QRemote Client to QuickBooks using QODBC DSN Driver.
Start "QRemote Server for QODBC Online" from the start menu. ( If QRemoteServer is not running )
Double-click the QRemote Server icon from the system tray
QRemote Server Main screen shows the IP address and Port allowing the QRemote Client to connect.
Note the IP address and Port number listed on the QRemote Server "Event Logs window."Create a new DSN entry/or configure the existing oneNavigate to Start Menu, QODBC Drivers for Use with QuickBooks Online, and click Configure QODBC Online Data Source
"QuickBooks Online Data QRemote" is the default DSN created when installing QODBC.
Configure the DSN and provide the IP address and Port as listed under "QRemote Server."
Under the QRemote for QuickBooks Online– Client DSN configuration screen, Please fill in the following information
(Keep Encryption Key empty/blank. In case you want to use encrypted data transfer between QRemote client and QRemoteServer, You can configure your encryption key on QRemoteServer and use the same on QRemote Client DSN)
Run MS SQL 2005 Dev / 2008 / 2012 (32-bit) and login inRun SQL Server Management Studio. You'd better choose SQL Server Authentication and input the correct name and password.
Under SQL Server Management Studio, Navigate to "Server Objects" -> Linked Server -> New Linked Server.
OR
Provide the "New Linked Server" information
On Clicking OK, it will start establishing a connection to QuickBooks Online, The Linked server will be shown under the "Linked Server" Category.
Configure MSDASQL (Microsoft OLE DB Provider for ODBC Drivers)
The dynamic parameter should be checked to allow parameter queries. Level zero only should be limited to enable four-part naming to work. Allow InProcess should be restricted to help performance. Non-transacted updates should be reviewed if you want to be able to update QuickBooks data. Index as access path should be checked to help performance. Disallow Adhoc accesses should be unchecked to allow OPENQUERY to function.
QODBC Online/QRemote is ready to use with SQL Server/Linked Server Execute below query Select * from Online…Company
On each query, QRemote Server Logs the events. If you are facing any issues or delays in response, please refer QRemote Server Event Logs for details on which stage it's taking more time.
Another Test Select * from Online…Account
On each query, QRemote Server Logs the events. If you are facing any issues or delays in response, please refer QRemote Server Event Logs for details on which stage is taking more time.
Keywords: SQL Server 2008 Management Studio, SQL Server 2016 Management Studio, SQL Server 2012 Management Studio, SQL Server Management Studio, SSMS, QuickBooks Online, QBO, online 32-bit | |
|
|


















