Forum Discussion

Frequent Visitor

2 years ago

KQL Database - Shortcut creation failed

Hello everyone!, I want to create a Shortcut in a KQL database pointing to a Warehouse table but I'm getting errors (I am the owner of both and they are in the same Workspace). I don...

v-cboorla-msft

Microsoft Employee

2 years ago

Hi AnibalBenedetto

Thanks for using Microsoft Fabric Community.

Apologies for the inconvenience.

KQL databases don't currently support data in the Delta format. Tables in a KQL database only export to OneLake as Parquet files. Shortcuts in KQL databases that contain Delta-formatted data in the target aren't recognized as tables.

For more details refer Link

I tried creating a shortcut pointing to a Lakehouse which has csv file. Please find the screenshot for reference.

I hope this helps. Please do let us know if you have any further questions. Glad to help.

AnibalBenedetto

Frequent Visitor

2 years ago

Thanks v-cboorla-msft!

I’m confused. I have already created some shortcuts in my KQL Database pointing to Lakehouse or Warehouse tables using the wizard to do that.

In this particular case, I got an error.

I see that warehouse table which has a PK produces error in shortcut creation.

Steps to reproduce:

1- Create a Warehouse called “test_shortcut”

2- Create two tables and only one of them with primary key

CREATE TABLE [test_shortcut].[dbo].[table_without_pk]
(
   col1 int NOT NULL,
   col2 varchar(10) NOT NULL
)
GO

CREATE TABLE [test_shortcut].[dbo].[table_with_pk]
(
   col1 int NOT NULL,
   col2 varchar(10) NOT NULL
)
GO
ALTER TABLE dbo.table_with_pk ADD CONSTRAINT table_with_pk_key PRIMARY KEY NONCLUSTERED (col1, col2) NOT ENFORCED
GO

3- Create a Shortcut in KQL Database pointing to the new tables

table_without_pk -> ok

table_with_pk -> error

Thanks

v-cboorla-msft
Microsoft Employee
2 years ago
Hi AnibalBenedetto

Apologies for the inconvenience that you are facing here.

I tried to repro the same scenario from our end and initially I have faced the same error, but after deleting the KQL Database and creating a new one the issue was resolved. Please try this workaround and let me know. I have attached screenshots for reference.

I hope this helps. Please do let us know if you have any further questions. Glad to help.
- v-cboorla-msft
  Microsoft Employee
  2 years ago
  Hi AnibalBenedetto
  
  We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
  In case if you have any resolution please do share that same with the community as it can be helpful to others.
  Otherwise, will respond back with the more details and we will try to help.
  
  Thanks
  - v-cboorla-msft
    Microsoft Employee
    2 years ago
    Hi AnibalBenedetto
    
    We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
    In case if you have any resolution please do share that same with the community as it can be helpful to others.
    If you have any question relating to the current thread, please do let us know and we will try out best to help you.
    In case if you have any other question on a different issue, we request you to open a new thread.
    
    Thanks