I am using MSSQL + ASP.To load my home page, I have configure my home page code to connect to MSSQL server at least 5 times..I have some Tables like News,Pics,Products,.. in MSSQL Database and I want to insert 5 new fields from each table to mu home page.I wonder is it a right method or not.Another choice

That really depends on the nature of your database and the queries used to access it.

If it's a relational database, some of the queries may be built using joins to access information from multiple tables at once.

The best thing you can do is look at your situation individually (tables, etc.) and figure out how you can combine queries where and when possible.

thanks ADAM,
My question is that, if the amount of table fields effects on the page load elapsed time. Is it better for me to make queries in my DB and then ASP codes read from queries tables in my DB.

again the answers is;

it depends.

is your database table structure normalised to reduce redundant data
are your queries optimised and not using such things as "SELECT * FROM ... "

as adam said,
Can you use JOINs to reduce the number of DB round trips?

plus many other things.

If you mean stored SQL procedures, then in very general terms, yes it can.

Mind you, it would depend on the complexity of the query and the resulting recordset as to how much difference it really would make. And if you ever need to move the database, stored procedures do become a problem.

For the most part, it's not even necessary. 99.99999% of ASP-based sites don't even generate enough traffic to necessitate the use of an SQL Server backend in the first place (if coded properly, which most aren't). I can show you sites that get 100,000 page views per month that work off of an Access backend and you'd never even know it.

By the way, if you are using MS SQL, you can use its Query Analyser to iron out what mechanisms are involved for your SQL statements. For example, it will show you whether your SQL statements are using index or table scan is being used. If you notice that table scan is involved in your SQL execution plan, then you need to add some relevant indexes for your SQL statement to speed things up.