Discussion on Issues with TEM Usage

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TEM使用问题讨论

| username: xiaoqiao

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version] V7.5
[Encountered Issues: Phenomena and Impact] If production availability is estimated to take some time, for example:

  1. Backup management still lacks incremental backups, making it difficult to use with large clusters.
  2. Lack of logical backups.
  3. Platform objects include non-DBA roles (if opened for developer use, viewing monitoring, SQL diagnostics, etc., requires adding related read and write permissions to the platform).
  4. CDC capability integration.
  5. Issues regarding SQL Edit permissions.
  6. Other discussions…
| username: DBAER | Original post link

If operating with a blank screen:

  1. Platform permissions and roles
  2. Cluster project ownership
  3. Backup and recovery, point-in-time recovery
  4. Data migration integration such as DTS, CDC, DM, etc.
  5. SQL review
  6. Circuit breaker, termination of certain SQLs
| username: onlyacat | Original post link

It’s not open source and there’s no free trial available, so I have no idea what the current state of TEM is.

| username: 小龙虾爱大龙虾 | Original post link

TEM is a component of TiDB Enterprise Edition and will not be open-sourced.

| username: Hacker_QGgM2nks | Original post link


| username: 芝士改变命运 | Original post link

Take a look.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.