Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Am not able to drop any table from Microsoft SQL Analytics End point -

Hi Friends,   am trying to drop the tables from SQL analytics end point.  getting the below error.   The external policy action 'Microsoft.Sql/Sqlservers/Databases/Schemas/Tables/Drop' was denie...
data engineering
  • v-sgandrathi's avatar
    v-sgandrathi
    1 year ago

    HI Anonymous,

     

    Thankyou 46 for the accurate and helpful response! You've clearly explained that DROP TABLE is not supported through the SQL Analytics Endpoint and pointed out the correct alternatives via Lakehouse or Notebooks.

     

    Just to add a few more helpful points for your idea:
    These endpoints are primarily built for querying and reporting. Operations like SELECT, JOIN, and AGGREGATIONS work fine, but DDL operations (e.g., DROP, CREATE, ALTER TABLE) are not supported from this layer.

     

    Tables exposed in the endpoint are stored in the Lakehouse as Delta Lake tables (in OneLake).
    So, any structural changes must be performed at the Lakehouse level, either through the Lakehouse UI (Explorer) or using PySpark in a Fabric Notebook:
    spark.sql("DROP TABLE IF EXISTS your_table_name")

    Please Accept as solution if this meets your needs and a Kudos would be appreciated.

     

    Thank you.

     

Srisakthi's avatar
Srisakthi
Super User
1 year ago

Hi Anonymous ,

 

Are you using your own personal workspace?

1. If you are using workspace assigned by someone reach out to them for access, they might have applied restrictions.

2. If you are shared with particular Lakehouse/warehouse , they might have applied restrictions. 

So reach out to the person who has give access.

 

Regards,

Srisakthi

 

Anonymous's avatar
Anonymous
Not applicable
1 year ago

Thanks Srisakthi for the reply,

 

I'm the admin here, but I'm still unable to drop the table.

Also, I’ve noticed that a few tables are visible from the SQL Analytics endpoint, but not from the Lakehouse. I'm not sure why that’s happening.

We dropped a few tables using PySpark code from the Lakehouse. However, I can still see them in the SQL Analytics endpoint, and querying them throws an error.

Does this mean the actual data was dropped, but the metadata still exists? I'm a bit confused and would appreciate some clarification.

 

Thanks

Ramana