Overview
There are two possible types of QQube provisioning in a hosting environment.
- QQube Single-User version
- QQube Multi-User version
Each type refers to the number of users that access the QQube database to run reports, and not related to the number of QuickBooks users.
You procure the QQube Single-User version for a customer when:
- There is only one person licensed to run QuickBooks and that person is the only individual who will run reports and analytics against the QQube database.
- This user can synch multiple QuickBooks files but will not be able to take advantage of the scheduler. The user will have to login to the server and manually perform the synch.
You procure the QQube Multi-User version for a customer when:
- There are multiple people remotely logging in to use QuickBooks.
- There is one or more person(s) who will run reports and analytics against the QQube database.
- This is the best option for synching multiple files under a dedicated synch server user.
QQube Single-User Version
There is only one type of user in this scenario.
- Combines available operations under one regular user login for both the Dedicated Super User and the Regular User.
- No server scripts for auto-login necessary unless requested by the customer.
QQube Multi-User Version
There are three types of users in this scenario
1. QQUBE DEDICATED SYNCH USER
This is where the QQube database server and synchronizer mechanism are installed, and where QQube will talk directly to QuickBooks using a client interface (Intuit does not give developers direct access to the database - so the client version of QuickBooks must be installed under this dedicated user).
- Install with administrative permissions, and then revert to regular user permissions.
- User is always logged in - timeout set to never.
- Create a script to auto re-start the always logged in user when server reboots occur.
- The QQube Synchronizer is available in the start menu, and in the startup folder.
The following operations are performed under this user and can be permitted without elevated permissions.
- >Get Up and Running
- Understanding The Synch Process
- Synch Issues and Error Codes (QB Desktop)
- >Add or Remove a QuicBooks File
NOTE: Reports should never be created or run under this user. It is only for the synch process.
2. QQUBE REGULAR USER
This fits the description for anybody who creates or runs reports and visualizations against the QQube database running under the QQube Dedicated Synch User. The number of users per multi-user license (5,10) refers to the number of concurrent connections to the QQube Database.
- Regular User:
- Login under their normal account
- Use auto installed DSN’s to create/run reports against the QQube database - no connection strings necessary
- Access to the QQube Configuration Tool - which will be naturally limited, to do the following:
- Run a Manual Synch
- View the Synch Logs
- Clear QQube data and/or reload from scratch
- Use built-in examples
- Use Excel Add-In
- Access to install .vsto (Excel Add-In) which then becomes available on Excel ribbon
3. QQUBE SUPER USER
Designated "Super User" can use RDP to login to the Dedicated Synch User and perform the operations listed under the dedicated synch user in [1] above.
NOTE: Some providers currently hosting QQube, do not allow these functions to be handled by a designated Super User, and are instead handled by the hosting support staff.
- Installation
- Upgrades
- Licensing and Activation
- Stopping/Starting Database
- Change Engine Name
- Change Directory where the QQube Database is stored
Available Examples
Ideally, the following applications that work out-of-the-box with QQube - over 250 pre-built examples - will be installed according to the path that was chosen during the install.
- Excel (and the included Excel Add-In)
- Excel PowerPivot
- Microsoft Access
- Microsoft Power BI
- Crystal Reports (Sometimes a Reader will suffice if somebody else builds the reports)
- Tableau
Additional Information
Overview of QQube Implementation
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article