diff --git a/robot-server/tests/persistence/test_tables.py b/robot-server/tests/persistence/test_tables.py
index a28bf03da99..b57389273f2 100644
--- a/robot-server/tests/persistence/test_tables.py
+++ b/robot-server/tests/persistence/test_tables.py
@@ -44,6 +44,9 @@
     )
     """,
     """
+    CREATE INDEX ix_protocol_protocol_kind ON protocol (protocol_kind),
+    """
+    """
     CREATE TABLE analysis (
         id VARCHAR NOT NULL,
         protocol_id VARCHAR NOT NULL,
@@ -726,7 +729,8 @@ def record_statement(
 
     normalized_actual = [_normalize_statement(s) for s in actual_statements]
     normalized_expected = [_normalize_statement(s) for s in expected_statements]
-
+    print(set(normalized_actual))
+    print(set(normalized_expected))
     # Compare ignoring order. SQLAlchemy appears to emit CREATE INDEX statements in a
     # nondeterministic order that varies across runs. Although statement order
     # theoretically matters, it's unlikely to matter in practice for our purposes here.