While developing a product, I've come across a situation where my group wants to store meta data for data entry forms (questions, layout, etc) in a different database then the database where the collected data is stored.  This is mostly for security because we want to be able to have our meta data public facing, while keeping collected data as secure as possible.I was thinking about writing a web service that provides the meta information that the data collection program could access.  The only issue I see with this approach is the front end is going to have to match the meta data with the collected data, which would be more efficient as a join on the back end. Currently, this system is slated to run on .NET and MSSQL. I haven't played around with .NET libraries running in SQL, but I'm considering trying to create logic that would pull from the web service, convert the meta data into a table that SQL can join on, and return the combined data and meta data that way.Is this solution the wrong way to approach the problem?  Is there a pattern or industry standard way of bringing together two datasets that don't live in the same database?
Working with data and meta data that are separated on different servers
design;.net;sql;rest
Well, the bigger problem is that effectively prevents you from maintaining consistency between the data sets. If you store the data like this, it will break.I would probably store the metadata in the internal database alongside the data and set up replication of the metadata only to another server in DMZ where the public facing interface can access it.