title: The dbo. prefix in database object names, can I ignore it?
body: <p>I am looking for a performant default policy for dealing with the .dbo prefix. </p>
  
  <p>I realize that the dbo. prefix is more than syntactic noise, however I got through the past 8 years of MS based development skipping typing the dbo. prefix and ignoring its function.</p>
  
  <p>Apart from a performance issue with stored proc compile locks is there a downside to skipping typing ".dbo" in SQLqueries and stored procedures?</p>
  
  <p>Further background: All my development is web middle-tier based with integrated security based on a middle tier service account.</p>