What problem does it solve? SharpPS Sitecore solutions replay every *.sql file in a configured Scripts folder on every run of the Database.Tools console project, so any non-idempotent statement fails or corrupts state on the second execution. This Skill explains how to locate the correct Database project and Scripts folder by structure, choose between a one-time EF Core migration and the replay-every-run scripts folder, and write each statement type with the idempotency guard it requires. ## Core Features & Use Cases - Project and folder discovery: Locate the Database project via its DbContext/Migration classes and confirm the Scripts folder through the MigrationScriptPath config key in the sibling Database.Tools project, instead of guessing fixed project names. - Mechanism selection: Decide between an apply-once EF Core migration under Migrations/ and a *.sql file that is re-asserted on every deploy, or a Manual/ folder for one-off DBA scripts. - Idempotency patterns: Provides ready-to-copy guards for CREATE TABLE (OBJECT_ID check), column add/drop (COL_LENGTH check), seed data (IF NOT EXISTS on a stable key), and CREATE OR ALTER for stored procedures and functions. - Use Case: You need to add a CreatedBy column and a new stored procedure to a Sitecore solution's database. The Skill guides you to the correct Scripts folder and gives you a script that runs cleanly no matter how many times Database.Tools executes. ## Quick Start Ask the assistant to write an idempotent SQL script that adds a column and a stored procedure to the SharpPS Sitecore database project's Scripts folder.
