Dear Tencent Cloud user,
To provide more stable and reliable account management, TencentDB for SQL Server is refactoring the backend logic of its account management module. The refactored capabilities will be made available through a new set of APIs, which add new features including last login time, login history queries, and the ability to enable or disable accounts.
During this refactoring, the legacy and new APIs will run in parallel. The existing (legacy) APIs remain unchanged, with no breaking changes, so you can migrate at your own pace. Going forward, all new account management features will be delivered only through the refactored APIs. If your systems are integrated with account management capabilities, we recommend that you evaluate the new APIs and plan your migration.
Effective Time and Scope
Effective date: October 31, 2026 (UTC+8).
Scope: All TencentDB for SQL Server instances in all regions and of all specifications.
API Change Summary
Legacy APIs (unchanged; no new features)
|
DescribeAccounts | DescribeAccounts | Legacy | Remains available, with no plans for deprecation; no new features will be added. |
New APIs (recommended)
|
DescribeAccountsV2 | DescribeAccountsV2 | New | Queries the list of accounts on an instance and also returns additional fields, such as each account’s last login time. |
Enable/Disable Account | ModifyLoginStatus | New | Changes the login status of a database account, allowing it to be enabled or disabled. |
Capability Comparison
New Capabilities
The refactored Account Management page and new APIs introduce the following capabilities:
Last login time for each account: The account list now shows the most recent login time for each database account, helping you identify inactive ("zombie") accounts and detect unusual account activity.
Account login history: You can query each account’s login history, including login statistics and login details, on the Account Management page. This data can be used for security audits and incident investigations.
Enabling and disabling accounts: You can disable and enable database accounts on the Account Management page or through the ModifyAccountStatus API. Unlike deleting an account, disabling it retains the account and its permission settings while temporarily blocking logins, which reduces the risk of accidental changes.
Discontinued Capabilities
|
Databases column | Shown on the Account Management page, listing the databases associated with each account | Removed from the Account Management page; this information is no longer returned by DescribeAccountsV2 | To view which databases an account is mapped to, go to Database Management and query account permissions at the database level |
Note：
This change applies only to the Account Management page and the new DescribeAccountsV2 API. If your workloads rely on querying the databases associated with an account, the legacy DescribeAccounts (V1) API remains unchanged and continues to return the relevant fields.
FAQ
Q1: Will the legacy DescribeAccounts API be deprecated?
No. The legacy API remains unchanged and will continue to be available, and you will not be required to migrate. However, all future account management enhancements will be released only on the new APIs, so we recommend switching to them when convenient.
Q2: What happens if I don’t migrate to the new APIs?
Existing features of the legacy API will remain unaffected, but new fields and capabilities will not be added to it. You can still use the related features via the updated console; when using the API, please integrate with the corresponding new endpoints.
Q3: Why was the "Databases" column removed from the Account Management page?
This column required permission data to be aggregated across databases, which caused high query overhead and slow page loading on instances with many accounts or databases. As part of the refactoring, account-to-database mappings are now queried at the database level in Database Management, providing a clearer query path and more consistent performance.
Q4: Will disabling an account terminate its existing connections?
Disabling an account only prevents subsequent logins and does not automatically terminate existing connections. To immediately stop the account from accessing the system, you must separately terminate the relevant connections. It is recommended to perform this operation during off-peak business hours. Before proceeding, confirm with the business team the handling method for existing connections and assess the potential business impact.
Q5: How far back can I query login history data?
Contact Us
If you encounter any issues while migrating to the new APIs or using the new features, please submit a ticket via the Tencent Cloud Ticket System or contact your dedicated solution architect or after-sales technical support team. Thank you for your continued support of TencentDB for SQL Server.