Run migration scripts created by SQL Source Control

I would like to be able to specify a variable with a name i.e. MyDatabase then set different values depending on the environment/machines its deployed to.
Currently I have to duplicate each variable by the number of environments/machines I have which makes it more difficult to keep in sync if names change and makes the UI a bit messy.

We have about 400MB of reference data that our application is using. This is difficult to deploy using Deployment Manager at the moment for a few reasons.

I don't want to have to write custom powershell to make this work.

If you have a lot of project and environment then your dashboard get very hard to read and you are not sure if every project in you project group (group of related projects) have correct version. In some cases timeline would help, or show only one group or even only one environment and one group (just mix) to get better visual overview.

Add custom Update.sql scripts when deploying from Sql Management studio deployment manager plugin. When you are creating or updating database you might want to add custom sql script to insert static data into table(s)

Option to skip tSQLt framework and tests when deploying package SQL management studio plugin. When using tSQLt test framework I only want to deploy that to the test database not the production database.

When you set up a deployment you have the option to have only certain steps apply to certain environments. You also have the option to not run a step when you hit "Deploy to". When the package is deploying and afterwards if a step is skipped it still gets a green check box which is miss leading. That step should be struck through or have a different icon (blue !) or something to denote it was not run on purpose. A green check makes you think the step was actually run when it was not.

We use Azure to host our staging and production website and databases.

Anyway to deploy there?

I think it would be useful to be able to copy an existing project in the web interface.

Deployment Manager should be able to deploy database changes to target databases using DACPACs.

The ability to control the appSettings and connectionString settings in config files with variables in a deployment project is great stuff, but I want more! :-)

It would be great to be able to control other sections as well.

As it stands, we've ended up with a hybrid solution consisting of variables and config file transforms; ideally, I'd like to be able to stick to one of these methods.

The IIS commandlets are not available from a 32 bit Powershell, which is how the DM agent currently hosts it. A work around was suggested in the forum, but it would be better to be able to use native powershell IIS tooling.

In most cases it's sufficient to see the NuGet package id in the list of steps in the web gui, but I think it would be useful to be able to add a customized name to steps in order to further distinguish steps from each other (this is something I miss from TeamCity).

I think it would be useful to have a "Stop running deployment" button in the Deployment Server Web Interface so that we can stop a currently running deployment process.

If you would like to test powershell scripts that are run at different stages of deployments, you have to create a release and actually deploy.

The agent hosts Powershell in-process and some scripts may run differently to when you are testing them by running them in Powershell. Agent.exe command line functionality to run scripts will in the same way they are run during a deployment.

Variables are listed here:
http://www.red-gate.com/SupportCenter/content/Deployment_Manager/help/1.0/dm_variables

But they are not shown anywhere in the UI.

For each project, can we have all these variables listed (in the variables sub-section) with their default values (and possible values) in a similar way that Team City shows all possible configuration options.

This way we can easily see what settings are available, what their values are, and what we might change them to.

A note about design... It's a a bit too vertically spaced. I find myself having to scroll up and down a lot. And this is with only a single test project.

We have 50+ clients. That means 50+ projects on the dashboard. Lots of scrolling!

Environments section could be more compact, as with Settings.

The UX of the Projects section needs a bit of work.

It's a bit hard to find a deploy button.

My user story: "As a user, I want to be presented with the option to easily deploy a specific release"

- Overview could have a release summary with deploy buttons.
- Releases should have deploy buttons.