Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint

[Daria Aleksich]

 I have Cloud SQL instance(16 vCPUs, Memory 128 GB, SSD storage 300 GB). Db size 110GB.

When I execute a complex query from the cloud windows VM using SQL Server Management Studio(this vm is in the same VPC as SQL Server), it always takes on average 35s. When I execute the same query from the same machine using DBeaver it takes 1.5s on average. Tried connecting with SQL Proxy, nothing changed.

Every time i try to connect the database using SSMS, I see the following error in the sql server logs in SSMS:

Login failed for user '3aec90b46f01d28\3aec90b46f01d28$'. Reason: Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission. [CLIENT: 127.0.0.1]

Is there a solution to this? We are close to giving up migrating to Cloud SQL :(

Thanks for all the help in advance.

[David (Cloud Platform Support)]

Hello,

Did you follow our quickstart about how to use SSMS with Cloud SQL and were not able to get it working properly? If you have made sure that steps were followed properly, and you are still not able to connect to your instance, I would recommend you to contact GCP support as they would be able to work with you to find out what’s the issue.

In general, Cloud SQL is designed for stability over performance. If you are using MySQL, you can actually enable a flag called performance_schema. I would also make sure the instance is not being overwhelmed and in the same region as the VM. This is also a good subject to discuss with GCP support as they may advise you on things you can try to gain some performance on your instance depending on their analysis of your specific instance. However, a local server, on average, will execute queries faster.

[Alex johson]

Your contribution is greatly appreciated. Your solution is very useful for Techno blade clothes.