Forum Discussion
Permission denied for CREATE TABLE statement
Hi ToddChitt - Sorry to hear you are having problems!
I've run into a similar situation before myself. For me it happens when I am connecting to the Analytics Endpoint instead of the SQL Endpoint.
For copy table the steps should look a lot like this document: Load data with data pipelines into SQL database - Microsoft Fabric | Microsoft Learn. The key thing is to pick your SQL database endpoint from the OneLake Data Hub.
For the SSMS connection, at the top of the SQL Editor, you should see an "Open In" menu.
Click on SQL Server Management Studio and copy the server and database name into the connection dialog in SSMS. (database name is on the Connection Properties tab)
Let's make sure you are getting connected to the right place, then we can dig into the double schemas. We like schemas and think everyone should use them but once seems like enough.
Hello dlevy and thank you for the information. I have created a support case with Microsoft, Request Number: 2412060040007766.
Regarding the GUID appended to the Database Name behind the SQL Endpoint:
It's not there for the Analytic Endpoint. Did those guys figure out how to do a two-part unique key for a database (Server and database)? Seems that has to be unique. In fact, I ran into it yesterday trying to test out the Copy Job (Preview):
Solving that would go a long way to helping it get accepted by the consumers. Nobody likes when someone else messes with their settings.
By the way, I was happy to see that the Collation setting of the database was "...CI..." (Case Insensitive).
Hi ToddChitt - For things like that, https://ideas.fabric.microsoft.com/ is going to be a better bet. Support doesn't have a lot of options for something that is working the way the engineering spec says it should. Feel free to upvote and add entries to the ideas site with anything you think would make the product work better for you. We really appreciate your help improving the product!