EnitySpaces: the same Query can be used to save multiple tables

I wanted to minimize number of calls to the database, but get back results of dynamic query for small number of columns, as well as detailed data(e.g Itinerary table and Itinerary joined with Itinerary items) .In EntitySpaces
I've created a where condition, filled Query and loaded detailed data, then saved the returned table to DataSet.

Then  for the same query I've specified distinct select columns and Load it again(When LINQ will be available, it could be done in memory without extra database call).  Different table was created, that I've added to the same dataset. Below is code snippet:
                VwItinerariesCollection collPendingList = new VwItinerariesCollection();
                VwItinerariesQuery queryFilter = collPendingList.Query;
                queryFilter.AddWhereConditions();//custom code
                 collPendingList.Query.Load();
                 DataTable tbl= collPendingList.ConvertToDataTable();
                tbl.TableName = "ListWithDetailsTable";   
              DataSet  itineraries = new DataSet();
                itineraries.Tables.Add(tbl);
                 queryFilter.DistinctSelectForList();//custom code
                 collPendingList.Query.Load();
                 tbl = collPendingList.ConvertToDataTable();
                 tbl.TableName = "ListTable";
                 itineraries.Tables.Add(tbl);

SQL Server Seminar presented by Kevin Kline

Last week I was on SQL Server Seminar presented by Kevin Kline.
Performance, Baselining, Benchmarking and Monitioring Presentation
Stored Procedure Best Practices Presentation
Surviving the Data Avalanche Presentation
Top 10 Mistakes on SQL Server Presentations

There were a few interesting points.
Causes of performance problems-5%-hardware, 15%-bad database design, 80%-bad application code.
Do not Interleaved DDL and DML -No create/Drop table in the same SP as insert/Select.
Keep transactions as short as possible.Use @@TRANCOUNTor sys.dm_tran_active_transactionsto look for orphaned transactions when entering a new routine.

Set Theory is Better. then rows.Cursors are depricated.
Use table variables,minimize use of tempdb
Again: Set Nocount On
Again: Owner qualify all names (2-part)

Tiered storage:
Active(e.g. RAID10, high RPM speeds).
Near-term older data (e.g. RAID5, middle RPM speeds)
Old, long-term data (e.g. SATA drives - high volume, low RPM speeds)

Related white papers from Quest Site(login probably will be required):

The Top 10 Mistakes on SQL Server
Tuning SQL Statements on Microsoft SQL Server
Finding and Fixing Bad SQL in Microsoft SQL Server 2000
Performance Baselining, Benchmarking, and Monitoring for SQL Server 2000

Microsoft T-SQL Performance Tuning Part 1: Analyzing and Optimizing T-SQL Query Performance on Microsoft SQL Server using SET and DBCC 

Microsoft T-SQL Performance Tuning Part 2: Analyzing and Optimizing T-SQL Query Performance on Microsoft SQL Server using Indexing Strategies  

Microsoft T-SQL Performance Tuning Part 3: Analyzing and Optimizing T-SQL Query Performance on Microsoft SQL Server using Query Optimizer Strategies

Microsoft T-SQL Performance Tuning Part 4: Analyzing and Optimizing T-SQL Query Performance on Microsoft SQL Server using SHOWPLAN Output and Analysis
Virtualization and SQL Server in the Enterprise

«October»
SunMonTueWedThuFriSat
30123456
78910111213
14151617181920
21222324252627
28293031123
45678910