SQLserver on Small Business Server for Win 2003.
Client application updates records in DB. i.e. the content of a field is
updated from "First" to "Second"
Client application closed and opend again. DB returns value "Second".
Next morning _SOME_ - not all - of the updates seems missing. DB returns
the value "First"

The client software has run for years i several thousand installations,
with MSDE/SQLserver on w2k and 2003 servers.
This is the first time we have seen this spooky behavior. And it is the
first time we are targeting SBS.

Could there be some unflushed cache between client and SQLserver?


Poul Petersen

Poul Petersen (psp@tech-p.dk) writes:
> SQLserver on Small Business Server for Win 2003.
> Client application updates records in DB. i.e. the content of a field is
> updated from "First" to "Second"
> Client application closed and opend again. DB returns value "Second".
> Next morning _SOME_ - not all - of the updates seems missing. DB returns
> the value "First"
>
> The client software has run for years i several thousand installations,
> with MSDE/SQLserver on w2k and 2003 servers.
> This is the first time we have seen this spooky behavior. And it is the
> first time we are targeting SBS.
>
> Could there be some unflushed cache between client and SQLserver?

No.

I don't know much about SBS, but I've never heard anything that SBS
would come with some special version of SQL Server.

This behaviour typically has two explanations:
1) Poorly handled query timeouts. If a query times out, no transaction
is rolled back automatically. If the client does not handle this
appropriately, the user may jog along all day with an open transaction.
When he logs out, everything is rolled back.

2) There is simply a process that performs an update in the other
direction.


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

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx