Open VickyWinner opened 5 years ago
Is this because PowerShell is case-insensitive as default, and BIN2 collation is case-sensitive?
Yes. When I pass the values of hostnames for replica creation, I pass them in lower case. But still the one replica got created in uppercase. When I try to set AG properties using PS Provider, it couldn't find the AG replica. So, I had to manually convert to replica name to uppercase so it can find and I can set the AG properties. Hope this is clear now.
So it’s the SqlAg or SqlAGReplica that had this problem creating the replica name in upper case? Trying to narrow down where the fault might be.
Problem: I see that one of the AG replicaname was created in upper case. Both the endpoint URLs created in upper case.
Description Unable to manage AG objects when used with BIN2 collation.
Steps to produce error Simply assign node names in lower case.
Error Produced No errors because this is a behavioral issue
Exploration I did manually converted to lowercase and then assigned to parameters of these resources but no luck.
SqlServerEndpoint SqlAG SqlDatabase SqlAGReplica SqlAGDatabase
I am using SQL 2016 on Windows 2016.