I have a requirement where data is encrypted using Privacera and stored into Azure SQL server tables.
I need to show this data from Azure SQL server in Power BI report. In Power BI I need to decrypt the data while showing in the report.
Is there any way in Power BI to decrypt the encrypted data?
Related
My company plans to copy all data from on-premise SQL Services Analysis Services (2017 tabular) to Azure Analysis Services on a periodic basis. We want to do this at least once a day, and then use the Azure Analysis Services version for Power BI reporting only. The idea is to reduce load on the on-premise cube, and to improve response in Power BI.
Is this a recommended design for reporting?
What are the methods available for the periodic copy of data (and pros and cons for each)?
In addition to Nandan’s approach, you could continue to refresh the model on premises, then backup and restore to Azure Analysis Services. I shared a PowerShell script which automates this operation.
can you tell us what is the data source for the on prem SSAS cube ?
In case it a SQL server, rather than syncing data from SSAS to AAS, you can directly refresh the AAS with on prem SQL server as the source via on prem gateway.
And in case if the cube is only used for reporting(powerbi), then having AAS is enough rather than maintaining SSAS and AAS.
From SQL Server 2019, how do I connect to SQL Server Analysis Server (Tabular Model) / Azure Analysis Service using CREATE EXTERNAL DATA SOURCE command?
I would like to connect to it using Polybase and extract data from the Tabular data model.
I installed the latest drivers for the Tabular model:
https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=asallproducts-allversions
Thanks,
grajee
I want to setup the data encryption on SQL Server 2008 R2 Standard edition at database level. I already tried TDE but it is not available in Standard edition.
What can be the most efficient way of data encryption at database level in SQL Server 2008 R2 Standard edition?
With Standard Edition, there are several things you can do to encrypt data
EFS is a windows feature that can be used to encrypt the contents of files or folders using a certificate installed on the server. Be sure to test this on a non production system before impelementing and that the certificate is safely backed up.
Column level encryption can be implemented to protect the data
You can use Bitlocker to encrypt drives on your server to prevent low level attacks or data theft.
With 2008 R2 Enterprise, there are some additional methods to address encryption
TDE is one you already mentioned, so I'm sure you are familiar with this option
EKM stands for Extensible Key Management system and it can be an expansion card or separate hardware with a high speed interface that offloads the storage of keys and encryption and decryption functions. It can be managed by a separate team that the DBA for effective separation of duties.
So for the past couple of days, I've been trying to establish a connection between SAP BW and Microsoft PowerBI. I'm establishing the connection between the two systems using the driver (HDBODBC) provided in the HANA Suit.
Using the connection provided in PowerBI I was able to establish a connection between the two systems. The user used to create the connection was a DB level user created by our BASIS consultant. This use has sa access to the DB.
I want to stress on the fact that application level users couldn't connect to this so we had to create a DB level user and connect tot he DB Server of HANA instead of the Application Server of SAP BW.
The problem occurs when I try to browse and view data available in HANA queries, Composite Providers and Cubes.
I want to know if there is a configuration/authorization that has to be assigned in the application level to rectify this error?
Thanks in Advance
How does the ODBC driver transfer data between an application to MSSQL Server 2005?
Is it serialized?
I'm trying to send data between SQL Server 2005 & MS Dynamics 4.0 but I suspect my data is altered by the ODBC driver in between.
Its sent as a wide-character string to SQL server -- i.e., a SQL query batch. No transformation needs to take place. The return data is structured in a protocol called TDS.
I believe if you are using the ASCII functions of the ODBC native client it gets upscalled to wide-character.
Look at the date formats on the 2 servers, you may have issues with localisation/regional settings