vscode-cosmosdb icon indicating copy to clipboard operation
vscode-cosmosdb copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

Fail to create a collection to the attached Core(SQL) server which created using the "Serverless" capacity model

Open v-mengwe opened this issue 3 years ago • 4 comments

OS: Win10 Build Version: 20210923.1 Regression: Not a regression

Repro Steps:

  1. Create a Core(SQL) server with "Serverless" capacity model -> Right click the Core(SQL) server -> Select "Copy Connection String".
  2. Click "Attach Database Axccount..." icon -> Paste the copied connection string.
  3. Create a collection to the attached Core(SQL) server.
  4. Check whether succeed to create a collection to the attached Core(SQL) server.

Expect: Succeed to create a collection to the attached Core(SQL) server.

Actual: Fail to create a collection to the attached Core(SQL) server. image

More Info: Create a collection to the Core(SQL) server -> Expand the attached Core(SQL) server -> There is a collection and can create a document for it successfully.

v-mengwe avatar Sep 23 '21 09:09 v-mengwe

Attached Accounts scenario for Azure is not a typical scenario as the database account is already available under the subscription tree. I don't see a value is fixing this issue as a priority. Is there a use case I might be missing?

neelip avatar Sep 23 '21 18:09 neelip

This issue does't reproduce for the attached Mongo DB server which created using the "Serverless" capacity model or the attached Core(SQL) server which created using the "Provisioned Throughput" capacity model. It would be better to keep the attached Core(SQL) server consistent with other servers. From the user's point of view, creating a collection is a basic function, so it would be better if the collection can be created successfully.

v-mengwe avatar Sep 24 '21 06:09 v-mengwe

Verified on the latest build 20211026.1, the error also reproduces for the attached Gremlin account which created using the "Serverless" capacity model.

v-mengwe avatar Oct 28 '21 10:10 v-mengwe

This error is occurring because when create a collection with an attached serverless SQL(Core) account, we don't stifle the prompt for throughput like we do with the remote experience.

Entering a value in throughput is what is causing the error to occur. The workaround is to just type some bogus value in the prompt (it's not being validated, probably another bug we could file 😅)

nturinski avatar Aug 18 '22 22:08 nturinski