Connection Issues

Hi,
I am working with a client whose primary software for their firm uses
MS SQL. They have been experiencing frequent issues with data missing
from query windows, or old data that has been deleted or archived
reappearing; the client closes the program and things are back to
normal. In talking with the support staff for the vendor, they assure
me that we have "an ideal enviroment" for running their software, but
are insisisting that the problems the client is experiencing are
"connection issues" and can't have not been able to point me in any
directions to check other than looking at the hardware environment
which they have said is "ideal". Can someone possibly explain what
other places we might look for connection issues? The client is
running SBS 2003 Premium, which includes SQL 2000. We have all
service packs installed on the server and the workstations.
If more info is needed please feel free to ask.
Thanks,
Mike Garoutte
Milwaukee, WII would look for transactions that are not being committed. In
general it is a Bad Thing for a transaction to remain open during any
user activity. It sounds like that is happening, and the connection
is being broken before or without the user doing whatever has to be
done to make the change final.
An alternate explanation would be that they application stages
transactions in other tables before updating the main tables, and the
user is not taking whatever final step there is that applies the data.
Roy Harvey
Beacon Falls, CT
On Tue, 29 Apr 2008 07:03:07 -0700 (PDT), Mike G <mgaroutte@.gmail.com>
wrote:
>Hi,
>I am working with a client whose primary software for their firm uses
>MS SQL. They have been experiencing frequent issues with data missing
>from query windows, or old data that has been deleted or archived
>reappearing; the client closes the program and things are back to
>normal. In talking with the support staff for the vendor, they assure
>me that we have "an ideal enviroment" for running their software, but
>are insisisting that the problems the client is experiencing are
>"connection issues" and can't have not been able to point me in any
>directions to check other than looking at the hardware environment
>which they have said is "ideal". Can someone possibly explain what
>other places we might look for connection issues? The client is
>running SBS 2003 Premium, which includes SQL 2000. We have all
>service packs installed on the server and the workstations.
>If more info is needed please feel free to ask.
>Thanks,
>Mike Garoutte
>Milwaukee, WI|||Hi Ron,
Thanks for your reply. I have to be honest that I am not sure how to
check for uncommitted transactions. When the record is saved, I would
assume it
would be updated in the database. One thing that frequently happens
while editing a record the
staff at the clients office will click the "Save & Close" button to
save the changes to the record and they get a message that the record
has
been deleted by another user, even though the record has not been
deleted. We are putting a gigabit nic in the server Thursday night.
Thanks for your help.
Mike
On Apr 29, 11:52=A0am, "Roy Harvey (SQL Server MVP)"
<roy_har...@.snet.net> wrote:
> I would look for transactions that are not being committed. =A0In
> general it is a Bad Thing for a transaction to remain open during any
> user activity. =A0It sounds like that is happening, and the connection
> is being broken before or without the user doing whatever has to be
> done to make the change final.
> An alternate explanation would be that they application stages
> transactions in other tables before updating the main tables, and the
> user is not taking whatever final step there is that applies the data.
> Roy Harvey
> Beacon Falls, CT
> On Tue, 29 Apr 2008 07:03:07 -0700 (PDT), Mike G <mgarou...@.gmail.com>
> wrote:
>
> >Hi,
> >I am working with a client whose primary software for their firm uses
> >MS SQL. =A0They have been experiencing frequent issues with data missing
> >from query windows, or old data that has been deleted or archived
> >reappearing; the client closes the program and things are back to
> >normal. =A0In talking with the support staff for the vendor, they assure
> >me that we have "an ideal enviroment" for running their software, but
> >are insisisting that the problems the client is experiencing are
> >"connection issues" and can't have not been able to point me in any
> >directions to check other than looking at the hardware environment
> >which they have said is "ideal". =A0Can someone possibly explain what
> >other places we might look for connection issues? =A0The client is
> >running SBS 2003 Premium, which includes SQL 2000. =A0We have all
> >service packs installed on the server and the workstations.
> >If more info is needed please feel free to ask.
> >Thanks,
> >Mike Garoutte
> >Milwaukee, WI- Hide quoted text -
> - Show quoted text -|||DBCC OPENTRAN can be used to find open transactions.
Roy Harvey
Beacon Falls, CT
On Wed, 30 Apr 2008 06:49:22 -0700 (PDT), Mike G <mgaroutte@.gmail.com>
wrote:
>Hi Ron,
>Thanks for your reply. I have to be honest that I am not sure how to
>check for uncommitted transactions. When the record is saved, I would
>assume it
>would be updated in the database. One thing that frequently happens
>while editing a record the
>staff at the clients office will click the "Save & Close" button to
>save the changes to the record and they get a message that the record
>has
>been deleted by another user, even though the record has not been
>deleted. We are putting a gigabit nic in the server Thursday night.
>Thanks for your help.
>Mike
>
>On Apr 29, 11:52 am, "Roy Harvey (SQL Server MVP)"
><roy_har...@.snet.net> wrote:
>> I would look for transactions that are not being committed. In
>> general it is a Bad Thing for a transaction to remain open during any
>> user activity. It sounds like that is happening, and the connection
>> is being broken before or without the user doing whatever has to be
>> done to make the change final.
>> An alternate explanation would be that they application stages
>> transactions in other tables before updating the main tables, and the
>> user is not taking whatever final step there is that applies the data.
>> Roy Harvey
>> Beacon Falls, CT
>> On Tue, 29 Apr 2008 07:03:07 -0700 (PDT), Mike G <mgarou...@.gmail.com>
>> wrote:
>>
>> >Hi,
>> >I am working with a client whose primary software for their firm uses
>> >MS SQL. They have been experiencing frequent issues with data missing
>> >from query windows, or old data that has been deleted or archived
>> >reappearing; the client closes the program and things are back to
>> >normal. In talking with the support staff for the vendor, they assure
>> >me that we have "an ideal enviroment" for running their software, but
>> >are insisisting that the problems the client is experiencing are
>> >"connection issues" and can't have not been able to point me in any
>> >directions to check other than looking at the hardware environment
>> >which they have said is "ideal". Can someone possibly explain what
>> >other places we might look for connection issues? The client is
>> >running SBS 2003 Premium, which includes SQL 2000. We have all
>> >service packs installed on the server and the workstations.
>> >If more info is needed please feel free to ask.
>> >Thanks,
>> >Mike Garoutte
>> >Milwaukee, WI- Hide quoted text -
>> - Show quoted text -