This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have a model constructed in VS2010 using LightSpeed Professional (the latest nightly, 20120326) that is then used in a mono 2.10.5 program on ubuntu. I'm using the nightly because I'm looking for the best speed I can get on compiled queries, but will revert to the release build soon to see if it fixes this problem. It's a fairly small model but with lots (>80000) of inserts. Keytable identity generation for all entites except one, which is on identity column. Database is SQL2008 using SqlServer2005 provider. To improve insert performance, the configuration is: identityBlockSize="200" updateBatchSize="x" Where "x" has been varied, as it seems to relate to the problem. Originally x=30. The problem is this exception being raised when I do a uow.SaveChanges()... System.Data.SqlClient.SqlException: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 29 ("@p2î"): Data type 0x01 is unknown Sometimes the unknown data type is 0x08. Reducing the updateBatchSize seems to at least reduce the problem. I have not seen it die with x-1 yet, but with x=30 it dies pretty quick. With x=5 it will go for a good while, and then raise the exception. Help? I'm going to uninstall the nightly and revert to the release build to see if that helps. Daniel. |
|
|
|
|
Same behaviour with the release LS 4.0. updateBatchSize does affect it. Works 100% with my app when UBS=4, dies 100% with UBS=5. Suggests its something to do with the amount of data being buffered for the database. There are reports of similar things both for Mono and Windows: http://lists.ximian.com/pipermail/mono-bugs/2010-July/102503.html Dunno. ?? Daniel. |
|
|
|
|
I believe this is a known issue in Mono, although the detail on what exactly the issue is seems a bit vague. See the bug report here: https://bugzilla.novell.com/showbug.cgi?id=609109 From the commit logs on Github it appears they have reverted this on the trunk late last year, so I am guessing that means it may only be available in 2.11? Possibly in 2.10.8 since that was released in Dec. See the history on: https://github.com/mono/mono/commits/master/mcs/class/Mono.Data.Tds/Mono.Data.Tds.Protocol/TdsComm.cs
|
|
|
|
|
Yup, that sure could be it. The problem is that type of error crops up in a lot of circumstances so it's hard to be sure which symptoms are related to what problem. I will see if I can install mono 2.10.8 and see if the behaviour still exists there. BTW, along the way I spotted that switching between releases of LightSpeed (uninstall A / install B) messed with some of the settings on the properties of my entities. In particular the 'IsNullable' option kept getting reset from True to False. Strange. Daniel. |
|
|
|
