I am redeveloping an old ecommerce website which is currently written in C# ASP.NET 2.0.

I have the opportunity to develop using whatever language and technique I like.

Because this is a reasonably high volume website and has suffered performance issues I want to develop in the most efficient manner possible.

I am contemplating developing in ASP.NET WebPages (Razor). I also plan to use SqlClient to access the database. As I will be the sole developer and, although I appreciate that future changes are inevitable, I feel that having the UI and data access in the same page/script will be manageable for a site such as this with a small number of pages.

To minimise database trips (using SQL Server 2012), as database performance is the usual bottleneck in the current system, I am looking at creating stored procedures that return everything required for the current page in one query as multiple recordsets. For example the home page query might return the promotional banner image filenames and text, the new release products, the top selling products, etc. Then using SqlDataReader get the data from each recordset as needed and dispose of the connection and reader when the last recordset has been read. I don't plan to use any data transfer objects.

I chose SqlClient over Webmatrix.Data as I can specify command type of stored procedure and specify parameter data types and lengths which I understand improves performance as query plans can be reused.

Will these methods provide maximum performance and are there any issues with the above.

I am redeveloping an old ecommerce website which is currently written in C# ASP.NET 2.0.

Because this is a reasonably high volume website and has suffered performance issues I want to develop in the most efficient manner possible.

To minimise database trips (using SQL Server 2012), as database performance is the usual bottleneck in the current system, I am looking at creating stored procedures that return everything required for the current page in one query as multiple recordsets. 

For example the home page query might return the promotional banner image filenames and text, the new release products, the top selling products, etc. The product page might return the product details, related products, etc.

I can't remember seeing this technique used often if at all. Is returning all data in a single database request more efficient than retrieving the same data in several database requests? Are there any flaws in doing this?

I am redeveloping an old ecommerce website which is currently written in C# ASP.NET 2.0.

I have the opportunity to develop using whatever language and technique I like.

Because this is a reasonably high volume website and has suffered performance issues I want to develop in the most efficient manner possible.

I am contemplating developing in ASP.NET WebPages (Razor). I also plan to use SqlClient to access the database. As I will be the sole developer and, although I appreciate that future changes are inevitable, I feel that having the UI and data access in the same page/script will be manageable for a site such as this with a small number of pages.

To minimise database trips (using SQL Server 2012), as database performance is the usual bottleneck in the current system, I am looking at creating stored procedures that return everything required for the current page in one query as multiple recordsets. For example the home page query might return the promotional banner image filenames and text, the new release products, the top selling products, etc. Then using SqlDataReader get the data from each recordset as needed and dispose of the connection and reader when the last recordset has been read. I don't plan to use any data transfer objects.

I chose SqlClient over Webmatrix.Data as I can specify command type of stored procedure and specify parameter data types and lengths which I understand improves performance as query plans can be reused.

Just looking for opinions on whether these methods will provide maximum performance or any issues with the above.

I am redeveloping an old ecommerce website which is currently written in C# ASP.NET 2.0.

I have the opportunity to develop using whatever language and technique I like.

Because this is a reasonably high volume website and has suffered performance issues I want to develop in the most efficient manner possible.

I am contemplating developing in ASP.NET WebPages (Razor). I also plan to use SqlClient to access the database. As I will be the sole developer and, although I appreciate that future changes are inevitable, I feel that having the UI and data access in the same page/script will be manageable for a site such as this with a small number of pages.

To minimise database trips (using SQL Server 2012), as database performance is the usual bottleneck in the current system, I am looking at creating stored procedures that return everything required for the current page in one query as multiple recordsets. For example the home page query might return the promotional banner image filenames and text, the new release products, the top selling products, etc. Then using SqlDataReader get the data from each recordset as needed and dispose of the connection and reader when the last recordset has been read. I don't plan to use any data transfer objects.

I chose SqlClient over Webmatrix.Data as I can specify command type of stored procedure and specify parameter data types and lengths which I understand improves performance as query plans can be reused.

Will these methods provide maximum performance and are there any issues with the above.

I am redeveloping an old ecommerce website which is currently written in C# ASP.NET 2.0.

I have the opportunity to develop using whatever language and technique I like.

Because this is a reasonably high volume website and has suffered performance issues I want to develop in the most efficient manner possible.

I am contemplating developing in ASP.NET WebPages (Razor). I also plan to use SqlClient to access the database. As I will be the sole developer and, although I appreciate that future changes are inevitable, I feel that having the UI and data access in the same page/script will be manageable for a site such as this with a small number of pages.

To minimise database trips (using SQL Server 2012), as database performance is the usual bottleneck in the current system, I am looking at creating stored procedures that return everything required for the current page in one query as multiple recordsets. For example the home page query might return the promotional banner image filenames and text, the new release products, the top selling products, etc. Then using SqlDataReader get the data from each recordset as needed and dispose of the connection and reader when the last recordset has been read. I don't plan to use any data transfer objects.

Just looking for opinions on whether these methods will provide maximum performance or any issues with the above.

I am redeveloping an old ecommerce website which is currently written in C# ASP.NET 2.0.

I have the opportunity to develop using whatever language and technique I like.

Because this is a reasonably high volume website and has suffered performance issues I want to develop in the most efficient manner possible.

I am contemplating developing in ASP.NET WebPages (Razor). I also plan to use SqlClient to access the database. As I will be the sole developer and, although I appreciate that future changes are inevitable, I feel that having the UI and data access in the same page/script will be manageable for a site such as this with a small number of pages.

To minimise database trips (using SQL Server 2012), as database performance is the usual bottleneck in the current system, I am looking at creating stored procedures that return everything required for the current page in one query as multiple recordsets. For example the home page query might return the promotional banner image filenames and text, the new release products, the top selling products, etc. Then using SqlDataReader get the data from each recordset as needed and dispose of the connection and reader when the last recordset has been read. I don't plan to use any data transfer objects.

I chose SqlClient over Webmatrix.Data as I can specify command type of stored procedure and specify parameter data types and lengths which I understand improves performance as query plans can be reused.

Just looking for opinions on whether these methods will provide maximum performance or any issues with the above.