MikeDutcher
Technical User
I am an actuary. My computer skills are concentrated in application development, bare bones in setting up systems.
I have a million record ACCESS 2000 table. (I have many multi-million record tables coming down the road.)
Others have said ACCESS unstable for large tables, get SQL SERVER.
Now I have ACCESS 2000 & SQL SERVER 2000.
I used upsizing wizard to upsize the large ACCESS table to SQL. After applying MS patches, setting up mixed-mode authorization & changing a registry setting, all went well.
ACCESS 2000 now links to this SQL SERVER 2000 table.
I ask ACCESS 2000 to go to the last record. (seems simple)
16 minutes pass, I get a "system resource exceeded" error & the row # is about 700,000.
I work for a NYS agency. The server is cutting edge, my client pc likewise. I do not lack for system resources.
I suspect that some setting is stifling me.
ANY SUGGESTIONS?
I have a million record ACCESS 2000 table. (I have many multi-million record tables coming down the road.)
Others have said ACCESS unstable for large tables, get SQL SERVER.
Now I have ACCESS 2000 & SQL SERVER 2000.
I used upsizing wizard to upsize the large ACCESS table to SQL. After applying MS patches, setting up mixed-mode authorization & changing a registry setting, all went well.
ACCESS 2000 now links to this SQL SERVER 2000 table.
I ask ACCESS 2000 to go to the last record. (seems simple)
16 minutes pass, I get a "system resource exceeded" error & the row # is about 700,000.
I work for a NYS agency. The server is cutting edge, my client pc likewise. I do not lack for system resources.
I suspect that some setting is stifling me.
ANY SUGGESTIONS?