On 30 Mar 2010, at 9:02am, Akbar Syed wrote:
> Unfortunately, I could not think about any other option than to keep
> the devices attached all the time.
I hope you don't have to handle many attachable devices, because SQLite can't
handle more than 30 simultaneous ATTACHes. See section 11 of
>>Make one big 'working' database by reading all the data from the databases on
>>the independent devices and putting it into one big table. Once you have
>>sucked out the data you can disconnect from the device. Then do all your
>>enquiries on this big table. There's a special convenient
On 26 Mar 2010, at 10:47am, Akbar Syed wrote:
> Unfortunately, my application restricts me to use independent
> databases than to a single database
> as each database exists on a different device and contains the info of
> that device in the database.
> Multiple devices are allowed to connect
Hello,
>>If you want to improve utilization memory, just put everything in one
>> database. Each attached database in each connection has its own cache.
>> With that many data sources you're going to get a very uneven distribution
>> of cache utilization, and very high worst-case usage.
On Thu, Mar 25, 2010 at 05:22:04PM +0100, Akbar Syed scratched on the wall:
> I have been trying to improve the performance and memory usage for my
> application whereby i have maximum of 30 databases attached. In total I have
> 31 databases with 30 databases attached to the first one. Each
I have been trying to improve the performance and memory usage for my
application whereby i have maximum of 30 databases attached. In total I have
31 databases with 30 databases attached to the first one. Each database has
a single table with approx 65 columns and the records in each table may go
6 matches
Mail list logo
