> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/resources/faq/powertable-general-faq.md). # PowerTable general FAQ This FAQ answers common questions and clarifications about working with PowerTable. It covers workspace permissions, SQL database setup, and PowerTable configuration. Feature-specific FAQs are covered in the relevant sections and the following article: * [Create PowerTable Sheets FAQ](/documentation/plan/powertable-sheets/how-tos/create-a-table-app/create-powertable-sheets-faq.md) ### What permissions do I need in the workspace to create the Fabric SQL database and the Plan item? You need at least the **Contributor** role in the Fabric workspace to create a Fabric Plan item and a Fabric SQL database. ### Why do I create a Fabric SQL database before creating the Plan item? Unlike Planning and Intelligence sheets, PowerTable sheets connect directly to a Fabric SQL database instead of a semantic model. PowerTable reads data from and writes data back to the Fabric SQL database. If you start with a CSV or Excel file, you must first import the data into a Fabric SQL database before you can use it in PowerTable. For this reason, you create the Fabric SQL database first. ### Why do I see two items with the same name in the workspace after creating the Fabric SQL database? Creating a Fabric SQL database also creates a companion SQL analytics endpoint with the same name. This behavior is expected. PowerTable connects directly to the Fabric SQL database, so you don't need to configure or use the SQL analytics endpoint when working through the PowerTable exercises. ### Do the names I choose for the Fabric SQL database and the Plan item matter? * The **Fabric SQL database** name matters because you select it in the **Select Fabric SQL Connection** dialog each time you create a PowerTable sheet. * The **Plan item** name is only a label. If you use different names than those shown in the documentation, use those names consistently throughout the remaining steps. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fabricplan.com/resources/faq/powertable-general-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.