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 |
|
osaleh
Starting Member
2 Posts |
 Posted - 2005-02-09 : 11:59:17
|
| In general, is it wise to use views to help with large scale update statement instead of many table join operations?Current problem: Transaction -> ATM -> Merchant -> SalesOrgMy transaction number in the millions, ATMs and Merchant in thousands. Currently to settle my transaction, I need to get information from ATMs, merchant and SalesOrg. I join on all tables and possibly more to do that. Is it better to write a view that have the hierarchy and have only the data I am interested in. This view in my example will link ATM to Merchant to SalesOrg. This way, I would just join my Transaction table to the View and save myself the other join operations. Is this better than joining everything? Are there inherit problems in this approach? Please help. |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2005-02-09 : 12:31:28
|
| It won't help efficiency but might be easier to code.The problem is that you will be restricting yourself to the way you access the tables (or should be as the views should be encapsulating relationships).It will make it more difficullt to optimise and split up queries as the relationships will be hidden in the views.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
|
|
|
Can I use Views in my update query