I have a very large site that I would like to publish using RgPublish to the deploy server. However it receives a OutOfMemory exception because it hits a 2GB process limit. It would be nice if there was a 64-bit version of the application that could handle much larger sites so I would not have to manually create the package.3 votes
It would be useful when creating a new release to have a safe guard for marking which environments a release is suitable for. Specifically it would be nice to be able to flag a release as not suitable for production, then prevent the release to the production environment. For example if a release is built for discussion or demonstration purposes which the team knows is not stable for production release but can be released to development or preproduction environments1 vote
Our web and database servers are shared by multiple applications. We would like to setup DA's in such a way so a particular instance is responsible for one or a few applications and can't affect other apps (for instance if someone accidentally or on purpose uses a path that belongs to some other application in a deployment ps script).
To eliminate that risk we want multiple DA's per target server running under different service accounts, so we have control over permissions at account/agent level.6 votes
I need to create (and deploy) a hot fix release on a 1.xx version of a nuget package. The current development effort is on the 2.xx series. When I go to the deployment manager "Create release" screen the version drop down only shows the last 20 versions which are all 2.xx versions.
Either (1) need to be able to increase the number of items in the drop down, or (2) make this a combo where I can enter the prefix and it pulls the versions that match the prefix entered for the "in development" series and the "hot fix" series.8 votes
Deployment manager by default creates new user accounts as a standard user when using windows authentication. This is against our information security policy. Our corporate security policy explicitly states that no user should have access to any system (even view only) unless explicitly created and granted access. In order to use deployment manager in accordance with our info sec policy we need for deployment manager to not create users on first login. There should be a way for a system admin to setup the user manually, then grant system/project permissions to the user. I know that you can disable a user one a user account is created. However, this doesn’t work. We can’t have people randomly finding our site, being setup as a standard user and then we have to deny them.
Deployment manager by default creates new user accounts as a standard user when using windows authentication. This is against our information security policy. Our corporate security policy explicitly states that no user should have access to any system (even view only) unless explicitly created and granted access. In order to use deployment manager in accordance with our info sec policy we need for deployment manager to not create users on first login. There should be a way for a system admin to setup the user manually, then grant system/project permissions to the user. I know that you can disable a…34 votes
I have a large team of developers (60) that support many projects (10+). We use windows authentication as required by corporate policy. All of my developers are members of a single active directory group. It would be nice to be able to add permissiosn to an active directory group instead of each individual user separatly. If this is not possible since I believe each user would need an id create in DM for the api key there should be a way to create a group within DM, map the users into that group and then give DM permission to the group which would be inherited by the members of the group. This way whenever I have a new developer or one leaves I just have to add/remove them from the group.
I have a large team of developers (60) that support many projects (10+). We use windows authentication as required by corporate policy. All of my developers are members of a single active directory group. It would be nice to be able to add permissiosn to an active directory group instead of each individual user separatly. If this is not possible since I believe each user would need an id create in DM for the api key there should be a way to create a group within DM, map the users into that group and then give DM permission to the…36 votes
Recently Deployment Manager added a feature to purge old deployments from the servers. It would be nice to allow this to be scheduled to occur regularly (on a weekly basis?) instead of requiring a manual process.9 votes
Allow the activity history to be exported or setup filtering/searching of the activity history. As an example I would like to see what a specific users activity has been.3 votes
Allow the Systems Admin to set the permissions of other users at a more granular level. Looking at the current permissions grid (http://documentation.red-gate.com/display/DM2/Permissions) it would be nice to turn on or off which of any actions a user could do.3 votes
Add additional deployment step types
Run Powershell scripts
I would like to be able to run a powershell script that are not part of the nuget packages.
We have an internal tool that shows deployment starting, completed and failed deployment. It requires me to touch an rest endpoint. I would prefer to run this as a deployment step and not build into the code nuget package.
This may be useful for doing other SQL powershell tasks like replication management etc.13 votes
It would be useful if you could add a link to the web server that has been deployed to, either from the link in the version label panel or directly from the dashboard page3 votes
We need to have more control over the transform process. We should be able to override the transform name instead of always using the environment name.2 votes
Operationally speaking, it is not ideal to be using the C drive for temp space. Release packages can be several hundred MBs and having a large cache of them needing to live on the C drive is difficult when we typicaly churn servers out with C drives specifically sized to the OS only -- all 'data' should be on attached storage (e.g. the D drive or equiv).
Can we please have the ability to specify a non-C drive location for 'temp' storage?3 votes
The variables grid has too small a column for the step name and I cannot resize it making it hard to know which step I have assigned.3 votes
As a DBA, I would not feel so comfortable when developers upload their modifications directly to Production databases. I must be able to review the changes they are willing to do. Most of the developers are not aware of Index Tuning, T-SQL Best Practices etc. unfortunately...6 votes
It would be great if there was the ability to include in the release documents/artifacts that are related to the release.
This could be done by extending the DeploymentManager.exe create-release command to include an additional param for artifact. Artifact can be a file (doc, pdf, xps, xls, zip, etc.). Ideally this would be used to communicate release notes.
Then in the DM UI, provide a means to display the artifact or allow opening the artifact. This gives DEV/QA/ITOPS clear visibility into any release note information and can be generated and included as part of the integrated build process.3 votesAdminSean Newham (Admin, Red Gate) responded
I don’t think it’s likely we will do this, as we have good ways to include artifacts and release notes.
It would be great if we could set the "Enable 32-bit applications" option for an application pool we create with Deployment Manager.
There's a recent discussion about this in the forum: http://www.red-gate.com/messageboard/viewtopic.php?t=19591&highlight=enable+32bit+applications
The solution presented in that thread will most certainly work (I haven't tested it myself yet) but a DM variable for this setting would be really handy!4 votes
I suspect that this may be a problem with the SQL Compare SDK instead of Deployment Manager proper.
Currently, when trying to deploy a database package with a script including something like the following, it fails to deploy with a parse error:
ON OBJECT::[dbo].[table_name] TO [role_name]
Both the object phrase ("OBJECT::") and the specification of the principal ("AS [dbo]") cause parse issues when trying to deploy this. They're perfectly valid T-SQL, though:
For reference, these database packages are being created via SqlCI.exe from a Visual Studio Database Project.3 votes
It would be nice to customize the dashboard to show/hide different environments.
Another idea is to create different dashboards. Dashboard1 can be all DEV/QA related environments, while Dashboard2 can be all ITOPS related environments (staging, beta, sandbox, production).
This allows the ability for each group to only show their dashboard on a monitor/screen.
Obviously still maintain the ability to show all on a dashboard.10 votes
We have a custom build monitor and it would be great if we could get deployment manager information for key projects/environments and show this on our build monitor.
I know we could add the Dashboard, but our dashboard is very big with all the environments we have.
Having a REST API would allow us to connect to DM and get key information we need.23 votes
- Don't see your idea?