Y
yooper_ssm
Equipment:
We are using a gigabit network with static IPs to each workstation
Server is Win2K Server
Workstation is XP Pro and or 2K Pro
Problem:
The data bases are located on the server. The forms are accessed from
workstations via access or access runtime. We have been dealing with the
databases being really slow. So today I thought I would rebuild a database
and try to weed out some of the data that is not needed to see if I can speed
the thing up. Well after I deleted all forms but one, all queries and
reports. I then deleted all non-essential tables - i.e. indexing tables.... I
have a table that contains the first and last day of every week of 2005 with
the year and week number - total number of datum is 208. I noticed it still
takes 5 seconds for it to open. I then created a new database and pasted the
information from this table into it, and it opens up just like is should -
very fast. I then opened up the database I was originally editing and deleted
all of the "Linked" tables and the performance of the table went from 5
seconds to instant. The table that I'm opening contains no lookup fields or
anything of that nature. So to kind of start this experiment over I started a
new database and imported the problem table opened it and again it opened
instantly. I imported the other table using the link option, and the
performance of the table degrades back to 5 seconds. I know 5 seconds is not
a lot of time but sometimes in the middle of the day the forms can and have
taken up to 5 minutes to open.
Question:
Is there a setting in access like snapshot record set or something of this
nature that would speed these tables up?
Why would this slow down the performance of a table that has absolutely
NOTHING to do with it?
It's like the database has to read all of the tables in order to display the
information from one!
Thanks
Mike Sundman
We are using a gigabit network with static IPs to each workstation
Server is Win2K Server
Workstation is XP Pro and or 2K Pro
Problem:
The data bases are located on the server. The forms are accessed from
workstations via access or access runtime. We have been dealing with the
databases being really slow. So today I thought I would rebuild a database
and try to weed out some of the data that is not needed to see if I can speed
the thing up. Well after I deleted all forms but one, all queries and
reports. I then deleted all non-essential tables - i.e. indexing tables.... I
have a table that contains the first and last day of every week of 2005 with
the year and week number - total number of datum is 208. I noticed it still
takes 5 seconds for it to open. I then created a new database and pasted the
information from this table into it, and it opens up just like is should -
very fast. I then opened up the database I was originally editing and deleted
all of the "Linked" tables and the performance of the table went from 5
seconds to instant. The table that I'm opening contains no lookup fields or
anything of that nature. So to kind of start this experiment over I started a
new database and imported the problem table opened it and again it opened
instantly. I imported the other table using the link option, and the
performance of the table degrades back to 5 seconds. I know 5 seconds is not
a lot of time but sometimes in the middle of the day the forms can and have
taken up to 5 minutes to open.
Question:
Is there a setting in access like snapshot record set or something of this
nature that would speed these tables up?
Why would this slow down the performance of a table that has absolutely
NOTHING to do with it?
It's like the database has to read all of the tables in order to display the
information from one!
Thanks
Mike Sundman