May 26, 2020 at 12:00 am
Comments posted to this topic are about the item Adding a Database with Polybase External Tables to Always On Availability Group
May 26, 2020 at 4:35 am
Good Article Ramya!
May 26, 2020 at 12:51 pm
Hi, Ramya,
nice work! Very detailed, very interesting!
Only thing that irritated me in terms of processes: We'd have a single point of failure in the external table; at least the assigned database might fail in such an availability group. What was the scenario: OLAP, OLTP?
Perhaps you might want to differentiate the passwords (you're using always "password@123" which is at least for me a bit misleading):
Idea: It might be more intuitive to use different passwords (e.g. P@$$w0rd_database_master_key, P@$$w0rd_database_scoped_credential, P@$$w0rd_external_data_source).
What do you think?
JP
________________________________________________________
If you set out to do something, something else must be done first.
May 26, 2020 at 1:50 pm
Nice work, Good to know Ramya.
May 28, 2020 at 3:00 am
I don't quite understand. If you are specifying the user/pass in the connection options when creating a data source, what is the point of creating a database scoped credential with the same user/pass?
June 5, 2020 at 8:38 am
@Dscheypie - Agreed. Master key password can be different from the one mentioned in data source. However, the secret in database scoped credential and the connection options in External data source should match to make a successful connection.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply