You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Software works very fine with <1GB files, but I have one sqlite, which is 8.6GB and can't open. The question is: is there any limit of sqlite file size? Do you have experience with large files?
if the command line utility can open it, I see no real reason why sqlitebrowser shouldn't be able to.
Until of course there is some sort of bug or we run out of memory while we generate additional table information
But for example the row size shouldn't really hit us, as since 3.0 we added partial table retrieve to not fill up the memory with huge tables.
I have a bunch of data-sets each larger than 1G plus a big one (50G). I tried SQLite Expert and it opens them and scans the data very quickly. So there should be no limit on this I think.
@serden84@renkun-ken Our new release from a few days ago has a 64-bit Windows build. Would you have a few minutes to try it out with your larger data set files?
I run SQLite Version 3.8.10.2 (Qt Version 5.4.1) on windows
I confirm that the software is very slow for files above 200 Mo and crashes when the file exceeds 1 GB.
It would be great if files that do more than 1GB where supported, but at least sqlite should warn the user at start that opening files of more than 1 GB can crash the software.
@ogloo Would you be ok to try our recent (3.7.0) release? The 64-bit version that is. In theory, it should open larger database files without a problem: 😄
The 32 bit version is unlikely to ever load large database files. To load large ones, you must use the 64 bit version. And yeah, I understand that might not be easy. 😦
Yes, the 64 bit version sounds like the right approach here.
But let's not forget the 'x rows affected' thing @ogloo mentioned above as this makes a lot of sense (even though it's a bit off topic in this issue 😃 ). With the latest commit I've just added this feature. Now, it's a bit awkward to say but it'll be available in the next nightly build which - unfortunately - is only available as a 32bit executable...
@ogloo Would you be ok to try tomorrow's nightly build, and let us know if the new UPDATE output is working well for you? (download locations are on the front page of this repo if that helps)
Activity
justinclift commentedon Sep 25, 2014
This may be related to #107.
Unsure how to approach this though for such large file sizes.
justinclift commentedon Sep 25, 2014
Does the command line version of sqlite open this database ok?
Z4us commentedon Sep 26, 2014
http://www.sqlite.org/limits.html
rp- commentedon Sep 26, 2014
if the command line utility can open it, I see no real reason why sqlitebrowser shouldn't be able to.
Until of course there is some sort of bug or we run out of memory while we generate additional table information
But for example the row size shouldn't really hit us, as since 3.0 we added partial table retrieve to not fill up the memory with huge tables.
justinclift commentedon Nov 2, 2014
@serden84 Is this still being a problem for you?
If so, would you have time to try opening the database file with the command line client, to see if that works?
renkun-ken commentedon Dec 8, 2014
I have a bunch of data-sets each larger than 1G plus a big one (50G). I tried SQLite Expert and it opens them and scans the data very quickly. So there should be no limit on this I think.
justinclift commentedon Apr 30, 2015
@serden84 @renkun-ken Our new release from a few days ago has a 64-bit Windows build. Would you have a few minutes to try it out with your larger data set files?
https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/v3.6.0
We're hoping the 64-bit builds work better for large data sets now... 😄
ogloo commentedon Jul 14, 2015
I run SQLite Version 3.8.10.2 (Qt Version 5.4.1) on windows
I confirm that the software is very slow for files above 200 Mo and crashes when the file exceeds 1 GB.
It would be great if files that do more than 1GB where supported, but at least sqlite should warn the user at start that opening files of more than 1 GB can crash the software.
justinclift commentedon Jul 14, 2015
@ogloo Would you be ok to try our recent (3.7.0) release? The 64-bit version that is. In theory, it should open larger database files without a problem: 😄
https://github.com/sqlitebrowser/sqlitebrowser/releases/tag/v3.7.0
ogloo commentedon Jul 15, 2015
I use the 32 bit version actually but it is the latest one 3.7.0.
ogloo commentedon Jul 15, 2015
And by the way in the SQL shell it would be great to have the number of affeted row when you do an update request, Some thing like:
Query executed successfully: UPDATE table SET field = 's' WHERE field2 = 1
(took 81ms, 5 rows affected)
justinclift commentedon Jul 16, 2015
The 32 bit version is unlikely to ever load large database files. To load large ones, you must use the 64 bit version. And yeah, I understand that might not be easy. 😦
ogloo commentedon Jul 16, 2015
So i'll deal with it but thank you for the answers.
justinclift commentedon Jul 16, 2015
Closing this as we introduced large database support on Windows with version 3.6.0 64-bit.
Add 'x rows affected' part to the Execute Query results
MKleusberg commentedon Jul 16, 2015
Yes, the 64 bit version sounds like the right approach here.
But let's not forget the 'x rows affected' thing @ogloo mentioned above as this makes a lot of sense (even though it's a bit off topic in this issue 😃 ). With the latest commit I've just added this feature. Now, it's a bit awkward to say but it'll be available in the next nightly build which - unfortunately - is only available as a 32bit executable...
justinclift commentedon Jul 16, 2015
@MKleusberg Good catch. 😄
@ogloo Would you be ok to try tomorrow's nightly build, and let us know if the new UPDATE output is working well for you? (download locations are on the front page of this repo if that helps)