title: Simplifying SQL Server's Logins/Owners/Schemas/Roles/Principals etc
body: <p>I frequently develop small internet applications using ASP.NET and SQL Server 2005.  My databases are always only accessed by one application through an ASP.NET web service or something similar.</p>
  
  <p>When I'm developing an application and moving a database back and forth between my development computer (SQLExpress 2008) and hosted server (SQL Server 2005) invariably I end up getting a hodgepodge of owners/roles/schemas/logins etc that seem to crop up and take control of various pieces of the database.</p>
  
  <p>I only know enough about SQL Server to be dangerous, and I just want to get databases designed, but I invariably have to change the db and end up getting various permissions errors (for example when trying to open a diagram after transferring a db).</p>
  
  <p>Is there a way to simply tell SQL Server Management Studio "Hey, I'm the only guy who's going to use this stupid db, so just let me do it?"</p>
  
  <p>Like some command that sets all of these pieces to 'dbo' or something like that?</p>