Select Language:
If you’re trying to rotate a secret using “ALTER DATABASE SCOPED CREDENTIAL” on your Synapse serverless SQL database and encounter error code 33253 saying, “Failed to modify the identity field of the credential because the credential is used by an active database file,” don’t worry. This issue happens because the secret is still in use, preventing the change.
To resolve this, the best approach is to clear the cache by restarting the connection pool. Usually, this means contacting support or your cloud administrator to deactivate and then reactivate the pool. Once the pool is reset, the credentials cache is refreshed, allowing you to make the necessary changes.
In most cases, after the pool is restarted, you should be able to run “ALTER DATABASE SCOPED CREDENTIAL” successfully. Keep in mind, restarting the pool might cause a brief downtime, but it’s necessary to complete the secret rotation properly.
Before requesting the pool restart, you can share the resource ID with support privately. Since the old secret has already expired, you don’t need to wait for planned maintenance windows—anytime downtime is fine for this task. Just let support know once the pool has been restarted, and then you can proceed with updating your credentials.
ChatGPT
Perplexity
Gemini AI
Grok AI
