Hi all,
In my accounting application if one user tries to execute a long report that
my take several minutes, the other users who are entering invoices almost
hang, and the process of enter products into the invoices or the saving the
invoices slow down significantly.
I'm using VC++ 2003, ODBC, SQL 2000 Ent.
Any body know how to overcome this problem.
Thanks in advance.You could try running the report query inside a transaction with READ
UNCOMMITTED isolation level.
The next time the report runs, take a look at the locks in the database. If
there are a lot of locks, running the report under READ UNCOMMITTED should
help.
"ATS967" wrote:
> Hi all,
> In my accounting application if one user tries to execute a long report th
at
> my take several minutes, the other users who are entering invoices almost
> hang, and the process of enter products into the invoices or the saving th
e
> invoices slow down significantly.
> I'm using VC++ 2003, ODBC, SQL 2000 Ent.
> Any body know how to overcome this problem.
> Thanks in advance.|||A seperate reporting database would solve this. A simple solution is to
restore a backup of the production db with a different name on a nightly
basis. Data is a day old but that's usually OK for reporting. If you mark th
e
reporting db read-only it will speed up those reports too.
"ATS967" wrote:
> Hi all,
> In my accounting application if one user tries to execute a long report th
at
> my take several minutes, the other users who are entering invoices almost
> hang, and the process of enter products into the invoices or the saving th
e
> invoices slow down significantly.
> I'm using VC++ 2003, ODBC, SQL 2000 Ent.
> Any body know how to overcome this problem.
> Thanks in advance.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment