SQLMigrationByQuery 1.0.0.9

There is a newer version of this package available.
See the version list below for details.
dotnet add package SQLMigrationByQuery --version 1.0.0.9                
NuGet\Install-Package SQLMigrationByQuery -Version 1.0.0.9                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="SQLMigrationByQuery" Version="1.0.0.9" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add SQLMigrationByQuery --version 1.0.0.9                
#r "nuget: SQLMigrationByQuery, 1.0.0.9"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install SQLMigrationByQuery as a Cake Addin
#addin nuget:?package=SQLMigrationByQuery&version=1.0.0.9

// Install SQLMigrationByQuery as a Cake Tool
#tool nuget:?package=SQLMigrationByQuery&version=1.0.0.9                

SQLMigrationByQuery

This library is SQL database schema version control, This library will execute SQL schema migration query list in .net projects. It's useful for software developers who don't want to use something like Entinty Framework code first and they prefer write their schema migration query by themselves.

Features

SQLMigrationByQuery is .net NuGet Package which control your database schema migration querys, This library will execute all .sql file which you mark them in you main project. After execute any query in your query list a log will save in database.

How to use?

  1. Add SQLMigrationByQuery NuGet Package to your project.
  2. Create a .sql file in your project.
  3. Set any 'Migration Mark' you want in .sql file name, For example "Migration-2020.08.18.sql", The word "Migration-" is 'Migration Mark'.
  4. Call the fuction below in any place you want execute your migration querys.
SQLMigrationByQuery.requestMigration objRequest = new SQLMigrationByQuery.requestMigration();
objRequest.strConnectionString = "YourConnectionString";
objRequest.strCallerProjectName = "YourProjectName";
objRequest.strMigrationMark = "Migration-";
SQLMigrationByQuery.resultMigration objResult = SQLMigrationByQuery.clsMigration.getApplyMigration(objRequest);
if (objResult.blnSuccess == true)
{
    MessageBox.Show("Migration was successful");
}
else
{
    MessageBox.Show(objResult.strError);
}

If objResult.blnSuccess be TRUE it means all query all execute successfully, Otherwise you can find the error in objResult.strError.

You can check the migration result in database by below query

SELECT
    *
FROM dbo.___DatabaseMigration

The .sql sample :

--@strMigrationDesc=Add address and mobile for user table
IF NOT EXISTS (
              SELECT
                  *
              FROM INFORMATION_SCHEMA.COLUMNS
              WHERE TABLE_NAME='tblUser'
                    AND COLUMN_NAME='strMobile'
              )
BEGIN
    ALTER TABLE dbo.tblUser ADD [strMobile] VARCHAR(11) NULL
END
IF NOT EXISTS (
              SELECT
                  *
              FROM INFORMATION_SCHEMA.COLUMNS
              WHERE TABLE_NAME='tblUser'
                    AND COLUMN_NAME='strAddress'
              )
BEGIN
    ALTER TABLE dbo.tblUser ADD [strAddress] NVARCHAR(300) NULL
END

Set your migration descrition from of --@strMigrationDesc= in your .sql file.

Tips

  1. If migration query execute successfully it means that query will never execute again.
  2. Migration .sql files will execute by STRING order so make sure their names are ok.
  3. If any query fail the process will stop and return FALSE.
  4. You can't use GO in your .sql file, If you need it you can add new .sql file.
  5. All command in same .sql file will execute in a transaction, It will rollback if query fail.
  6. The .sql file name should be unique otherwise they second query with same name will never execute.
  7. The migration description exists in your .sql files will be save in migration log (dbo.___DatabaseMigration table)
  8. Make sure your .sql files build action is set to "Embedded Resource".
  9. The caller project name ("YourProjectName") is useful when you want call migration library on more than one project on same database, You shouldn't change this text in future, Otherwise all query withh execute again with new project name.

Author message

I write this library for my personal use but i think it could be useful to other software developers which they don't want to use Entity Framework code first.

If you think any place need an improvement please let me know by pull reuqest.

Product Compatible and additional computed target framework versions.
.NET Framework net40 is compatible.  net403 was computed.  net45 was computed.  net451 was computed.  net452 was computed.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.0.16 471 10/26/2022
1.0.0.15 379 12/26/2021
1.0.0.14 369 9/7/2021
1.0.0.13 404 3/8/2021
1.0.0.12 404 2/23/2021
1.0.0.11 382 2/22/2021
1.0.0.10 425 1/22/2021
1.0.0.9 606 8/30/2020

Return more data in migration result