If you are doing cross db work then it depends on what you are doing. You probably won't notice a db hit unless you are going cross server.
If "for organizational purposes" is the only reason that you have it on db x instead of db y, then that's not really a legitimate reason for doing it. The databases should be as isolated as possible, otherwise there is no point in having separate databases, except for "organizational purposes, which we won't even go near.
The problem that you run into with cross db is if you ever change your database name. (Things get interesting)
If [blue]you have problems[/blue], I want [green]source code[/green] AND [green]error messages[/green], none of this [red]"there was an error crap"[/red]
