The following error text appears when running a SQL Change Automation PowerShell cmdlet or add-on:

...Default FILESTREAM filegroup is not available in database...

Cause

Some SQL Change cmdlets and add-ons will fail on their default setting if your database contains any tables with a FILESTREAM column. This is because they make a copy of your database on a temporary server. By default, they use LocalDB for this. However, LocalDB doesn't support FILESTREAM.

Fix

Instead of using the default option of LocalDB for the copy of your database, you can specify a blank database on an alternative temporary server that supports FILESTREAM.

If you're using the SQL Change Automation cmdlets

This error can occur with the following cmdlets:

• Invoke-DatabaseBuild
• Invoke-DatabaseTests
• New-DatabaseDocumentation

In the failing cmdlet, use one of the following parameters:

• -TemporaryDatabaseServer
  Use this parameter to specify an alternative server for the temporary copy of your database.

• -TemporaryDatabase
  If you don't have permission to create a database on the the alternative server, use this parameter to specify an existing database for the copy of your temporary database. 

For more information, see the cmdlet reference for the failing cmdlet.

If you're using the plugin for TeamCity

This error can affect the following steps:

• Build
• Test

Edit the failing step and and use the Temporary database server and Advanced Options to specify the details of the temporary database.