Hi @Jatinder Luthra
Hey, we ran into the same problem! We were trying to read from a specific database (catalogue) in Databricks, but kept getting this annoying 'Table not found' error. Turns out, the Azure Databricks Delta Lake Dataset was trying to pull the table from the hive_metastore, instead of the database (catalogue) we actually defined.
I found a little workaround. If you leave the database and table properties in the Azure Databricks Delta Lake Dataset blank, and then use the linked service in a copy activity to define the query, you can pull the data from a different catalogue than the hive_metastore.
Hope this gets your problem sorted!