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.
Freitag, 17. Februar 2012 15:59
Microsoft führt eine Onlineumfrage durch, um Ihre Meinung zur Msdn Website zu erfahren. Wenn Sie sich zur Teilnahme entscheiden, wird Ihnen die Onlineumfrage angezeigt, sobald Sie die Msdn Website verlassen.