I have a table with 30 columns and about 3.4 million records. Is it reasonable for SELECT * FROM [Table]; to take 8 to 12 minutes to return all 3.4 million results?
If not, where’s a good place/resource to begin diagnosing my problem?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a table with 30 columns and about 3.4 million records. Is it reasonable for SELECT * FROM [Table]; to take 8 to 12 minutes to return all 3.4 million results?
If not, where’s a good place/resource to begin diagnosing my problem?
It’s most likely that SQL server is doing its best to get the data you asked for.
It’s not unreasonable to assume at least 1K/record for 30 columns.
3.4M x 1K = 3.4Gb.
Just reading 3.4Gb from the disk could take minutes on an average machine (do not forget that this is not just reading, there’s obviously some SQL processing overhead in it.
But of course in a real world scenario you don’t want to retrieve all the data…