title: SSMS Hangs on Create Database (but not via T-SQL)
body: <p>Environment:   <code>SQL Server 2008 SP3</code> - using <code>SSMS2008</code> (local or remote) and <code>SSMS2012</code> (remote)</p>
  
  <p>Something happened with our SQL Server instance recently.    Nobody is able to create a new database through an SSMS (SQL Server Management Studio) interface.   Neither SSMS for 2008, or SSMS for 2012.    </p>
  
  <p>What happens is they hang (or appear to hang).    Sit and spin forever, and then the performance of the SQL instance <em>really</em> starts to tank while it is chewing away.    CPU usage skyrockets.</p>
  
  <p>Things I've noticed:</p>
  
  <ol>
  <li>Telling it to create the MDF/LDFs on a local drive or network drive makes no difference.</li>
  <li>We've tried disabling the anti-virus tools on both the SSMS machine and SQL instance server, with no change.</li>
  <li>We've tried using the SSMS on the SQL instance server itself, and it also just spins.  Any SSMS (we've tried three different machines) does the same thing.  </li>
  <li>If I open Windows Explorer and look at the locations I've told it to put the MDF/LDFs, <strong>they are created</strong>.     I see the MDF and LDF show up.</li>
  <li>As soon as I kill the SSMS process (because it feels like it's hanging), it does some cleanup work and the MDF/LDFs go away.</li>
  <li>I can successfully use the <code>CREATE DATABASE</code> t-sql script in a query window, and it creates the databases fine, fast as can be, like one would expect.</li>
  <li>FILESTREAM is <strong>not</strong> enabled for the server instance at all.   No database uses it in the instance.</li>
  </ol>
  
  <p>This only started happening recently - and the only thing I found with GoogleFu was a hotfix by Microsoft for SQL2008-SP2, that had to deal with microfilters and antivirii.   This is SP3, so that fix is rolled into it (as well as we disabled AV on the SQL server and our local machines - to be sure).</p>
  
  <p>Any suggestions or ideas?   Is there some trace profile I can start up that would show me what is going on, step by step, to see where the SQL instance seems to be spinning its wheels when I try creating a database through the SSMS interface?</p>