 |
Site Index
- Products
- Download
- Support
- News
- Contact
- Buy online
|
 |
|
Last updated on 2002-05-30
| Problem: |
SQLQuery throws an exception when calling
a stored procedure using blobs |
| Solution: |
Set the BlobTableName to indicate from what table the blobs
should be retrieved. |
|
|
| Problem: |
SQLQuery eats a lot of
memory when having large result sets |
| Solution: |
This is because the result set is locally
cached. If the sets are large you can turn on the
CacheToDisk option. This will do the cacheing to
a temporary file. |
| |
|
| Problem |
When setting the TSQLServer.MaxProcs
property to anything but 25 the application
allocates approx 50 Mb of extra memory. |
| Solution: |
This is a problem with DBLIB. DBLIB allocates
this memory regardless of what you set the
MaxProcs to. Try to redesign the application so
that is uses a maximum of 25 connections by using
the TSQLQuery.CacheAllRecords more frequently. |
| |
|
Home
| News
| Products
| Download
| Support
(C) Component Store Ltd. 2000 |
