76,115 reputation
1177173
bio website
location Jersey City, NJ (USA)
age 50
visits member for 4 years, 1 month
seen 26 mins ago

Mar
23
reviewed Close Oracle user in DBA_USERS_WITH_DEFPWD but not user tables/views
Mar
23
comment Percona Master-Master lag issues
Please post all the options in my.cnf for DB-02
Mar
23
revised Percona Master-Master lag issues
edited tags
Mar
23
reviewed Close Insert Into does not work with multiple rows
Mar
23
reviewed Close Regarding Reindexing
Mar
23
reviewed Close PostgreSQL Error Codes
Mar
23
reviewed Leave Closed Mysql Cluster vs Percona/Maridb Cluster
Mar
22
revised Export all MySQL users
edited tags
Mar
22
revised Export all MySQL users
added 141 characters in body
Mar
22
answered Export all MySQL users
Mar
22
revised Large ibdata file in MySQL
added 2014 characters in body
Mar
22
revised Large ibdata file in MySQL
added 2014 characters in body
Mar
22
comment Large ibdata file in MySQL
Here is an experiment you really need to do: 1) Get another DB Server (Dev or Test), 2) Install MySQL on it, 3) mysqldump the schema and load the schema-only dump into it (no data). 4) run ls -l /var/lib/mysql/ibdata1 | awk '{print $5}'. If the number is near 53687091200 (50G), then you can suspect the data dictionary. I would then be incredibly shocked.
Mar
22
comment Large ibdata file in MySQL
The data dictionary has absolutely nothing to do with ibdata1 growth. I have worked with a client that 800 databases (168 tables / database) with innodb_file_per_table. That's 134,400 tables. The ibdata1 file never surpassed 1G. If no more tables were added and you enable innodb_read_only (dev.mysql.com/doc/refman/5.6/en/…), ibdata1 would never grow because the rollback segments and undo space would never be used. Therefore, the data dictionary has never been, or ever will be, an issue when it comes to file size growth.
Mar
22
revised Large ibdata file in MySQL
edited tags
Mar
22
answered Large ibdata file in MySQL
Mar
21
reviewed Close Is a mySQL or mongoDB relational database scalable for holding 80 GBs of additional logs per day?
Mar
21
comment How to tell MySQL to ignore all indexes for a given query?
@RickJames For InnoDB, you are right in that aspect. The query should do a full pass through the PrimaryKey/Clustered Index anyway, even with my OPTION #1. Your approach should be the same, just more work sculpting the index names into the SELECT using information_schema.
Mar
20
answered How to tell MySQL to ignore all indexes for a given query?
Mar
20
revised Complex query performance in MySQL InnoDB versus MyISAM
added 450 characters in body