Skip to main content
deleted 458 characters in body
Source Link
NismoGTR05
  • 309
  • 2
  • 12

SQL User Permissions for Continuous Integration via TeamCityDbUp and Octopus

We are building a TeamCity projectCurrently, which would be getting some scripts from the SVN location and deploy against the production database server. This scripts will be generated by our developers, which have all the checks in place, so it can be executed as many times as we wanteddeverloper group has started using DbUp and Octopus to without causing any issuedo Continuous Integration on SQL Database Deployments. We have created a SQLDomain user, so, we can use SQLCMD option under TeamCity which will utilized to deploy scripts against database serversdo the SQL Database deployment via Octopus server.

I wanted to know, what permissions should a SQLDomain user needs to successfully do the database deployment viashould be granted for Continuous Integration process?

I don't want to give "SysAdmin" permission to this SQLDomain user. Is there any particular permissions I can give to this SQL user, so it can successfully do the deployment?

Script could include: Create a table, drop an old table, alter a table, truncate the records, update the records..... We DBA group manually deploy scripts at the moment, we wanted to leverage TeamCity so we can deploy automatically.Do people have implemented above combination for there Continuous Integration of DB Deployment?

SQL User Permissions for Continuous Integration via TeamCity

We are building a TeamCity project, which would be getting some scripts from the SVN location and deploy against the production database server. This scripts will be generated by our developers, which have all the checks in place, so it can be executed as many times as we wanted to without causing any issue. We have created a SQL user, so, we can use SQLCMD option under TeamCity to deploy scripts against database servers.

I wanted to know, what permissions should a SQL user needs to successfully do the database deployment via Continuous Integration?

I don't want to give "SysAdmin" permission to this SQL user. Is there any particular permissions I can give to this SQL user, so it can successfully do the deployment?

Script could include: Create a table, drop an old table, alter a table, truncate the records, update the records..... We DBA group manually deploy scripts at the moment, we wanted to leverage TeamCity so we can deploy automatically.

SQL User Permissions for Continuous Integration via DbUp and Octopus

Currently, our deverloper group has started using DbUp and Octopus to do Continuous Integration on SQL Database Deployments. We have created a Domain user which will utilized to do the SQL Database deployment via Octopus server.

I wanted to know, what permissions should a Domain user should be granted for Continuous Integration process?

I don't want to give "SysAdmin" permission to this Domain user.

Do people have implemented above combination for there Continuous Integration of DB Deployment?

Removed chattiness.
Source Link
Colin 't Hart
  • 9.4k
  • 15
  • 36
  • 44

We are building a TeamCity project, which would be getting some scripts from the SVN location and deploy against the production database server. This scripts will be generated by our developers, which have all the checks in place, so it can be executed as many times as we wanted to without causing any issue. We have created a SQL user, so, we can use SQLCMD option under TeamCity to deploy scripts against database servers.

I wanted to know, what permissions should a SQL user needs to successfully do the database deployment via Continuous Integration?

I don't want to give "SysAdmin" permission to this SQL user. Is there any particular permissions I can give to this SQL user, so it can successfully do the deployment?

Script could include: Create a table, drop an old table, alter a table, truncate the records, update the records..... We DBA group manually deploy scripts at the moment, we wanted to leverage TeamCity so we can deploy automatically.

Please let me know

Thank you, HP

We are building a TeamCity project, which would be getting some scripts from the SVN location and deploy against the production database server. This scripts will be generated by our developers, which have all the checks in place, so it can be executed as many times as we wanted to without causing any issue. We have created a SQL user, so, we can use SQLCMD option under TeamCity to deploy scripts against database servers.

I wanted to know, what permissions should a SQL user needs to successfully do the database deployment via Continuous Integration?

I don't want to give "SysAdmin" permission to this SQL user. Is there any particular permissions I can give to this SQL user, so it can successfully do the deployment?

Script could include: Create a table, drop an old table, alter a table, truncate the records, update the records..... We DBA group manually deploy scripts at the moment, we wanted to leverage TeamCity so we can deploy automatically.

Please let me know

Thank you, HP

We are building a TeamCity project, which would be getting some scripts from the SVN location and deploy against the production database server. This scripts will be generated by our developers, which have all the checks in place, so it can be executed as many times as we wanted to without causing any issue. We have created a SQL user, so, we can use SQLCMD option under TeamCity to deploy scripts against database servers.

I wanted to know, what permissions should a SQL user needs to successfully do the database deployment via Continuous Integration?

I don't want to give "SysAdmin" permission to this SQL user. Is there any particular permissions I can give to this SQL user, so it can successfully do the deployment?

Script could include: Create a table, drop an old table, alter a table, truncate the records, update the records..... We DBA group manually deploy scripts at the moment, we wanted to leverage TeamCity so we can deploy automatically.

edited tags
Link
user1822
user1822
Source Link
NismoGTR05
  • 309
  • 2
  • 12
Loading