The database cannot be located; the capacity and/or the database do not exist or are in the wrong

[LSPrab]

HI

I need some help

I am getting this error 

cannot be located; the capacity and/or the database do not exist or are in the wrong state.

Recently i moved the workspace to difference fabric capacity since then i am getting this error in my data warehouse, when i try to run a query

Regards

Prab

[LSPrab]

Hi  @v-achippa @nilendraFabric 

I am getting this error while i am trying to do DDL / DML (Create / Drop / Update), but there is no error when i do the select statement.

Regards

Prab

[v-achippa · Accepted solution]

Hi @LSPrab,

Since you can run SELECT queries but not DDL/DML commands, the issue is likely related to workspace permissions or data warehouse state.

• In the Microsoft Fabric Admin Portal verify that the data warehouse is active and not in a read-only or migrating state. If it is still migrating, wait for the process to complete.
• Ensure you have the required permissions Admin or Contributor, if you have Viewer or Read-Only access, DDL/DML operations won’t work.
• In addition to this try restarting the data warehouse service, if still not working, try moving the workspace back to the old capacity, wait for complete synchronization, and then reassign it to the new capacity.

Let me know if any of these steps help resolve the issue or if you are seeing any specific error messages during DDL/DML execution.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @LSPrab,

Thank you for reaching out to Microsoft Fabric Community.

After moving the workspace to a different Fabric capacity, the data warehouse may not be correctly linked to the new capacity, or the database is in an inactive/migrating state.

• Check if the database is assigned to the new capacity, go to Fabric Admin Portal --> Capacities --> Select the new capacity. Check if the workspace and data warehouse are listed under this capacity. If missing, move the workspace back to the old capacity and retry moving it again.
• After moving the workspace, permissions may not have transferred correctly. Verify if you have Admin or Contributor access.
• If the issue persists, move the workspace back to the old capacity, wait for full migration, and then reassign it.

Let me know if this helps to resolve the issue.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa

[LSPrab]

Hi @v-achippa 

Thanks for your support.  The problem is resolved, it is due to permission issues i faced the problem.

Regards

Prab

[nilendraFabric]

Hello @LSPrab 

Could you please check if you can connect to dw using ssms

if yes 

run this 

EXEC [XMLA_Endpoint_URL].ProcessDatabase Full