Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Use the CData JDBC Driver for Sage 50 UK in MicroStrategy
Connect to Sage 50 UK data in MicroStrategy Developer using the CData JDBC Driver for Sage 50 UK.
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData JDBC Driver for Sage 50 UK, you gain database-like access to live Sage 50 UK data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for Sage 50 UK in MicroStrategy Developer and create a Warehouse Catalog for the Sage 50 UK data.
The CData JDBC Driver offers unmatched performance for interacting with live Sage 50 UK data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Sage 50 UK, the driver pushes supported SQL operations, like filters and aggregations, directly to Sage 50 UK and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Sage 50 UK data using native MicroStrategy data types.
Connect to Sage 50 UK in MicroStrategy Developer
You can connect to Sage 50 UK in MicroStrategy Developer by adding a database instance based on the CData JDBC Driver for Sage 50 UK.* Before you begin, you will need to install the JDBC Driver for Sage 50 UK on the machine hosting the MicroStrategy Intelligence Server that your instance of MicroStrategy Developer is connected to.
- Open MicroStrategy Developer and select a Project Source.
- Navigate to Administration -> Configuration Managers -> Database Instances and right-click to add a new instance.
- Name the instance, select Generic DBMS as the database connection type, and create a new database connection.
- In the database connection wizard, name the connection and create a new Database Login name, setting the user and password for Sage 50 UK.
- On the Advanced tab for the connection wizard, set the additional connection string parameters as follows.
- Add the JDBC keyword to the connection string.
- Set MSTR_JDBC_JAR_FOLDER to the path of the directory containing the JAR file for the JDBC driver. (C:\Program Files\CData JDBC Driver for Sage 50 UK\lib\ on Windows.)
- Set DRIVER to cdata.jdbc.sage50uk.Sage50UKDriver, the driver class.
- Set URL to the JDBC URL for the Sage 50 UK driver, which contains the necessary connection properties.
Note: Only Sage 50 UK 2012 and above are supported.
The User and Password properties, under the Connection section, must be set to valid Sage 50 UK user credentials. These values will be the same used to log in to the Sage 50 UK software.
Additionally, the URL property, under the Connection section, will need to be set to the address of the company dataset desired. To obtain the address, do the following:
- If you have not already done so, open the Sage 50 UK software.
- Click Tools -> Internet Options.
- Select the SData Settings tab.
- Click the Details button next to Sage 50 Accounts. A window is displayed containing a list of company names along with the address to their corresponding datasets.
- Set the URL property to the value in the address field next to the company desired.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Sage 50 UK JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.sage50uk.jar
Fill in the connection properties and copy the connection string to the clipboard.
When you configure the JDBC URL, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
Typical additional connection string properties follow:
JDBC;MSTR_JDBC_JAR_FOLDER=PATH\TO\JAR\;DRIVER=cdata.jdbc.sage50uk.Sage50UKDriver;URL={jdbc:sage50uk:URL=http://your-server:5493/sdata/accounts50/GCRM/your-address;User=Manager;};
- Ensure that you have not selected an ODBC data source (this will trigger MicroStrategy to use the additional connection string parameters to build the database instance) and click OK.
- Click OK to close the database instance wizard.
- In the Project Source, right-click the project and open the Project configuration.
- Navigate to Database Instances, select the newly created database instance, and click OK.
- Close MicroStrategy Developer and restart the connected MicroStrategy Intelligence Server to complete the database instance creation.
With the database instance configured, you will now be able to connect to Sage 50 UK data from the Warehouse Catalog and Data Import.
Connect to Sage 50 UK Data from the Warehouse Catalog
Once you have created a database instance based on the JDBC Driver for Sage 50 UK, you can connect to data from the Warehouse Catalog.
- Select your project and click Schema -> Warehouse Catalog.
- In the Read Settings for the Catalog, click Settings and set the queries to retrieve the schema:
- To retrieve the list of tables, use the following query:
SELECT * FROM SYS_TABLES
- To retrieve the list of columns for selected tables, use the following query:
SELECT DISTINCT CatalogName NAME_SPACE, TableName TAB_NAME, ColumnName COL_NAME, DataTypeName DATA_TYPE, Length DATA_LEN, NumericPrecision DATA_PREC, NumericScale DATA_SCALE FROM SYS_TABLECOLUMNS WHERE TableName IN (#TABLE_LIST#) ORDER BY 1,2,3
- To retrieve the list of tables, use the following query:
- Select tables to be used in the project.
Using the CData JDBC Driver for Sage 50 UK in MicroStrategy, you can easily create robust visualizations and reports on Sage 50 UK data. Read our other articles on connecting to Sage 50 UK in MictroStrategy Web and connecting to Sage 50 UK in MicroStrategy Desktop for more information.
Note: Connecting using a JDBC Driver requires a 3- or 4-Tier Architecture.