Thank you for the reply!
There is a full backup that occurs every night. That was one of the first questions I asked.
Something else to note is that there is another team that is responsible for the maintanance of the server to include backups, SQL Server performace, and hardware. They are a "reactive" team instead of a "proactive" team, so we have to request them to run any type of performance monitoring. Kind of a bummer, but hey, I don't make the rules. My team is resposible for creating .NET applications and designing the databases to include tables, stored procs, triggers, all that fun stuff. So it's not too bad.
I think requesting a rebuild of the indexes is great place to start. I am almost positive this has never been done. If that doesn't help, then I'll move on to requesting output from perfmon.
Regarding the one database ... I've tried looking for a book or some kind of document that describes proper database design and how to determine when to create mulitple databases. I'm sure I didn't view every book out there on this subject. Do you know of anything I can refer to as reference to help support my point to my manager? Or ... Besides the fact that all of the data is kept in one file and we have to scroll through hundreds of tables to find what we need, can help me point other facts that make a "one database for everything" design a bad idea?
Thank you again for your response and for the congrats on the job.