Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Tim
Starting Member
392 Posts |
 Posted - 2005-03-13 : 05:21:50
|
| I have a "data warehouse" database that has many tables storing data from different applications. I want to provide users with sets of of views for each "subject area". For example, subject areas may be sales, inventory, finance etc. Some tables are used in multiple subject ares, and some are used in only one. Currently all the views are in the same database as the tables.I am thinking that a separate database (a "data mart") containing views for each "subject area" would be a nice way to give users a clean, uncluttered set of objects for their subject area only. Especially when query tools and report writers don't respect SQL permissions and show the objects (even if they can't be accessed)If I go this way, what are the disadvantages of building views that query tables in a different database. The views are straightforward ... just select and rename certain columns from a single corresponding table. No row selection involved or table joins involved.I don't mind that I have to have all the databases on the same server. |
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-03-13 : 06:34:35
|
| You can't use WITH SCHEMABINDING.Apart from that I think it is an ok approach.rockmoose |
 |
|
|
Tim
Starting Member
392 Posts |
Posted - 2005-03-13 : 06:37:14
|
| so no indexed views in the "data mart" databases then.could always create that in the "data warehosue" database and then create a simple view over that in the "data mart" database I suppose. |
|
|
|
rockmoose
SQL Natt Alfen
3279 Posts |
Posted - 2005-03-13 : 08:03:55
|
| btw, short article here [url]http://www.sqlservercentral.com/columnists/sjones/designingcrossdatabasequeries.asp[/url]rockmoose |
|
|
|
|
|
|
cross database opinions