title: Does SQL Server Management Studio come with Visual Studio?
body: <p>I have the full Visual Studio 2010 (not express) installed, with SQL Server that came with it as well:</p>
  
  <p><img src="https://i.stack.imgur.com/DKAmD.png" alt="enter image description here"></p>
  
  <p>I was trying to locate SQL Server Management Studio (<a href="http://en.wikipedia.org/wiki/SQL_Server_Management_Studio" rel="noreferrer">ssms</a>) in order to follow <a href="http://www.youtube.com/watch?v=OJfYSZzZOP8" rel="noreferrer">this tutorial</a> but I can't seem to find it in my installation.</p>
  
  <p>I could theoretically download the <a href="http://www.microsoft.com/en-us/download/details.aspx?id=7593" rel="noreferrer">2008 Management Studio Express</a> but given the so many editions and versions of SSMS (e.g. <a href="http://www.microsoft.com/en-us/download/details.aspx?id=29062" rel="noreferrer">2012 Express</a>), how do I know whether it is compatible with my VS 2010?</p>
  
  <p>Also, why download an Express Edition if I already have it in my original Visual Studio 2010 DVD?</p>
  
  <p>So my questions are:</p>
  
  <ol>
  <li>Is SSMS already installed but I don't see it? (if so, how do I locate it?)</li>
  <li>If it's not installed, do I just need to run Setup again, then install it?</li>
  <li>If it isn't really on the VS 2010 DVD (as many on SO suggest), which downloadable Express edition is most compatible with my VS 2010 (not express)?</li>
  </ol>
  
  <p><strong>Update:</strong> (for the benefit of future MS SQL Server newcomers)</p>
  
  <p>Thanks to the answers below I managed to successfully install what I needed and most importantly <strong>understand</strong> the tools picture.</p>
  
  <p>So to answer my particular questions one by one:</p>
  
  <ol>
  <li>No</li>
  <li>No</li>
  <li>SQL Server Management Studio <strong>2008</strong> Express</li>
  </ol>
  
  <p><strong>Tips:</strong> </p>
  
  <ol>
  <li>Once everything is installed, the next question is <em>"What do I do next?"</em>. Fortunately, there is a <a href="http://www.functionx.com/sqlserver/Lesson03.htm" rel="noreferrer">great tutorial</a> which to me is much clearer than the cumbersome (repetitious, cyclic links, non-linear, etc.) <a href="http://msdn.microsoft.com/en-us/library/bb500434%28v=sql.105%29.aspx" rel="noreferrer">official Microsoft documentation</a>. </li>
  <li>Despite the greatness of the functionx.com tutorial, it doesn't provide enough details on how to initially connect <a href="https://stackoverflow.com/questions/360141/how-to-connect-to-local-instance-of-sql-server-2008-express">to local</a>. Once again, SO comes to the rescue and clarifies that 2 more conditions must be met: <strong>(a)</strong> SQL Server <a href="https://stackoverflow.com/a/10421827">Browser</a> service must be running. <strong>(b)</strong> Server name must not be "local" but rather <code>&lt;local-pc-name&gt;\SQLEXPRESS</code>.</li>
  <li>To programmatically create a database in C#, use <a href="http://support.microsoft.com/kb/307283" rel="noreferrer">ADO.NET</a> as well.</li>
  <li><a href="https://stackoverflow.com/questions/529142/what-good-are-sql-server-schemas">Why</a> use schemas.</li>
  <li>Don't even think about storing database files on a <a href="https://stackoverflow.com/a/11954379/1731850">network share</a>.</li>
  <li>If you get "Invalid object name" in a SELECT statement for a table you just created, <a href="https://stackoverflow.com/a/1362575/1731850">refresh the local cache</a>.</li>
  <li>When encountering <code>System.Data.SqlClient.SqlException</code> for the first time you use C# with an existing database using <code>new SqlConnection()</code>, remember that "Data Source=" cannot specify the computer name alone (as in the tutorial) but rather have \SQLEXPRESS appended to the computer name. Also, make sure <a href="http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/" rel="noreferrer">TCP/IP Client Protocol</a> is enabled.</li>
  </ol>