See also Sage 300 Technical Details
Connecting to Sage 300 MS SQL Server Database
DataSelf has been working and optimizing the Sage 300 MS SQL Server data extraction since 2005:
If you haven’t installed ETL+ yet: ETL+ Deployment Instructions.
Login to ETL+ (help here).
On the ETL main page,
right-click Sage 300on the left panel →
If an ODBC Data Sources page pops up, click the
Change Data Sourcewrench icon →
MS SQL Server.
Microsoft SQL Serverpage:
Aliasbox will be automatically populated, but you can customize it.
Server name: the MS SQL Server instance name or IP address.
Authentication: select the correct one and its credentials if applicable. Read-only rights required.
Database name: The name of the SQL database from your source system.
Refreshicon on the right to load the list of database names.
dropdown listand select the correct one.
You’ll get back to the ETL page and see tables under the Sage 300 source on the left panel.
Testing a Table Load
Right-click a table on ETL main page’s center panel →
Failure? It’s likely that the prior step wasn’t properly configured. Go back and review it.
Logicon (top right) to view data load results. Log page help here.
Schedule the Data Load
On the ETL main page, click
Refresh Batch(top right icon on the center panel).
The Refresh Batch page (help here) usually comes pre-configured to your source system(s).
Overview this page’s configuration. On the right panel, feel free to uncheck tables and Tableau extracts that don’t apply to your reporting needs.
Optional: Run a Refresh Batch now: click the
Refresh Batch Now(play icon) on the left panel.
To schedule the data load:
WTS Settings-> enter the WTS parameters →
This step might require you to run ETL+ app as “Run as administrator” in Windows.
Level 1 Testing
The Level 1 Testing checks if the data extraction process finished successfully and row count per extracted table matches with Sage 300’s table row counts.
ETL+ must have already loaded your data manually or scheduled.
Login to ETL+ (help here).
On the ETL main page, click the top-right
Logicon. Log page help here.
Scroll down on the log page and double-check that no table load failed, and the row count matches with the Sage 300 tables. Following is an example highlighting two tables and their loaded row count.
Failed to load tables:
Check that the user assigned to DataSelf has reading rights to that particular data set.
Backfrom the Log page, on the ETL main page, select the failing table on the center panel, check that its SQL Statement on the right panel has correct information.
Tables with record count different than in Sage 300:
It might be just that new records have been populated in Sage 300 since the DataSelf data load. Reload the data. Click
Backfrom the Log page, on the ETL main page, select the table with incorrect row cound on the center panel,
right-clickthe table on the center panel again ->
Load Now. This might take a while if the table has a large data set.
The user assigned to DataSelf might have access to limited data sets, such as only data from one Division. Check the user’s security credentials.