NuGet Gallery Feed for sql-deploySql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/2018-12-04T08:50:41Zhttps://www.nuget.org/packages/sql-deploy/0.74.0sql-deploy 0.742013-11-22T16:12:18Z2018-12-04T08:49:47Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.70.0sql-deploy 0.702013-11-20T20:26:52Z2018-12-04T08:49:43Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.69.0sql-deploy 0.692013-11-20T20:02:52Z2018-12-04T08:49:43Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.68.0sql-deploy 0.682013-11-20T20:01:05Z2018-12-04T08:49:46Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.67.0sql-deploy 0.672013-11-20T19:59:33Z2018-12-04T08:49:43Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.66.0sql-deploy 0.662013-11-20T19:51:05Z2018-12-04T08:49:41Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.65.0sql-deploy 0.652013-11-20T19:42:39Z2018-12-04T08:49:44Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.62.0sql-deploy 0.622013-11-20T13:35:09Z2018-12-04T08:49:42Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.61.0sql-deploy 0.612013-11-20T13:18:49Z2018-12-04T08:49:47Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.6.0sql-deploy 0.62013-11-15T18:24:49Z2018-12-04T08:49:41Zvkaldihttps://www.nuget.org/profiles/vkaldiSql Deploy targets a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.5.0sql-deploy 0.52013-11-15T18:09:10Z2018-12-04T08:50:41Zvkaldihttps://www.nuget.org/profiles/vkaldiIt is targeted at a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...https://www.nuget.org/packages/sql-deploy/0.3.0sql-deploy 0.32013-11-15T18:00:10Z2018-12-04T08:49:43Zvkaldihttps://www.nuget.org/profiles/vkaldiIt is targeted at a development/deploy environment where each database change is scripted into a "change script" that brings the database to that level/version.
Each change script represents one database version and they are executed from the "lowest" to the "highest" version sequentially. If the database is already at the version that particular change script is at, that script is skipped.
You can bring the database to a required version by supplying all change scripts up to and including that version.
It supports backups, transactions, baseline scripts, test data population...