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 |
clement.store
Starting Member
25 Posts |
Posted - 2010-09-09 : 03:48:25
|
Hello there,I wonder if there is any performance difference between querying a huge single view or multiple broken down views? ( both totalling same number rows ) As I usually notice that only 50% of CPU usuage will be in use by SQL server on a query. If views are spread in multiple, then it takes multiple query to retrive data from multiple views. Would this overcome any resource constraint if there is any in the SQL server? I m using SQL server 2005 SP3 and windows 2003 standard. thanks |
|
MSquared
Yak Posting Veteran
52 Posts |
Posted - 2010-09-09 : 08:42:06
|
It depends. If a front-end is being used, then the queries would need to be changed to reflect the new views. How are the views setup? Are they all on the same table or are there multiple tables involved? Multiple views could be helpful, but not enough information to make a decision. If the tables are partitioned, then one view would be better. Can you provide more information as to how the data is setup and how it is queried?For Faster results please follow the posting guidelines herehttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspx |
 |
|
clement.store
Starting Member
25 Posts |
Posted - 2010-09-09 : 22:13:49
|
Thanks for your reply. Views generated from both approaches are from same set of tables ( over 100 ) andthey are not partitioned. They are generated by some stored procedures on monthly update of master data. These tables will be queried by reporting server (business objects) with requests on views containing about 20 tables each time. If i have a single view, i can manage the access right more easily ( filterd at row level by WHERE statement in reporting server ). If in 6 views, I would be managing 6 stored procedure and 6 set of access rights. Cheers. |
 |
|
|
|
|