I can only guess that the problem is related to some sort of index corruption – maybe it gets out of sync with the actual data store. In any case, when I run the sdf file through Repair in SSMS, the first query starts returning the correct row. The id column is uniqueidentifier, so it's not related to casing etc. Actually, when you select all rows from the table you can see that this row indeed exists in the db. NET Compact Framework app that we are running every once in a while we get into a situation where the following statement returns no rows select * from order_item where id = '043740d1-c6d0-4fd4-ae84-fdb9218f8b81' I'm looking for a cause of a really strange case of SQL Server Compact db corruption.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |