[DMS-938] Emit Project Schemas + Resource/Extension Tables + Abstract Identity Tables/Views

reference/design/backend-redesign/design-docs/data-model.md

@@ -947,13 +947,14 @@ Alignment note:
 - SQL Server scalar types intentionally match Ed-Fi ODS SQL Server conventions (authoritative DDL uses `NVARCHAR`, `DATETIME2(7)`, `TIME(7)`, and `DATE`).
 
 Rules:
-- Scalar strings must have `maxLength`; missing `maxLength` is an error.
+- Scalar strings should have `maxLength`. When `maxLength` is omitted, PostgreSQL emits `varchar` (unbounded) and SQL Server emits `nvarchar(max)`.
 - Decimals must have `(totalDigits, decimalPlaces)` from `decimalPropertyValidationInfos`; missing info is an error.
 - `date-time` values are treated as UTC instants at the application boundary. SQL Server storage uses `datetime2(7)` (no offset), so any incoming offset is normalized to UTC at write time.
 
 | ApiSchema JSON schema | PostgreSQL type | SQL Server type |
 | --- | --- | --- |
-| `type: "string"` (no `format`) | `varchar(n)` | `nvarchar(n)` |
+| `type: "string"` (no `format`, with `maxLength`) | `varchar(n)` | `nvarchar(n)` |
+| `type: "string"` (no `format`, no `maxLength`) | `varchar` | `nvarchar(max)` |
 | `type: "string", format: "date"` | `date` | `date` |
 | `type: "string", format: "time"` | `time` | `time(7)` |
 | `type: "string", format: "date-time"` | `timestamp with time zone` | `datetime2(7)` |

reference/design/backend-redesign/epics/03-provisioning-workflow/EPIC.md

@@ -16,6 +16,15 @@ Provide an operational workflow for schema provisioning that matches the redesig
 
 Authorization objects remain out of scope.
 
+## Implementation Notes
+
+### SQL Server Batch Separators
+
+The emitted MSSQL DDL contains `GO` batch separators required for `CREATE OR ALTER` statements (triggers and views must be first in their T-SQL batch). `GO` is not valid T-SQL—it is a batch delimiter recognized by `sqlcmd` and SSMS.
+
+- **DB-apply smoke tests**: Use `sqlcmd -b -i ...` which handles `GO` natively.
+- **CLI `ddl provision`**: When executing via ADO.NET, the provisioner must split the script on `GO` lines and execute each batch separately.
+
 ## Stories
 
 - `DMS-950` — `00-ddl-emit-command.md` — CLI: `ddl emit` (files + manifests)

src/dms/backend/EdFi.DataManagementService.Backend.Ddl.Tests.Unit/CoreDdlEmitterTests.cs

@@ -845,6 +845,20 @@ public void It_should_create_or_alter_trigger()
         _ddl.Should().Contain("CREATE OR ALTER TRIGGER [dms].[TR_Document_Journal]");
     }
 
+    [Test]
+    public void It_should_emit_go_batch_separator_before_trigger()
+    {
+        // CREATE OR ALTER TRIGGER must be the first statement in a T-SQL batch
+        var triggerIndex = _ddl.IndexOf("CREATE OR ALTER TRIGGER");
+        var goIndex = _ddl.LastIndexOf("GO\n", triggerIndex);
+
+        goIndex.Should().BeGreaterOrEqualTo(0, "expected GO batch separator in DDL");
+        triggerIndex.Should().BeGreaterThan(goIndex);
+        // The GO should be immediately before the trigger (only whitespace between)
+        var between = _ddl.Substring(goIndex + 3, triggerIndex - goIndex - 3);
+        between.Trim().Should().BeEmpty("GO should immediately precede CREATE OR ALTER TRIGGER");
+    }
+
     [Test]
     public void It_should_attach_trigger_to_document_table()
     {