title: Use a own instance for SqlServer Express?
body: <p>I'm currently developing an application that needs to store data in it's on database, I'm currently using SQL <em>Server Express 2005 with Advanced Services</em> (because we need full text search capabilities).</p>
  
  <p>Local company lore says there have been all sorts of strange problems some years ago when two products used MS SQL Server with the default instance and they had interesting times cleaning everything up into making each application use a named instance.</p>
  
  <p>As I can't remember the exact problems they had ... is it advisable for an application that has to run in a stable way without interference from some other application to have its database in its own named instance? If so, why? What additional isolation does that grant me as opposed to attaching the database to the default instance (or even use a watchacallit - user instance? - where you specify the mdb file location in the connection string).</p>
  
  <p><strong><em>Update:</em></strong></p>
  
  <p>The main concern I have is not performance/CPU - I'm talking about an application that manages Persons/Guests at the front desks of large organizations, think a hotel for example. I think even SQLite could easily handle the amount of data I need (disregarding some features like fulltext search).</p>
  
  <p>My main concern is Customers installing stuff that interferes. From Mitchell's Answer and John's comment from it I think it is advisable to stay in a named instance - but if you have more reasons for that, please voice them.</p>