From b60ee8255bada99be20924b41baea238a448432c Mon Sep 17 00:00:00 2001
From: yuki-tei <57980555+yuki-tei@users.noreply.github.com>
Date: Fri, 10 Oct 2025 09:51:03 +0900
Subject: [PATCH] Update 08_mtk_command_options.mdx

---
 .../55/07_invoking_mtk/08_mtk_command_options.mdx             | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx
index 6f1082f9951..cc63f5d892d 100644
--- a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx
+++ b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx
@@ -403,6 +403,10 @@ Use the migration options to control the details of the migration process.
 
 Truncate the data from the table before importing new data. Use this option with the `-dataOnly` option.
 
+!!!note
+If -truncLoad is spcified, all indexes and constraints are dropped before data laod and recreated afterward. Hence if data load is failed, indexes and constraints might be lacking. Manual operation might be necessary, depending on the situation.
+!!!
+
 ### `-enableConstBeforeDataLoad`
 
 Include the `-enableConstBeforeDataLoad` option if a nonpartitioned source table is mapped to a partitioned table. This option enables all triggers on the target table, including any triggers that redirect data to individual partitions, before the data migration. `-enableConstBeforeDataLoad` is valid only if you also specify the `-truncLoad` parameter.