Cake Build addin for working with SqlServer and LocalDb.
Show me the codez: integration tests for live up to date examples. Or look through XML-generated documentation on Cakebuild.net site.
- General Functionality
- Working With Backup files
- Working with BACPAC and DACPAC
- Working with LocalDB
- Usage
- Reason to Develop
DatabaseExists(string connectionString, string databaseName)Return true if the database exists, false otherwise.
CreateDatabase(string connectionString, string databaseName)Creates database. If database with this name exists - SqlException is thrown.
var createSettings = new CreateDatabaseSettings()
.WithPrimaryFile(@"C:\MyPath\MyCakeTest.mdf")
.WithLogFile(@"C:\MyPath\MyCakeTest.ldf");
CreateDatabase(masterConnectionString, "CreateCakeTest", createSettings);Creates a database with the specified primary and log files locations.
CreateDatabaseIfNotExists(string connectionString, string databaseName)Here we check if the database exists first, if it does not exists - create it. Does not do anything if database with this name already exists.
var createSettings = new CreateDatabaseSettings()
.WithPrimaryFile(@"C:\MyPath\MyCakeTest.mdf")
.WithLogFile(@"C:\MyPath\MyCakeTest.ldf");
CreateDatabaseIfNotExists(masterConnectionString, "MyCakeTest", createSettings)This will check if database does not yet exist and will create a new one. And will place primary data file and log file into specified locations.
DropDatabase(string connectionString, string databaseName)Basically executes Drop Database databasename with some fail-safes. Actually it sets the database into offline mode - to cut off all existing connections. Then sets the database back online and then drops it.
Reason for this dance - you can't drop a database if there are existing connections to the database.
DropAndCreateDatabase(String connectionString, String databaseName)Simply a short-hand for DropDatabase(); CreateDatabase();. I found these calls frequently together to create a short-hand.
var createSettings = new CreateDatabaseSettings()
.WithPrimaryFile(@"C:\MyPath\MyCakeTest.mdf")
.WithLogFile(@"C:\MyPath\MyCakeTest.ldf");
DropAndCreateDatabase(masterConnectionString, "MyCakeTest", createSettings)This will drop and re-create the database with provided locations for data and log files.
ExecuteSqlCommand(String connectionString, string sqlCommands);
ExecuteSqlCommand(SqlConnection connection, string sqlCommands);Does what it says on the tin: executes the sql query. But this method accommodates for Go within scripts. Usually executing long queries from .Net won't work when query has GO inside. This one does know what to do with it.
ExecuteSqlFile(String connectionString, string sqlFile);
ExecuteSqlFile(SqlConnection connection, string sqlFile);Reads sql file and executes commands from it. Executes parts of scripts separated by GO as a separate command executions.
OpenSqlConnection(String connectionString)Allows you to use the same connection for multiple SQL commands. Close the connection (by disposing) once you're finished with it. Example:
using (var connection = OpenSqlConnection(@"Data Source=(localdb)\MSSqlLocalDb;Initial Catalog=MyDatabase"))
{
ExecuteSqlCommand(connection, "...");
ExecuteSqlFile(connection, "./somePath/MyScript.sql");
}SetSqlCommandTimeout(int commandTimeout)Allows you to specify the command timeout in seconds for all commands. This is used to set the CommandTimeout property on the underlying SqlCommand.
SetSqlCommandTimeout(60);
using (var connection = OpenSqlConnection(@"Data Source=(localdb)\MSSqlLocalDb;Initial Catalog=MyDatabase"))
{
ExecuteSqlCommand(connection, "..."); // <- execute long-running command
}RestoreSqlBackup(String connectionString, FilePath backupFile, RestoreSqlBackupSettings settings)
RestoreSqlBackup(String connectionString, FilePath backupFile)Restores the database from a .bak file. Options include to rename the target database, specify path where the data/log files are stored and ability to replace existing database.
If new database name is not provided, db-name is extracted from the backup file; if new storage location for data files is not provided, system default folder is used.
Example:
Task("Restore-Database")
.Does(() => {
var connString = @"data source=(localdb)\MSSqlLocalDb";
var backupFilePath = new FilePath(@".\src\Tests\TestData\multiFileBackup.bak");
backupFilePath = backupFilePath.MakeAbsolute(Context.Environment);
RestoreSqlBackup(connString, backupFilePath, new RestoreSqlBackupSettings()
{
NewDatabaseName = "RestoredFromTest.Cake",
NewStorageFolder = new DirectoryPath(System.IO.Path.GetTempPath()), // place files in special location
});
});RestoreMultipleSqlBackup(String connectionString, RestoreSqlBackupSettings settings, IList<FilePath> backupFiles, IList<FilePath> differentialBackupFiles = null)Restores from a list of .bak files. The options and behavior are the same as for RestoreSqlBackup.
If a set of differential backup files are specified the task will first restore the full backup and then restore the differential backup files with appropriate restore settings for the two steps.
The option BackupSetFile and DifferentialBackupSetFile (both are null by default) can be used to explicitely specify the desired backup set for the full backups and the differential backups.
Example:
Task("Restore-Split-Database")
.Does(() =>
{
var connString = @"data source=(localdb)\MSSqlLocalDb";
var backupFile1 = new FilePath("C:/tmp/myBackup1.bak");
var backupFile2 = new FilePath("C:/tmp/myBackup2.bak");
var backupFileList = new List<FilePath> {backupFile1, backupFile2};
var diffBackupFile1 = new FilePath("C:/tmp/myDiffBackup1.bak");
var diffBackupFile2 = new FilePath("C:/tmp/myDiffBackup2.bak");
var diffBackupFileList = new List<FilePath> {diffBackupFile1, diffBackupFile2};
RestoreMultipleSqlBackup(connString, new RestoreSqlBackupSettings()
{
NewDatabaseName = "RestoredFromTest.Cake",
NewStorageFolder = new DirectoryPath(System.IO.Path.GetTempPath()), // place files in Temp folder
WithReplace = true, // tells sql server to discard non-backed up data when overwriting existing database
BackupSetFile = 1, // tells which backup set file to use for backupFile*
DifferentialBackupSetFile = 1, // tells which backup set file to use for diffBackupFile*
}, backupFileList, diffBackupFileList);
});BackupDatabase(string connectionString, string databaseName, BackupDatabaseSettings settings)Backup a database to a .bak file. Options all you to compress the backup file and specify the path (or the specific filename).
Example:
Task("Backup-Database")
.Does(() =>
{
var connString = @"data source=(localdb)\MSSqlLocalDb";
var databaseName = "MyDatabase";
BackupDatabase(connString, databaseName, new BackupDatabaseSettings()
{
Compress = false,
// you can specify either a folder or a file
Path = System.IO.Path.GetTempPath()
});
});This addin includes a thin wrapper around Microsoft.SqlServer.DacFx to provide ability to work with BACPAC and DACPAC files
To create a bacpac file from a database call:
Task("Create-Bacpac")
.Does(() =>{
var connString = @"data source=(localdb)\MSSqlLocalDb";
var dbName = "ForBacpac";
var resultingFile = new FilePath(@".\ForBacpac.bacpac");
CreateBacpacFile(connString, dbName, resultingFile);
});To restore from bacpac file into a database use this:
Task("Restore-From-Bacpac")
.Does(() =>{
var connString = @"data source=(localdb)\MSSqlLocalDb";
var dbName = "FromBacpac";
var file = new FilePath(@".\path\to\my.bacpac");
RestoreBacpac(connString, dbName, file);
})To extract a dacpac file from a database call:
Task("Extract-Dacpac")
.Does(() =>{
var connString = @"data source=(localdb)\MSSqlLocalDb";
var dbName = "ForDacpac";
CreateDatabase(connString, dbName);
var settings = new ExtractDacpacSettings("MyAppName", "2.0.0.0") {
OutputFile = new FilePath(@".\TestData\Nsaga.dacpac")
};
ExtractDacpacFile(connString, dbName, settings);
});
});To publish from dacpac file into a database use this:
Task("Create-Bacpac")
.Does(() =>{
var connString = @"data source=(localdb)\MSSqlLocalDb";
var dbName = "ForDacpac";
var file = new FilePath(@".\src\Tests\TestData\Nsaga.dacpac");
var settings = new PublishDacpacSettings {
GenerateDeploymentScript = true
};
PublishDacpacFile(connString, dbName, file, settings);
});
});Samples show here are using LocalDb\v12.0. This used to be default name for LocalDB instance when installed with SQL Server 2012. Since Sql Server 2014 the default name for LocalDB instance is MSSQLLocalDB, making the default instance name for LocalDB looking like this: (LocalDB)\MSSQLLocalDB. So before using v12.0 double check what instance you have installed and go from there.
This package includes a wrapper for working with LocalDB. LocalDB is a lightweight SQL Server version that is great for running tests against.
Also please don't be alarmed that all the examples are using LocalDB. The plugin is capable of working with any SQL Server installation. This package includes commands to Create, Start, Stop and Delete instances of LocalDB. To be used like this:
#addin "nuget:?package=Cake.SqlServer"
Task("Create-LocalDB")
.Does(() =>
{
// creates and starts instance
// you don't need to start the instance separately
LocalDbCreateInstance("Cake-Test");
});
Task("Start-LocalDB")
.Does(() =>
{
LocalDbStartInstance("Cake-Test");
});
Task("Stop-LocalDB")
.Does(() =>
{
LocalDbStopInstance("Cake-Test");
});
Task("Delete-LocalDB")
.Does(() =>
{
LocalDbDeleteInstance("Cake-Test");
});You can also check our integration tests for live examples.
Remember to always add @ before your connection strings. Some connection strings (i.e. (localdb)\MSSqlLocalDb) can contain backward slash \ and that is an escape symbol in C#. So you need to always add @ before the string:
var connString = @"(localdb)\MSSqlLocalDb";
\v is the C# escape sequence for vertical tab which is not what you want. Using the verbatim string syntax @ prevents escape sequences from being interpreted and you get what you expect, verbatim \ and v characters.
If you have complex connection strings, please consider using SqlConnectionStringBuilder for creating your connection strings:
var connectionString = new SqlConnectionStringBuilder
{
DataSource = @"(LocalDb)\MSSQLLocalDB",
InitialCatalog = databaseName,
}.ToString();This class adds a lot of sugar around creating a connection string.
This script is courtesy of Joseph Musser
If you need to create and delete the database inside of your build script you can use this nice trick.
Somewhere your cake script (usually I put it in lib.cake and reference it from the main script via #load "./lib.cake") put this class:
public static class On
{
public static IDisposable Dispose(Action action)
{
return new OnDisposeAction(action);
}
private sealed class OnDisposeAction : IDisposable
{
private Action action;
public OnDisposeAction(Action action)
{
this.action = action;
}
public void Dispose()
{
var exchange = System.Threading.Interlocked.Exchange(ref action, null);
if (exchange != null)
{
exchange.Invoke();
}
}
}
}Then in your actual cake script you can do:
IDisposable TempDatabase(string connectionString, string databaseName)
{
CreateDatabaseIfNotExists(connectionString, databaseName);
return On.Dispose(() => DropDatabase(connectionString, databaseName));
}and
var masterConnectionString = @"data source=(LocalDb)\MSSQLLocalDB;";
var databaseName = "Tests";
using (TempDatabase(masterConnectionString, databaseName))
{
var connectionString = @"data source=(LocalDb)\MSSQLLocalDB;Database=Tests";
ExecuteSqlCommand(connectionString, "select * from products.......");
// execute your SQL operations
// or run tests
}This technique will make sure your temp database will be dropped after the payload/integration tests are executed.
There is already a project that does similar things: Cake.SqlTools. I have tried it and it was not enough for my purposes. I did look into extending functionality, but the way the project is structured - it won't let me do what I would like to do. The great idea in that project - be able to switch between MySql and SqlServer with a change of a single parameter.
But I wanted to implement things like creating a database if it does not exist. And syntax for that in MySql and SqlServer is different. So if I wanted to extend that project I had to come up with the same functionality in MySql. But I don't use MySql, hell I don't even have it installed on my dev-machines any more.
Install .Net Framwork 4.7.2 Developer Pack
Open a command prompt in the root folder, and run these commands (Only need to run this once for any project. It will allow powershell scripts to execute):
powershell Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
powershell Get-ExecutionPolicy -List
# compile and run unit tests
powershell .\build.ps1 --target run-unit-tests
# publish NUGET package
powershell .\build.ps1
For questions and to discuss ideas & feature requests, use the GitHub discussions on the Cake GitHub repository, under the Extension Q&A category.
