A hot standby node belongs to a clique of nodes and does not host virtual processes such as AMPs or Parsing Engines.
The standby node remains idle until a member of its clique crashes or fails. At this point, the standby node is activated to take over the failed node’s responsibilities.
The AMPs from the node that crashed are swiftly migrated to the hot standby node, resulting in negligible performance loss.
The intelligence of the design lies in the fact that once the failed node goes back online, it automatically takes over as the active standby node.
Related Services
🔧 Need Expert Database Administration?
Our team brings 25+ years of enterprise DBA experience across Teradata, Snowflake, and Oracle.
Meet Our Team →📋 Considering a Move From Teradata?
Get a personalized migration roadmap in 2 minutes. We have migrated billions of rows from Teradata to Snowflake, Databricks, and more.
Free Migration Assessment →