is it normal for a Access query to take forfvckingever?

[HomeBrewerDude]

the database has about 500k records, each with about 30 fields and I am putting limits on 5 fields.

anyways the query is crawling.....

is it me (my query) or is it Access?

 

[Platypus]

"If you have to ask, it's Access" ©

 

[HomeBrewerDude]

Originally posted by: CorporateRecreation
"If you have to ask, it's Access" ©

yeah i know it gets a bad rap, but i haven't gotten around ot learning anything else at the moment.

i plan on learning SQL starting in about 2 weeks.

 

[her209]

Its Oracle.

 

[KLin]

Originally posted by: HomeBrewerDude
the database has about 500k records, each with about 30 fields and I am putting limits on 5 fields.

anyways the query is crawling.....

is it me (my query) or is it Access?

That's a big fusking table. what is it you're trying to do with the query?

EDIT: FYI, wrong forum .

 

[HomeBrewerDude]

Originally posted by: KLin

Originally posted by: HomeBrewerDude
the database has about 500k records, each with about 30 fields and I am putting limits on 5 fields.

anyways the query is crawling.....

is it me (my query) or is it Access?

That's a big fusking table. what is it you're trying to do with the query?

EDIT: FYI, wrong forum .

yeah wrong forum.... i know. but i love you guys so much.


its student test data for LA.

essentially i am pulling out a percentage of students at a certain level, broken out by a mix of demographic variables, school, grade, and test type.

once out, i plan on pivotign it excel and formatting it the way i need to (i have done similar work for another file and should be able to leverage some of that file.)

 

[Shawn]

access sucks. so yes it's probably normal.

 

[KLin]

Originally posted by: HomeBrewerDude

Originally posted by: KLin

Originally posted by: HomeBrewerDude
the database has about 500k records, each with about 30 fields and I am putting limits on 5 fields.

anyways the query is crawling.....

is it me (my query) or is it Access?

That's a big fusking table. what is it you're trying to do with the query?

EDIT: FYI, wrong forum .

yeah wrong forum.... i know. but i love you guys so much.


its student test data for LA.

essentially i am pulling out a percentage of students at a certain level, broken out by a mix of demographic variables, school, grade, and test type.

once out, i plan on pivotign it excel and formatting it the way i need to (i have done similar work for another file and should be able to leverage some of that file.)

Which means you have criteria in many different fields? Does the table have a primary key setup in it?

 

[HomeBrewerDude]

Originally posted by: KLin

Originally posted by: HomeBrewerDude

Originally posted by: KLin

Originally posted by: HomeBrewerDude
the database has about 500k records, each with about 30 fields and I am putting limits on 5 fields.

anyways the query is crawling.....

is it me (my query) or is it Access?

That's a big fusking table. what is it you're trying to do with the query?

EDIT: FYI, wrong forum .

yeah wrong forum.... i know. but i love you guys so much.


its student test data for LA.

essentially i am pulling out a percentage of students at a certain level, broken out by a mix of demographic variables, school, grade, and test type.

once out, i plan on pivotign it excel and formatting it the way i need to (i have done similar work for another file and should be able to leverage some of that file.)

Which means you have criteria in many different fields? Does the table have a primary key setup in it?

i don't think so. I have two tables, and then a link table (comma delimited, roughly 65 MB). i bet you're going to tell me thats why my query is so slow....

let me re-iterate: me = DB newb

and yes, many criteria in many fields.

 

[KLin]

Originally posted by: HomeBrewerDude

Originally posted by: KLin

Originally posted by: HomeBrewerDude

Originally posted by: KLin

Originally posted by: HomeBrewerDude
the database has about 500k records, each with about 30 fields and I am putting limits on 5 fields.

anyways the query is crawling.....

is it me (my query) or is it Access?

That's a big fusking table. what is it you're trying to do with the query?

EDIT: FYI, wrong forum .

yeah wrong forum.... i know. but i love you guys so much.


its student test data for LA.

essentially i am pulling out a percentage of students at a certain level, broken out by a mix of demographic variables, school, grade, and test type.

once out, i plan on pivotign it excel and formatting it the way i need to (i have done similar work for another file and should be able to leverage some of that file.)

Which means you have criteria in many different fields? Does the table have a primary key setup in it?

i don't think so. I have two tables, and then a link table (comma delimited, roughly 65 MB). i bet you're going to tell me thats why my query is so slow....

let me re-iterate: me = DB newb

and yes, many criteria in many fields.

You may want to consider doing an import of the comma delimited file into an access table and having it add a primary key to the table. That may speed up query quite a bit(I think it would, but I've never worked with a CSV file that was 65 megs big in access). It's pretty easy to import a table.

 

[HomeBrewerDude]

will do. i don't know why its a linked table rather than an import. i must of done something goofy.

anyways, thanks for the advice, I will import the file before running another query. can't hurt at least.

thanks!

 

[Rogue]

I'm guessing also that your db is not normalized and broken down in the most efficient manner either. In short, yes, it can take a very long time to parse through a lot of data that is not structured properly.

 

[KLin]

Originally posted by: Rogue
I'm guessing also that your db is not normalized and broken down in the most efficient manner either. In short, yes, it can take a very long time to parse through a lot of data that is not structured properly.

From what the OP is describing, I would venture a guess that he's working with some sort of download from another DB system. So there's not much data normalization that can take place.

 

[pancho619]

If you've tried running the query and it's gotten stuck on several occasions, it probably made the size of the DB bigger. You might want to try Compacting and Repairing the database to bring it back to its original size. This happens to me at work, where sometimes a single DB file gets up to 1.5gb from an original 200mb after many query runs. Give that a try.