Comments
Sort by recent activity
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. / comments
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 ac...
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. / comments
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,...
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 / comments
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 ac...
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 ? / comments
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 databa...
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. / comments
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 ac...
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 / comments
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 ac...
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 / comments
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 ac...
Could you check if the tables the views refer to are pre-fixed with the same database name as they are in? I had the same issue and it was solved by removing the database prefix. Otherwise the plugin considers them to be outer references and doesn't search for them in the payload. / comments
Could you check if the tables the views refer to are pre-fixed with the same database name as they are in? I had the same issue and it was solved by removing the database prefix. Otherwise the plug...
I found it here: https://assets.red-gate.com/products/dba/sql-clone/sql-clone-getting-started-guide.pdf
It does say 'or later' however ...
Thanks for the answer :-) / comments
I found it here: https://assets.red-gate.com/products/dba/sql-clone/sql-clone-getting-started-guide.pdf
It does say 'or later' however ...
Thanks for the answer :-)