Max Size Before Going SQL Server?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DaveK - 29 Jun 2005 19:16 GMT

In practice, what is the cutover point where we would want to go to SQL
Server? I have a user with two Access databases, one is 850MB and one is
1.02GB in size, after compaction. Both are on drives mapped to a Win2K
server. Her queries take hours to run. There are a couple of million rows
in her favorite tables. Should she move this app to SQL Server? The
application does lots of summing of data over time, not individual lookups.

Reply to this Message

John Nurick - 29 Jun 2005 20:49 GMT

Hi Dave,

It sounds as if the queries are having to pull a lot of data across the
network. In that case, you should see a big increase in speed just by
copying the mdb files to a local drive and working with them there.

If that's not satisfactory, it sounds like time for SQL Server, taking
care to get as much of the processing as possible done on the server.

>In practice, what is the cutover point where we would want to go to SQL
>Server? I have a user with two Access databases, one is 850MB and one is
>1.02GB in size, after compaction. Both are on drives mapped to a Win2K
>server. Her queries take hours to run. There are a couple of million rows
>in her favorite tables. Should she move this app to SQL Server? The
>application does lots of summing of data over time, not individual lookups.

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.

Reply to this Message

debsumrall - 29 Jun 2005 21:06 GMT

be sure you are compacting your database regularly. This will cut the size
and speed up processes

> Hi Dave,
>
[quoted text clipped - 16 lines]
>
> Please respond in the newgroup and not by email.

Reply to this Message