Hi all,<div><br></div><div>It appears SM SQL 5 reduces the maximum number of databases from 100 (SM SQL 2) to 35 due to a &#39;Microsoft Limitation&#39; on a storage volume.</div><div><br></div><div><a href="https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb53310">https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb53310</a></div>
<div><br></div><div>This article references</div><div><br></div><div><a href="http://support.microsoft.com/kb/943471/en-us">http://support.microsoft.com/kb/943471/en-us</a></div><div><br></div><div>If the NetApp Snapshot occurs at the Volume level nearly instantly via SnapDrive api call, what part of SM SQL uses VDI/VSS ? I understand that SM SQL has to queisce the DB momentarily for a consistent snapshot - is this when VDI/VSS is called ?</div>
<div><br></div><div>It would appear that upgrading our SD/SM SQL version has resulted in a chunk of extra work in splitting out databases out onto more volumes/luns to accommodate this limitation. Its tempting to go back to the previous version.</div>
<div><br></div><div>Most of the DB&#39;s are small MS CRM / SharePoint ones with minimal loading (ie the SQL box isn&#39;t being hammered and the DB&#39;s themselves aren&#39;t big).</div><div><br></div><div>Before we go down this track of adding more drives and splitting out the databases (our DBA&#39;s are less than pleased at the prospect) have other people struck SM SQL 5 backup issues since upgrading due to the number of databases on a lun ? </div>
<div><br></div><div>Thanks in advance,</div><div>Raj.</div><div><br></div><div><br></div>