title: What is the best way to partition large tables in SQL Server?
body: <p>In a recent project the "lead" developer designed a database schema where "larger" tables would be split across two separate databases with a view on the main database which would union the two separate database-tables together.  The main database is what the application was driven off of so these tables looked and felt like ordinary tables (except some quirky things around updating).  This seemed like a HUGE performance problem.  We do see problems with performance around these tables but nothing to make him change his mind about his design.  Just wondering what is the best way to do this, or if it is even worth doing?</p>