SQL Database Too Big?

[Rexolio]

Hi,

I have a table in my SQL Database that has about 40,000 records. I have a form that pulls records from it according to specified criteria. This form was working fine not too long ago. I have been working a lot in that SQL Database, creating tables, exporting records, etc.

Now its taking forever to get the info to display to my ASP. Some people on slower internet connections experience wait times as long as 7 to 10 minutes. And even then sometimes they don't get results. And usually its a matter of trying to pull only 50 - 150 records.

I'm thinking that with all of the work I've been doing I need to compress the tables. If that's not appropriate please let me know.

If it IS what I should do, I have NO idea how to do it and besides doing what I mentioned above, I'm a beginner at SQL and probably won't understand the terminology, so please explain to me as if I'm a 5 year old. I'm going to get a book, but for now I need help in a hurry.

Any other suggestions or troubleshooting would be beneficial too...again, explained in a way that a 5 year old can understand.

Thanks for your help. This site rocks!!!

 

[stoolpigeon]

The size of the table is not the problem. It could be the network,the box your database is on, your query or an indexing issue. There are a lot of things that may be affecting the performance but it doesn't sound like size is one of them.

A database I use right now has tables ranging in size from around 350,000 records to over 12 million records. On the 12 million record tables the size does cause issues at times. On the 350,000 my queries and such are executed quite rapidly. And this is in SQL Server 6.5.

Trying analyzing the queries when they run. Look at the sql itself in the query. And then there's a bunch more you can do.