Devart Forums

I was wondering performance wise which one is better to use using 3.50 and visual studio 2005. Also what type of concurrency checking to use when using these data objects. Will using the compression protocol on your wonderful provider help speed things up a bit or not ?

I was wondering performance wise which one is better to use using 3.50 and visual studio 2005.

We behave the same way as standard ADO.NET components.

Also what type of concurrency checking to use when using these data objects.

Use default - Optimistic Locking.

Will using the compression protocol on your wonderful provider help speed things up a bit or not ?

Compressing data leads to reducing network traffic, in exchange for CPU usage on both client and server sides. To obtain performance gains, use Compress property when transferring BLOB fields.

With the optimistic locking do i need to make a time stamp field on each table or am i thinking of something else. Does the command builder and table adapter both use optimistic locking by default ?

For optimistic locking you may include all table fields in the key fields.

Thanks for your help i did some research on the commandbuilder and what i have concluded its probally better to use the table adapter to pre generate the statements for that table. Also did some research on optimistic locking and it seems like a good practice, and a timestamp field is not needed with it. Does MySQL server 5.0 i believe turns compression on by default ?

No. It fully depends on connection options.