two questions regarding a big database table

[Seraph_summer]

I am a newer to database of SQL. I want to create a website which mainly contains a table, wich may contains 20,000 items. I want to know that whether due to the large table, then perhaps the speed of the website will be very slow for the user to request some information from this table? if so, if I divide this table into several sub tables, then it would become faster? secondly, between the following two techniques, which one should be better choice for my applicaiton (I am using ASP.net): 1: using the new ADO.NET data source controls, which are tightly integrated with the GridViewand DetailsView controls in ASP.net. 2: involves using the SqlDataAdapter class in conjunction with the DataTable,DataView, andDataSet classes. any expert can give me one hint? thank you!

[David Mujica]

20,000 items in a table is not terribly large for a database engine, so you should be fine with response time. The main thing to remember is that a good design will give the best performance. You should research topics like "database normalization and design". I would only split the data into sub tables where it makes sense. For example you may have a customer table which contains the customer ID and address and an Orders table which refers to the customer number; this way you don't store the customer address for each order created. (This is part of good database design) Relative to the two techniques you mention, 1: using the new ADO.NET data source controls, which are tightly integrated with the GridViewand DetailsView controls in ASP.net. 2: involves using the SqlDataAdapter class in conjunction with the DataTable,DataView, andDataSet classes. Look at the following article by Microsoft: http://msdn.microsoft.com/en-us/library/aa581778.aspx[^] Look around the MSDN site for all kinds of helpful "How To" articles and videos.:thumbsup:

[Mycroft Holmes]

I think Davids answer is excellent, except 20,000 rows in a SQL database is miniscule, we have systems with 20 million rows. The trick is not returning all 20k rows to the user, this is the UI design, only show them the minimum number of rows to meet their needs. Check out tuning and index design, get to know your database. As for using the MS tightly integrated adapters and strongly typed datasets I loathe these constructions, the developer (new) has no real understanding of what is happenning. A large number of post on these forums are cries for help from new devs who cannot customise their data because they are using a wizarded widget they learnt in the tutorials. By all means use the tutorials but remember they are only the FIRST step, you are going to need a deeper knowledge to become proficient.

Never underestimate the power of human stupidity RAH