Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi all,
I'm currently working for a client trying to figure out if a switch from their current BI tool to PowerBI is relevant. Their analytics database runs on-premise with HP Vertica.
I understand that a build-in connector in PBI is not yet on the table for the dev team. On the other end, HP provides a step-by-step method to connect, which is what I will try next.
Is anyone knowledgeable on the matter ? Specifically :
Those would be my main concerns at this stage. I've had a first few very interesting talks with people a few days ago during a big data convention, but i'd like to know what's the word on this.
Best,
Antoine
Solved! Go to Solution.
Hi @AntoineCh,
Firstly, for the time that it takes to create DSN to HP Vertica, I would recommend you contact Vertica support. Once you create DSN, it would simple to connect to the DSN from Power BI Desktop. However, it depends on the amount of your data that how long it will take to completely load the data from DSN to Desktop. And do you want to mass install Power BI Desktop across many computers? If that is the case, you can consider to deploy Power BI Desktop via SCCM, for more details, please review this blog: https://blogs.msdn.microsoft.com/samlester/2016/09/30/installing-power-bi-desktop-through-sccm/ .
Secondly, it is stable, it will not affect the available features of Power BI Desktop after you connect to DSN.
Thirdly, after you import data from Vertica to Power BI Desktop, all the data are stored in Power BI Desktop file, and calculations are based on the imported data. Once you publish Power BI Desktop file to Power BI Service, Power BI manages the storage of data and metadata using Azure BLOB and Azure SQL Database.
In addition, if you have a large amount of data to import to Power BI Desktop, it may take you some time to load data to Desktop, from Power BI side, to improve performance, import data by entering SQL query to include the tables you want. And also contact Vertica support to improve Vertica ODBC performance.
Thanks,
Lydia Zhang
Hi @AntoineCh,
Firstly, for the time that it takes to create DSN to HP Vertica, I would recommend you contact Vertica support. Once you create DSN, it would simple to connect to the DSN from Power BI Desktop. However, it depends on the amount of your data that how long it will take to completely load the data from DSN to Desktop. And do you want to mass install Power BI Desktop across many computers? If that is the case, you can consider to deploy Power BI Desktop via SCCM, for more details, please review this blog: https://blogs.msdn.microsoft.com/samlester/2016/09/30/installing-power-bi-desktop-through-sccm/ .
Secondly, it is stable, it will not affect the available features of Power BI Desktop after you connect to DSN.
Thirdly, after you import data from Vertica to Power BI Desktop, all the data are stored in Power BI Desktop file, and calculations are based on the imported data. Once you publish Power BI Desktop file to Power BI Service, Power BI manages the storage of data and metadata using Azure BLOB and Azure SQL Database.
In addition, if you have a large amount of data to import to Power BI Desktop, it may take you some time to load data to Desktop, from Power BI side, to improve performance, import data by entering SQL query to include the tables you want. And also contact Vertica support to improve Vertica ODBC performance.
Thanks,
Lydia Zhang
Thanks Lydia, that's very helpful. I may have other questions later, but this covers it for now !
The volume should be manageable (couple Go at best), especially if pre-filtered on the appropriate time-frame.
Best,
Antoine
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.