SQL Server "Database" definition

[Kirk R Fleming]

I have a beginner question regarding the creation of databases (in the SQL
Server sense). Specifically, I'm beginning to move Access databases to SQL
Server, and up until now I have had a 1:1 correspondence between
applications and PC-based databases. I would like to eventually get to a
comprehensive enterprise data model, shared data, and a managed data
environment.

Rather than create SQL Server databases for each application (and rather
than naming those databases after the applications) I'd prefer to set up a
minimum number of SQL Server databases based on some logically organization
of the information. But, for an organization of about 500 users, I can't
think of any reason to have more than just a single named SQL Server
database on the SQL Server machine.

The same SQL Server machine used to support all in-house developed
databases will also be used to support the DOCS Open document management
system, which I believe will create its own SQL Server database.
Therefore, even if I only did create one single monolithic database for use
by all applications, I will still probably have more that one named
database on the system due to commercial apps such as DOCS Open.

I've never seen this issue of data organization at this level addressed.
How do others do it? I don't want to establish SQL Server databases based
on departments, based on intended use of the data or any other criteria
that violates the whole idea of a shared data resource. Multiple
departments will naturally have common data needs, and I don't believe data
should be organized based on it's intended use, since there is no way to
predict "intended use" and I certainly don't want to presume a use that
would in any way preclude or hinder any unforeseen use. What to do?