Inconsistent Database Performance

Hi,

I am facing a peculiar problem while looking ahead in a live Database
currently under operation in one of my clients Project. An
Application that is updating 3 - tables in the Database is missing to
update a certain number of Fields in one of the Tables. The fact is
not frequent and I have checked through the Server Performance Monitor
that there is no performance slag of the Server during any point of
time.

The Tables are indexed with common Key fields. Can anybody help me in
this regard ?

Thanks & Regards.

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/General-Dis...pict193836.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=655931"gangulyarindam" <UseLinkToEmail@.dbForumz.com> wrote in message
news:42010bd1$1_5@.alt.athenanews.com...
> Hi,
> I am facing a peculiar problem while looking ahead in a live Database
> currently under operation in one of my client's Project. An
> Application that is updating 3 - tables in the Database is missing to
> update a certain number of Fields in one of the Tables. The fact is
> not frequent and I have checked through the Server Performance Monitor
> that there is no performance slag of the Server during any point of
> time.
> The Tables are indexed with common Key fields. Can anybody help me in
> this regard ?
> Thanks & Regards.
> --
> Posted using the http://www.dbforumz.com interface, at author's request
> Articles individually checked for conformance to usenet standards
> Topic URL:
> http://www.dbforumz.com/General-Dis...pict193836.html
> Visit Topic URL to contact author (reg. req'd). Report abuse:
> http://www.dbforumz.com/eform.php?p=655931

You can use Profiler to see exactly what commands the application is sending
to MSSQL - sometimes an application may not be doing what you think it is,
especially if it builds SQL strings dynamically.

If that doesn't help, you would need to give some more information about
your environment and exactly what is going wrong.

Simon|||gangulyarindam (UseLinkToEmail@.dbForumz.com) writes:
> I am facing a peculiar problem while looking ahead in a live Database
> currently under operation in one of my client's Project. An
> Application that is updating 3 - tables in the Database is missing to
> update a certain number of Fields in one of the Tables. The fact is
> not frequent and I have checked through the Server Performance Monitor
> that there is no performance slag of the Server during any point of
> time.
> The Tables are indexed with common Key fields. Can anybody help me in
> this regard ?

There is far too little information to give much useful advice. But
it certainly sounds like an application problem to me. Maybe there is
some bad error handling. Maybe you have a poor transaction scope, so
that the update is carried out partly.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Inconistent time out error during update operation.

Using our ASP.net application we are getting inconsistent results when we are trying to update a table with more than 15 update queries sequentially.

We are using Merge replication in our SQL server database. On updating one row, it invokes a trigger to update another table and one more trigger for the merge replication. At only few
instances, the update operation fails and it reports "Time out expired" error.

We are not able to simulate this error in the Test environment since it does not have replication. Can any one help me in resolving this issue.

Please advise .

Hi Krithi,

Is this SQL 2000 or SQL 2005?
Would the updates be touch a lot of rows? If so, I can understand the timeout because, it seems like there are multiple triggers here and also replication adds its own triggers on the tables. That bing the case, if the number of rows touched are large, timeouts can occur.

And are you doing the update operations through isqlw/Management Studio?
If so, can you increase the timeout value in the options in isqlw/Management Studio and try again?