Forum Discussion
Schema on lakehouse sql endpoint
DennesTorres It seems to be same limitations that we use to have in Synpase analytics -- lake databases
Reference Text:Custom SQL objects in lake databases
Lake databases allow creation of custom T-SQL objects, such as schemas, procedures, views, and the inline table-value functions (iTVFs). In order to create custom SQL objects, you MUST create a schema where you will place the objects. Custom SQL objects cannot be placed in dbo schema because it is reserved for the lake tables that are defined in Spark, database designer, or Dataverse.
Link :
https://learn.microsoft.com/en-us/azure/synapse-analytics/metadata/database
Schemas are available at the SQL endpoint. I transfered a table from dbo to a custom schema, which sounds like an extended property. Is there a way (or will be) to define the schema while creating the table in fabric? That's benfecial for permissions granted via SQL at schema level instead of each table.
Hi,
Could you provide more details about how you managed to transfer a table to a different schema and it you still could access this table on a notebook?
Kind Regards,
Denned
you can move a table from schema while using the SQL Point and querying via tsql (I did in SSMS). This looks to be nothing more than an extended property to the underlying delta table.
However, from the notebook you still querying using spark which doesnt support schema, as mentioned by the support team.
alter schema conformed transfer [dbo].[sales_internal]
select count(*) from [conformed].[sales_internal]