swilson
Posts: 84
|
| Posted: 10/12/2005, 11:10 PM |
|
Please share your tips to speed the processing of record grids.
I am using Access, asp.net. One example of a very slow update is a many to many grid update bewteen one table of 5,000 records and another of 300 records where there are 100 matches between the two.
Another grid that takes a long time to submit is 5 columns, 50 rows, connected to a table of 300 records.
What could be taking 5 minutes for the browser to submit? I had to lengthen the timeout of the server.
THANKS!
_________________
It continues to amaze me, how often the solutions to seemingly complex problems are so very simple. |
 |
 |
Edd
Posts: 547
|
| Posted: 10/13/2005, 6:04 AM |
|
It is your database. Re-Engineer your tables OR switch MSAccess to MySQL or MSSQL.
You can convert from MSAccess quite easily.
You will eventually have to dump MSAccess as it is obsolete except for the desktop products.
Sorry
Edd
_________________
Accepting and instigating change are life's challenges.
http://www.syntech.com.au |
|
|
|
swilson
Posts: 84
|
| Posted: 10/13/2005, 6:53 AM |
|
Okay, I'm convinced to take the plunge.
I own my server running Windows Server 2003, and presently installed is SQL Server Developer Edition ver 8.00.194 (RTM)
What are the limitations of using this database to develop and implement the switch?
THANKS!
_________________
It continues to amaze me, how often the solutions to seemingly complex problems are so very simple. |
|
|
|
Walter Kempees
|
| Posted: 10/13/2005, 6:59 AM |
|
Barging in: no disadvantage except for pricing.
Edd's approach will work as well with MSSql Oracle or any other major Db.
It's Access that is the problem.
"swilson" <swilson@forum.codecharge> schreef in bericht
news:2434e66c16c6ac@news.codecharge.com...
> Okay, I'm convinced to take the plunge.
>
> I own my server running Windows Server 2003, and presently installed is
> SQL
> Server Developer Edition ver 8.00.194 (RTM)
>
> What are the limitations of using this database to develop and implement
> the
> switch?
>
> THANKS!
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
Edd
Posts: 547
|
| Posted: 10/13/2005, 7:27 AM |
|
If you are using MSAccess you can upgrade the DB using the upgrade facility to a MS Project. There is always a bit of cleaning up to do but it will get you started.
Good Luck
Edd
_________________
Accepting and instigating change are life's challenges.
http://www.syntech.com.au |
|
|
|
swilson
Posts: 84
|
| Posted: 10/13/2005, 7:35 AM |
|
Thanks the input!
_________________
It continues to amaze me, how often the solutions to seemingly complex problems are so very simple. |
|
|
|
E43509
Posts: 283
|
| Posted: 10/13/2005, 8:50 AM |
|
Moving to an upscale db may help some but the db design should have a look-see first. Are there indexes on those columns, are there primary keys, Are you using a primary key or indexed field to do the update/insert
I use MS access for some systems and have not found any response issues unless I didn't optimize the structure first. Moving to another db engine without putting in the proper indexes probably won't help
|
|
|
|
swilson
Posts: 84
|
| Posted: 10/13/2005, 9:09 AM |
|
Good suggestions. I believe I have been careful about this, but will confirm.
_________________
It continues to amaze me, how often the solutions to seemingly complex problems are so very simple. |
|
|
|
