title: Using Solutions/Projects on SQL Server Management Studio
body: <p>[I posted a <a href="https://dba.stackexchange.com/questions/19141/alternatives-for-ssms-solutions-projects">related question</a> over at dba.stackexchange, but got little response, so I thought I'd post this here.]</p>
  
  <p>The MSDN documentation is schizophrenic. On the official <a href="http://msdn.microsoft.com/en-us/library/ms173803%28v=sql.105%29.aspx" rel="nofollow noreferrer">SQL Server Documentation</a>, we're told that the use of "Solutions, Projects, and Items" is deprecated. The warning banner reads,</p>
  
  <blockquote>
    <p>"This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature." </p>
  </blockquote>
  
  <p>However, <a href="http://msdn.microsoft.com/en-us/library/ms167154(SQL.105).aspx" rel="nofollow noreferrer">elsewhere in the MSDN docs</a>, using Projects &amp; Solutions is still the prescribed method for storing scripts etc.</p>
  
  <p>So what would you recommend for storing and packaging the various scripts, queries, and files that make up your database application? I would also be very interested to know if any of you are acually using the Solutions or Projects framework in your current work, and what you use them for. </p>
  
  <p>[Note: I realize that I could use VS2010 for this functionality, but I am only interested in SSMS-based approaches as the rest of my team does not have access to VS (and also for the reasons expressed in the answer to <a href="https://dba.stackexchange.com/questions/7599/why-should-i-use-visual-studio-2010-over-ssms-for-my-database-development">this question</a>).]</p>
  
  <p>I am particularly keen on finding the best practice for sharing SQL statements and queries amongst a team -- would you use projects/solutions (backed up in source control)? or perhaps custom templates?</p>