Use Teamcity with Sql Change Automation Build for an AWS RDS instance with temporary database

• 
  I'm not overly familiar with RDS sadly but does it work if you precreate the temporary database in RDS?

  Russell D August 05, 2019 07:31

  - 0 +
• 
  I did in the second scenario and I gave the redgate login db_owner rights. Unfortunately as you see in the log snippet it starts with dropping users first (including itself). After that it can't access the database anymore. In our on premises server the redgate user is sysadmin but that role is not available in RDS instances

  Freek August 07, 2019 08:12

  - 0 +
• 
  Yeah ok that sounds about right - you'd need to have a pre-created database and specify it in the build parameters with -TemporaryDatabase so that it doesn't get dropped/recreated every time.
  

  Russell D August 07, 2019 08:18

  - 0 +
• 
  So why is this happening when I do that:
  
  

  [13:07:44][Step 1/2] VERBOSE: Dropping users

  [13:07:44][Step 1/2] WARNING: The error 'The server principal "our_redgate_user" is not able to access the database "redgate_temp" under

  [13:07:44][Step 1/2]  the current security context.' occurred when executing the following SQL:

  @ERROR <> 0 SET NOEXEC ON
  
  ?

  Freek August 07, 2019 08:34

  - 0 +
• 
  I did in the second scenario and I gave the redgate login db_owner rights. Unfortunately as you see in the log snippet it starts with dropping users first (including itself). After that it can't access the database anymore. In our on premises server the redgate user is sysadmin but that role is not available in an RDS instance.

  Freek August 08, 2019 10:51

  - 0 +
• 
  I did in the second scenario and I gave the redgate login db_owner rights. Unfortunately as you see in the log snippet it starts with dropping users first (including itself). After that it can't access the database anymore. In our on premises server the redgate user is sysadmin but that role is not availabl

  Freek August 08, 2019 10:51

  - 0 +
• 
  I did in the second scenario and I gave the redgate login db_owner rights. Unfortunately as you see in the log snippet it starts with dropping users first (including itself). After that it can't access the database anymore. In our on premises server the redgate user is sysadmin but that role is not availabl

  Freek August 08, 2019 10:51

  - 0 +
• 
  I did in the second scenario and I gave the redgate login db_owner rights. Unfortunately as you see in the log snippet it starts with dropping users first (including itself). After that it can't access the database anymore. In our on premises server the redgate user is sysadmin but that role is not available in an RDS instance.

  Freek August 08, 2019 10:51

  - 0 +
• 
  I wonder if it just doesn't work for the temporary database, and RDS is supported for deployment targets only - I'll try to find out.
  

  Russell D August 08, 2019 13:48

  - 0 +
• 
  I've been working with the automation plugin for over two years now and with RDS instances little over a year since we migrated away from our own servers. So if there's anything I can do to assist, let me know.

  Freek August 14, 2019 12:01

  - 0 +

Add comment

Please sign in to leave a comment.