Multi connection problem

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.

MSSQL with one or more users

People, can u in few words explain to me which method is better: to use MSSQL own auth system - logins or to use one login for connection and make own auth subsystem?
Of course both methods works but i wanna know pluses and minuses of both methods.

RegardsIt is not a right question to ask it depends on level of security you want to achieve.

In case of a windows authentication:
If I, for example, logged in to my computer and left the room, anyone can stop by and get into the database. But on the other hand you dont have to do anything to get to the database. Users who got rights because they need to use some applications that connect to the database can easily get to the server itself and change any data they want on the back end. Some of them really think that they are very smart and know what they do. Especially when they try to update\delete with no WHERE condition or just do counts on millions of records (this can use up all server resources and stop the server from responding).

In case of a password protection:
If you have password protected login it is harder to get to the server you need to know a password. Also in very secure and protected environments (I work in one) password can be provided through a front end applications where they hashed before actually logging in to SQL Server. So in this case regular user doesnt even know his actual password to get to the server directly and each action of such user can be monitored and recorded.

So in first case it is less secure but much easier.
In second case it is opposite more secure but harder to get to the server.

It is the same as your mail box. Do you want your friends or relatives being able to get to your mail or you would put a password and will protect it from nosy readers.

Hope I answered your question.