Database table needed in different databases, how do I organise this?

I am sure this is a common problem, but I would be interested to know the best solution to this. I have an employee table in my dat开发者_如何学Cabase, and I am sure I will need it in many other databases as well. I do not want duplicate data all over the place. So how show I organise this? Should I have a company wide database as well? I am using SQL Server 2008.

One database is preferable to many duplicates. You can create a service layer for your applications to allow them to share the data easily or you can do it at the database level by linking data from different databases/servers (e.g. a "linked server" in Microsoft SQL Server)

One database. And for the details - The "Data Model Ressource book" has exact data structures for common problems (and guess what - yours is one of them) ;)

With SQL Server 2008, Microsoft came out with a new "sofware" called Master Data Management. For exemple, in your case, employee will be Master Datas they need to be unique in every database you will be using. It can be the same way with customers or providers, etc...

Master Datas are the datas that need to be unique organisationnaly wise. All the apps should count on it, CRM, ERP, and home made application.

Here is the link to the product.