Comments
Sort by recent activity
Hi @Bobby, Have you generated the documentation using the UI at least once and saving the project file? This is a necessary first step, after which you're able to use the command line to refresh the documentation. Cheers, Lubos
/ comments
Hi @Bobby,Have you generated the documentation using the UI at least once and saving the project file? This is a necessary first step, after which you're able to use the command line to refresh the...
Hi @..., You're able to mark a migration script as deployed from SQL Source Control under the Migrations tab, where you can expand the Existing migration scripts and find the latest migration script to mark it as deployed. Note the Name and Id of the script and edit the following Insert statements, swapping out the MigrationName and MigrationId with Name and Id, respectively. <div><code>INSERT INTO [RedGateLocal].[DeploymentMetadata] ([Name], [Type], [Action], [BlockId], [MetadataVersion]) <br>VALUES (N'MigrationName', 'Compare', 'Deployed', 'MigrationId auto', 'manual')<br>INSERT INTO [RedGateLocal].[DeploymentMetadata] ([Name], [Type], [Action], [BlockId], [MetadataVersion])<br> VALUES (N'MigrationName', 'Migration', 'Deployed','MigrationId user', 'manual') Execute this SQL on the database you wish to have the migration script deployed on. SOC5/RedGateLocal.DeploymentMetadata Documentation Lubos / comments
Hi @..., You're able to mark a migration script as deployed from SQL Source Control under the Migrations tab, where you can expand the Existing migration scripts and find the latest migration scrip...