Eko Budiharto wrote:
Hi,
I would like to ask about the size that can be handled by mysql. How big if I
use innoDB? How big with myISAM?
Quoting from the manual "65536 terabytes"
http://dev.mysql.com/doc/refman/5.0/en/table-size.html
Try 5 minutes of searching the manual next time.
Ruslan Spivak <[EMAIL PROTECTED]> wrote on 21/06/2004 12:22:04:
> I have quite big database - around 15Gb(~ 180 million of rows).
> My problem is that after deleting 70million of rows(with 'delete from'
> statement) database file size didn't decrease - it's still 15Gb.
>
> Can anybody give me adv
Dear Friends
First thanx for all of to ans me but
I feel that i put the question in wrong way.
Actually i created 5 databases other than default one that is mysql and test
I created the 5 different database for my client and i want to resitrct them for
particulary size limt.
So is this possibl
On Thu, Mar 27, 2003 at 02:35:18PM -0600, Jeff Kilpatrick wrote:
> It's also interesting to note that it's possible to split innodb data
> between multiple files to have databases larger than the OS's max file
> size.
The theoritical maximum table size for the various storage engines is:
BDB
On Thu, Mar 27, 2003 at 12:54:49PM -0800, Dathan Vance Pattishall wrote:
> ISAM tables have a 4GB limit myISAM tables do not have a filesize limit.
> There is a big difference between ISAM and myISAM.
Ah, okay. I read ISAM as MyISAM. Sorry. :-(
Who's still using ISAM anyway? :-)
Jeremy
--
Jer
ot an irrelevant consideration.
-Original Message-
From: Jeremy Zawodny [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2003 12:30 PM
To: Dathan Vance Pattishall
Cc: [EMAIL PROTECTED]
Subject: Re: database size
On Thu, Mar 27, 2003 at 12:17:45PM -0800, Dathan Vance Pattishall wrote:
> ISA
On Thu, Mar 27, 2003 at 12:17:45PM -0800, Dathan Vance Pattishall wrote:
> ISAM tables are cut off at 4gb of data
No, they aren't. I have a 9GB MyISAM table here. By using a MAX_ROWS
specifier, you can suggest that MySQL use larger row pointers (more
than 4 bytes).
> MYISAM / INNODB /BDB have a
It's also interesting to note that it's possible to split innodb data
between multiple files to have databases larger than the OS's max file
size.
-jeff
On Thu, 2003-03-27 at 14:17, Dathan Vance Pattishall wrote:
> ISAM tables are cut off at 4gb of data
> MYISAM / INNODB /BDB have a filesystem lim
ISAM tables are cut off at 4gb of data
MYISAM / INNODB /BDB have a filesystem limit.
I suggest to limit the maximum size of data file: find out if reiserfs
can set a limit on files sizes. I know that EXT3 a few revisions ago
could not go past 2GB per file. Or prune your data so it doesn't get to
bi
Sunil-
Seems the easiest way to restrict the size of everything except
privilege tables is to use nothing but InnoDB tables. You can set the
default table type using --default-table-type=InnoDB when launching
mysqld.
If you're not keen on that, you may want to look into using a quota on
your mys
On Mon, Jan 14, 2002 at 11:52:35AM -0800, Aaron Brick wrote:
> in specific reference to linux, you are speaking of the 2.4 kernel,
> glibc 2.2, and ext{2,3} filesystem? is it the case that large files
> are correctly addressed (ie, seamlessly) on such systems?
Yes.
--
Jeremy D. Zawodny, <[EMAIL
in specific reference to linux, you are speaking of the 2.4 kernel, glibc
2.2, and ext{2,3} filesystem? is it the case that large files are correctly
addressed (ie, seamlessly) on such systems? this is the impression i have
got from the limited research i've done.
looking for a generalized soluti
Oganes,
are your really using disk partitions as InnoDB data files? If you use raw
disk partitions, then the operating system may put a limit on the number of
them, for example, 16.
But usually InnoDB data files will be just ordinary files of the file
system. The number of data files is restrict
I disagree. The 4GB slowdown is usualy caused by indexing problems
associated with the OS having increased overhead when looking up and
inserting data. I have eliminated this slowdown in Solaris and Linux be
re-indexing the entire database once it becomes larger then 4GB. This
fixes the problem
The size limitation is becauseof the operating system parameters. In
order to use tables larger then 3 GB, use either Redhat 7.2 or Solaris 8.
These operating systems allow file sizes greater then 2 GB. For the most
part I achievedtables sizes using these operating system of greater the 50
GB.
This is speculation:
They're slower because many operations have to be done using 64 bit
values rather than 32 bit values. You set the flag by setting the max
data size when creating the table. You can also alter this after the
table is created with ALTER TABLE. The doc suggests you're settin
> Yes and no. With 3.23, the MyISAM format will, by default, have a 4GB
> limit (32 bits). You can set flags on the table to allow a 64-bit table,
> and you'll generally hit an OS or physical limitation long before you
> run out of space. The downside of the 64-bit version is it's considerably
On Thu, 10 Jan 2002, Dan Nelson wrote:
> In the last episode (Jan 11), Manish Mehta said:
> > As we know that MySql support maximum of 4 GB data per table.
>
> Actually, http://www.mysql.com/doc/T/a/Table_size.html says that only
> Mysql 3.22 had a 4gb table size. With 3.23, the real limit is h
Hello everyone,
I guess I have the similar question, that has been brought up.
I have 36 InnoDB tables, and I have allocated two 2GB partitions for my data.
Provided I have very big hard drive, how many partitions at 2GB each could I allocate?
As many as my hard drive can handle?
I also have
In the last episode (Jan 11), Manish Mehta said:
> As we know that MySql support maximum of 4 GB data per table.
Actually, http://www.mysql.com/doc/T/a/Table_size.html says that only
Mysql 3.22 had a 4gb table size. With 3.23, the real limit is how big
a file your OS can handle.
--
Dan
Hi,
For most of the platforms Mysql has reasonably enough
space for each table itself(in GB).Database wise, also
there should not be any problem for the database size
you are mentioning.For sure,I can say that I have not
worked on Mandrake.But, I feel the size you have
mentioned should not be a pr
Well, my server is running on Mandrake 8.0. We're trying to implement
database hosting at our site, therefore people should probably have
database spaces between 10-50 MB.
In Microsoft SQL server you can limit the size of a database when
creating it. Is it possible in MySQL ?
VVM Ravikum
No need to worry.On NT each table can have
upto4GB.Database there is predefined limit.It can go
even upro 20GB or more also.
--- Ali Kemal YURTSEVEN <[EMAIL PROTECTED]>
wrote: >Hi,
>
> I'm new in this list and new to MySQL also. What I
> want to know is how
> to limit the size of a
RedHat 7.1 uses kernel 2.4, which *does not* have a file size
limitation of 2Gb.
I have a few tables bigger than 2Gb (3.23.37 / RedHat 7.1)
It takes forever to index them, though...
Vadim.
Dhiin Data - Erik Dhiin wrote:
>
> Hi,
>
> I have a problem, my database has reached Linux Redhat 7.1
> > > Hi,
> > >
> > > I have a problem, my database has reached Linux Redhat 7.1
> > > max file size. (2147483647 Bytes). Does eny one know what i
> > > can do to make a lager database. (lager
> > > filesystem)
> > >
> > > Thanks
> > > Erik Dhiin
I myself run a 300Gb database on a Linux redhat 6
Erik,
You mentioned 40Gig files on Intel platform -
what OS/DBMS did you use then? How about the performance?
Thanks,
Vadim.
Terry Katz wrote:
>
> Erik,
> If your running Linux on an Intel machine (which I assume it is), then
> you've hit Linux's limit for IA32 and 2.2.x kernels .. If you w
Erik,
If your running Linux on an Intel machine (which I assume it is), then
you've hit Linux's limit for IA32 and 2.2.x kernels .. If you want to go
with sizes higher then 2gig you need to upgrade to a 2.4 kernel (and the
latest GNU Libc) .. I've had (not mysql databases) 40gig files on Intel
b
I run Linux 6.2 and don't have problems with file size. Check the version
of MySQL you run. The maximum table size was recently expanded in 3.23.x I
think. Also, look at the MAX_ROWS parameter for the table. Finally, if
nothing else works perhaps you can define the table as a UNION, check the
Hi.
First, there is somewhere a chapter about disk usage in the manual
(too lazy to look it up).
On Fri, Feb 09, 2001 at 09:51:03AM -0500, [EMAIL PROTECTED] wrote:
> I was wondering if someone could help advise me on calculating
> database size estimations. Assume the following table:
>
> Field
29 matches
Mail list logo
