I have a database in an AG whose secondary replica has different file paths (a mount point) than the primary. This secondary replica's file paths shown in SSMS are always the same as the primary database, even though they are not the same.
I did failover, the secondary becomes primary, now the paths are correct, but the previous primary's paths become incorrect. Is this known issue? I am using RC0.
I have seen this issue too. It seems that the DMVs for the file paths are somehow stored or cached within the database. My assumption is that with the new readable secondary feature you are actually looking at the readable copies of the primary instead of
the metadata on the secondary.
I am basically interested in using SMO (or any other means) to programmatically find out all file paths of the secondary replicas. I haven't tried SMO yet, but I can see it is not working with SSMS. Thanks.
2012년 2월 17일 금요일 오후 3:59
Microsoft는 Msdn 웹 사이트에 대한 귀하의 의견을 이해하기 위해 온라인 설문 조사를 진행하고 있습니다. 참여하도록 선택하시면 Msdn 웹 사이트에서 나가실 때 온라인 설문 조사가 표시됩니다.