我需要一些说明。我知道仅仅为了将 View 放入其中而构建数据库是一个坏主意。更难跟踪，没有架构绑定(bind)或 View 索引。但是我有一些报告人一直在纠缠我，有没有人可以给我任何好的论据？
他们基本上希望拥有适用于不同业务用户的数据库，以及与数据仓库交互的这些 View 。因此，将有 5 个左右的附加数据库，其唯一目的是查看。
最佳答案
您没有“ View 数据库”。
那是摇狗的尾部:)
您可以将一个或多个表的“ View ”放入数据库中。甚至 数据库之间的表。听起来这就是您要找的东西。
强烈建议:阅读这些文章:
附言: 这也可能有用:
Schema
MSDN: SQL Server Best Practices – Implementation of Database Object Schemas
SQL Server 2005 implemented the concept of a database object schema.
A schema is a distinct namespace to facilitate the separation, management, and ownership of database objects.
It removed the tight coupling of database objects and owners to improve the security administration of database objects.
Views
MSDN: Scenarios for Using Views
Views are generally used to focus, simplify, and customize the perception each user has of the database.
Views can be used as security mechanisms by letting users access data through the view, without granting the users permissions to directly access the underlying base tables of the view.
Views can be used to provide a backward compatible interface to emulate a table that used to exist but whose schema has changed.
Views can also be used when you copy data to and from Microsoft SQL Server to improve performance and to partition data.
关于sql - 对另一个数据库的 View ，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/39710437/