Wednesday, February 11, 2015

PowerBI Preview reporting from SQL Anywhere 16 - Part 1

This post describes the steps you may take to connect to SQL Anywhere 16's 'demo' server. Previously you have seen that it is possible to create a linked server successfully using the drivers provided with SQL Anywhere 16.

In a future article here are on my other blog,  you will learn how to use PowerPivot to connect to SQL Anywhere 16.

Here are some screen shots of PowerBI  connecting  to SQL Anywhere.
Before you start connecting make sure you have started the SqlAnywhere 16 server successfully and also Sybase Central to verify that you can access the objects.

If you have followed my earlier article here:

You will notice that PowerBI can obtain its data from a Sybase Database as(I am assuming that SQL Anywhere 16 is a Sybase database) shown

Choose Sybase Database and click Connect button. The following screen will be displayed

I have superposed the server start up screen on the PowerBI's screen. The server name is demo16. This server takes the pair dba/sql as username and password for connection, a database authentication.

When I complete the database name 'demo' and click Ok on the PowerBI's Sybase Database page, the following will be displayed:

I enter the authentication information (dba/sql) and click Connect, the following will be displayed

Looks like the program is looking for an IP Address.  Since the server is running on the local computer the IP address should be the same as the computer's IP address. Also from Sybase Central 16 you find the following:


Every connection turns up in a Query in PowerBI and you can delete the query to connect to a new connection. Following the above reasoning the following connection was tried:


After clicking OK the following was displayed.

However trying to connect produces the following:


It appears that there is a connectivity problem via PowerBI where as ODBC Ole DB seems to work as well as ODBC drivers. The PowerBI program certainly needs enhancements in terms of allowing ODBC and OLE DB drivers in addition to the vendor products.  Also the interactive screens should provide a gateway for a solution rather than a hard stop.

I am sure these will improve in the final version. In the mean time if I find a work around you may find it on this blog should you revisit.

No comments: Protection Status