Forum Discussion

DennesTorres's avatar
DennesTorres
Power Participant
3 years ago
Solved

Schema on lakehouse sql endpoint

Hi, A SQL Endpoint in a lake house allow us to create schemas. The tables from the lakehouse are automatically in the DBO schema, but we can create new schemas. Is there anyway to include the t...
data engineering
  • puneetvijwani's avatar
    puneetvijwani
    3 years ago

    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 

DennesTorres's avatar
DennesTorres
Power Participant
2 years ago

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

yllsuarez76's avatar
yllsuarez76
Microsoft Employee
2 years ago

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]