The solution is to use SQL views, materialized views, or create a new table that contains only the filtered data the user needs.

Why are there INFOMATION_SCHEMA and catalog views in SQL Server that do very similar things? For example, to retrieve a list of tables in a database, I can do it via sys.tables or INFORMATION ...

Indexed Views were introduced in SQL Server 2000 as an Enterprise Edition feature. The confusion arose in SQL Server 2005 when it appeared that all editions supported Indexed Views.

What does your view look like? SQL Server doesn't like inserting values into "complex" views, iirc.

A reader recently pointed out to me that I could drastically simplify that retrieval code by leveraging SQL views. A SQL view pulls together multiple tables (and selected columns from those tables) ...

DATA step views are very versatile because they can harness the power of SAS DATA step processing, including DO loops and IF-THEN-ELSE statements. DATA step views do not have write capability, that is ...

Peter steals another tip from a reader: Entity Framework isn't just for tables and stored procedures. Leveraging SQL Server views can simplify your code.

Peter steals another tip from a reader: Entity Framework isn't just for tables and stored procedures. Leveraging SQL Server views can simplify your code.