title: What's the best way to manage sql change scripts for two developers?
body: <p>Up until now I've been a lone wolf on my client projects.  Anytime I would make changes to SQL Server: tables updates, stored procs, etc.  I would generate the change script and plop it into a directory.  When the application was ready for release, I would run the scripts on the live server and be done.</p>
  
  <p>Soon I will have another developer working on the same project.  The project files are all in source control.  I'm just not exactly sure how to go about handling the change scripts.  I'm guessing they should be under source control as well?  If so, what would be the best naming convention?  How exactly would I determine which scripts are to be executed on the next release?  Keeping in mind that this is a fairly low-key, informal web project that does not have any version numbers or project management software.</p>
  
  <p>Thanks.</p>