Quick question. I read this in the article: "Don't nest the views and join views to views"
If you have to rely on getting data from a previous view in order to proceed with a query in a following view, is there a better way of doing that? I'm new to SQL Server, so I'm still learning. I have a query that relies on a couple of other views, and its about a 5-6 level nested view.
Obviously, I can't speak to why the OP posted this.
I advise my developers against it (but it's not a rule), because often multiple views can use some of the same tables. What can happen is the same table(s) being joined in multiple times, potentially significantly decreasing performance.
Stylistically, some developers dislike keeping too much logic in views because they have to dig into views every time they want to fix a query, just to understand the logic of the views. I don't personally have a problem with them at all, but I mostly only use them as a convenience in a highly normalized environment or as a layer of abstraction in an application back-end.