Have a look at this and it should help you. RLS is only supported on a Lakehouse through the SQL Analytics Endpoint. learn.microsoft.com/en-us/fabric/data-warehouse/tutorial-row-level-security

Thanks. If your semantic model is based on a star schema, you can filter your fact tables and slice based in your dimensions. So yes the relationships are key in the scenario you described.

We recently launched a new Oracle connector. You can use this connector in addition to an on-premise gateway to access oracle on prem data. support.fabric.microsoft.com/en-ca/blog/announcing-new-data-factory-connectors-released-in-may-2024?ft=All

I appreciate it!!! 💪🏽

at 5:31 in video , can you tell what is there in "more"

Yes SAP data can be accessed through an on-prem gateway. Check out this link for more details. blog.fabric.microsoft.com/en-us/blog/integrate-your-sap-data-into-microsoft-fabric/

Just like we provided the primary instance with access to the key vault, we need to provide any secondary instances with that same access to the key vault.

Glad it helped!

Thank you! Please like and share!

Thank you!!

Increasing a service tier can vary depending on if the current underlying VM has the resources to allocate to your instance, or if it needs to be moved to a different instance. However the downtime is minimal as some of this work involved with potentially moving to a new VM happens in the background while your current instance continues to run, and then we will do, in essence a DNS change, at the end. Moving databases into a new elastic pool is a relatively seamless experience. Within elastic pools, your can limit the amount a vCores that a database can consume from that pool helping to put guardrails around noisy neighbors.

@@DataBar my main concern is kicking out the noisy neighbour from the elastic pool to a dedicated azure SQL instance

Understood. That’s why it’s important to set up good monitoring and alerting procedures so you can identify things like that and take appropriate action!

From the Lakehouse you are either using the SQL Endpoint to access data with T-SQL in which the row level security will apply, or you are accessing the data via Spark and hitting the underlying delta parquet files and RLS will not apply in that scenario.

That was at the time of this recording. nvarchar should be supported now as long as it’s not nvarchar(max) as LOB data over 1MB is unsupported.

One gateway can be used to connect to multiple on-prem databases.

Thank you. Glad it was helpful!

Any user with Admin, Contributor, or Member permissions on the workspace will be able to see unmasked data. If you need it to be masked for a user, either give the Viewer workspace role, or grant more granular SQL permissions using the GRANT statement.

I am not aware of a way to do this via notebooks. The ideal solution would be to use Fabric Mirroring to mirror your SQL Server database into OneLake. Currently the mirroring feature is in private preview and only supports Azure SQL DB, CosmosDB, and Snowflake, but sql server will be coming soon.

Will do

No each user does not need to install their own gateway. The admin of the gateway, usually the person that installs it, can grant additional users permission to use the gateway. See the below doc for more info: learn.microsoft.com/en-us/data-integration/gateway/manage-security-roles

No each user does not need to install their own gateway. The admin of the gateway, usually the person that installs it, can grant additional users permission to use the gateway. See the below doc for more info: learn.microsoft.com/en-us/data-integration/gateway/manage-security-roles

Thanks! Glad it helped!!!

Thank you!

Glad it was helpful!

Thank you! Glad it was able to help!!

On prem gateways are used to access data on-prem and are currently only supported within Gen2 Dataflows.

Glad this was able to help you!!!

I would need to review it to really understand what’s going on. I recommend you open a support case for assistance.

Thank you! I appreciate you watching!!

I agree, I need hands on as well

Best of luck!

Thank you!!!

Thank you for watching sir! I appreciate it!!!

I will keep watching and learning. As I have questions I will reach out Keep doing what you do! I greatly appreciate it! 😊 ❤

Thank you! I appreciate you!

Thanks for watching!!

Indexes help with data retrieval, but they slow down data writes. In a real-time replication scenario you have lots of write activity taking place. Each time you write new data, any indexes you have will need to be updated, thus impacting performance.

Azure SQL only allows one replica to serve both read and write workloads so load balancing isn’t really a concept here. You can redirect read-only workloads to a secondary replica. Does this answer your question?

Glad it helped!

Glad it helped!

It just depends on your use case. If your main goal is offloading read-only workloads then using the included replica of the BC tier meets that purpose. The replica is there for high availability purposes and to ensure Microsoft can maintain its SLA’s. But if you are looking for a solution for disaster recover, then, as you stated, auto-failover groups would be the best solution for that use case.

Glad it was helpful!

Glad it was helpful!

MacOS is my host OS. I then have an RDP connection to a Windows 11 VM. At the 1:50 mark I am running the SSMS app connected to a SQL Server 2022 instance hosted on Windows Server 2022.

We don’t have a date to announce publicly yet but other providers are in the works.

Thanks for watching and glad I could help you!!

It’s kind of hard to troubleshoot without actually understanding and looking into your environment. Have a look at this and perhaps it can help you. learn.microsoft.com/en-us/azure/synapse-analytics/synapse-link/troubleshoot/

We’re you able to resolve this issue?

Yes the flow should still be the same for restoring to your local pc. You still must use SQL 2022 and your must go through the process of ensuring your instance can access the CMK stored within the key vault.

​@@DataBar thanks. I think there are two scenarios here. The first one is to restore the database to our local location. If I used the Azure default TDE key, I can not do the backup with Azure Blob, because I don't have the master key password. So If we want to back up to the Azure Blob, we should use the custom key. And the custom key should use Azure Key Vault. And then we can restore the database from the Azure blob. The second one is just to ensure that the data is secure. The Azure default enabled the TDE, So we don't need to do anything. I hope I understand correctly, LOL

Correct, anytime you want to move a backup outside of Azure you have to use a customer managed keys, and SQL Server 2022 is the only version they currently supports restoring backups from Azure SQL MI. Backups created using a service managed key can only be restored within Azure.

Thank you for watching!

Thank you sir. I appreciate that! More content coming soon!!!

Thanks for the feedback. I may revisit this topic in a future video.