Consider the following scenario:
You have a Windows-based clustering environment.
You create a mount point to mount more than 20 disks or volumes under a single drive letter.
The disks or volumes are marked as available storage.
You install a Microsoft SQL Server 2012 failover cluster instance in this environment.
In this scenario, the installation process takes an unexpectedly long time to validate all the clustered storage.
This issue occurs because of slow performance when the Windows Failover Cluster WMI provider is used to query the partitions of a shared disk.
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2679368 Cumulative Update package 1 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This issue also occurs in SQL Server 2008 and in SQL Server 2008 R2. However, a fix is not available for those versions of SQL Server.
For more information about what to do before you install failover clustering, visit the following Microsoft Developer Network (MSDN) website:
Before Installing Failover ClusteringFor more information about how to install SQL Server failover clusters, visit the following MSDN website: