Latency Issues

I'm seeing latency issues with a single user on MSDE. It appears that
data doesn't get persisted to the database for up to 30 minutes. What the
devil could be causing this? These are all new machines running the latest
service packs.
TIA
Tina
Hi
The application is not committing the data until very late. In a bad case,
where the connection to the server gets lost, SQL Server will rollback the
transaction as it is not committed. You can loose a lot of data though this.
In effect, there is a BEGIN TRANSACTION and somewhere further down the line,
maybe by chance (due to developer luck), there is a COMMIT TRANSACTION,
resulting in the data being committed.
Ask the developer to look at his application.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tina Smith" <tb.smith@.earthlink.net> wrote in message
news:uGNS5ZdFFHA.2676@.TK2MSFTNGP12.phx.gbl...
> I'm seeing latency issues with a single user on MSDE. It appears that
> data doesn't get persisted to the database for up to 30 minutes. What
the
> devil could be causing this? These are all new machines running the
latest
> service packs.
> TIA
> Tina
>
sql