• Before you put different applications within a single database, I'd check to see just how much cross-dependencies there are between the apps. Do they share tables & procedures? If so, you have a case for putting them into a common database. If they share nothing, or little, I'd keep them seperated because by putting them into a common database, you're going to tightly couple these apps and make it very difficult to develop them indepdent of each other.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning