Database log problem
Permalink
I just downloaded a database of one of my concrete5 websites and noticed the size was over 100Mb. How the in the world is that possible? There are thousands and thousands rows of weird logs...
...
(444878, 1, '2015-10-23', '2015-10-23 17:46:40', 0),
(444879, 1, '2015-10-23', '2015-10-23 17:48:52', 0),
(444880, 1, '2015-10-23', '2015-10-23 17:49:08', 0),
(444881, 1, '2015-10-23', '2015-10-23 17:49:41', 0),
(444882, 293, '2015-10-23', '2015-10-23 17:50:45', 0),
(444883, 226, '2015-10-23', '2015-10-23 17:52:58', 0),
(444884, 172, '2015-10-23', '2015-10-23 17:54:24', 0),
(444885, 126, '2015-10-23', '2015-10-23 17:55:07', 0),
(444886, 1, '2015-10-23', '2015-10-23 17:55:11', 0),
(444887, 132, '2015-10-23', '2015-10-23 17:55:12', 0),
(444888, 293, '2015-10-23', '2015-10-23 17:56:32', 0),
(444889, 1, '2015-10-23', '2015-10-23 17:56:37', 0),
(444890, 124, '2015-10-23', '2015-10-23 17:56:51', 0),
(444891, 124, '2015-10-23', '2015-10-23 17:56:51', 0),
(444892, 172, '2015-10-23', '2015-10-23 17:57:36', 0),
(444893, 224, '2015-10-23', '2015-10-23 18:05:49', 0),
(444894, 360, '2015-10-23', '2015-10-23 18:12:47', 0),
(444895, 1, '2015-10-23', '2015-10-23 18:17:43', 0),
(444896, 126, '2015-10-23', '2015-10-23 18:17:47', 0),
(444897, 1, '2015-10-23', '2015-10-23 18:18:02', 0),
(444898, 190, '2015-10-23', '2015-10-23 18:18:08', 0),
(444899, 363, '2015-10-23', '2015-10-23 18:18:24', 0),
(444900, 192, '2015-10-23', '2015-10-23 18:18:43', 0),
(444901, 1, '2015-10-23', '2015-10-23 18:20:57', 0),
(444902, 293, '2015-10-23', '2015-10-23 18:21:03', 0),
(444903, 1, '2015-10-23', '2015-10-23 18:22:13', 0),
(444904, 367, '2015-10-23', '2015-10-23 18:23:28', 0),
(444905, 1, '2015-10-23', '2015-10-23 18:28:12', 0),
(444906, 131, '2015-10-23', '2015-10-23 18:28:12', 0),
(444907, 366, '2015-10-23', '2015-10-23 18:28:14', 0),
(444908, 191, '2015-10-23', '2015-10-23 18:28:26', 0),
(444909, 192, '2015-10-23', '2015-10-23 18:29:28', 0),
(444910, 238, '2015-10-23', '2015-10-23 18:31:00', 0),
(444911, 1, '2015-10-23', '2015-10-23 18:33:32', 0),
(444912, 126, '2015-10-23', '2015-10-23 18:35:07', 0),
(444913, 131, '2015-10-23', '2015-10-23 18:41:27', 0),
(444914, 191, '2015-10-23', '2015-10-23 18:44:35', 0),
(444915, 191, '2015-10-23', '2015-10-23 18:46:16', 0),
(444916, 172, '2015-10-23', '2015-10-23 18:46:37', 0),
(444917, 192, '2015-10-23', '2015-10-23 18:49:37', 0),
(444918, 1, '2015-10-23', '2015-10-23 18:51:41', 0),
(444919, 126, '2015-10-23', '2015-10-23 18:52:48', 0),
(444920, 192, '2015-10-23', '2015-10-23 18:54:16', 0),
...
What is going on?
...
(444878, 1, '2015-10-23', '2015-10-23 17:46:40', 0),
(444879, 1, '2015-10-23', '2015-10-23 17:48:52', 0),
(444880, 1, '2015-10-23', '2015-10-23 17:49:08', 0),
(444881, 1, '2015-10-23', '2015-10-23 17:49:41', 0),
(444882, 293, '2015-10-23', '2015-10-23 17:50:45', 0),
(444883, 226, '2015-10-23', '2015-10-23 17:52:58', 0),
(444884, 172, '2015-10-23', '2015-10-23 17:54:24', 0),
(444885, 126, '2015-10-23', '2015-10-23 17:55:07', 0),
(444886, 1, '2015-10-23', '2015-10-23 17:55:11', 0),
(444887, 132, '2015-10-23', '2015-10-23 17:55:12', 0),
(444888, 293, '2015-10-23', '2015-10-23 17:56:32', 0),
(444889, 1, '2015-10-23', '2015-10-23 17:56:37', 0),
(444890, 124, '2015-10-23', '2015-10-23 17:56:51', 0),
(444891, 124, '2015-10-23', '2015-10-23 17:56:51', 0),
(444892, 172, '2015-10-23', '2015-10-23 17:57:36', 0),
(444893, 224, '2015-10-23', '2015-10-23 18:05:49', 0),
(444894, 360, '2015-10-23', '2015-10-23 18:12:47', 0),
(444895, 1, '2015-10-23', '2015-10-23 18:17:43', 0),
(444896, 126, '2015-10-23', '2015-10-23 18:17:47', 0),
(444897, 1, '2015-10-23', '2015-10-23 18:18:02', 0),
(444898, 190, '2015-10-23', '2015-10-23 18:18:08', 0),
(444899, 363, '2015-10-23', '2015-10-23 18:18:24', 0),
(444900, 192, '2015-10-23', '2015-10-23 18:18:43', 0),
(444901, 1, '2015-10-23', '2015-10-23 18:20:57', 0),
(444902, 293, '2015-10-23', '2015-10-23 18:21:03', 0),
(444903, 1, '2015-10-23', '2015-10-23 18:22:13', 0),
(444904, 367, '2015-10-23', '2015-10-23 18:23:28', 0),
(444905, 1, '2015-10-23', '2015-10-23 18:28:12', 0),
(444906, 131, '2015-10-23', '2015-10-23 18:28:12', 0),
(444907, 366, '2015-10-23', '2015-10-23 18:28:14', 0),
(444908, 191, '2015-10-23', '2015-10-23 18:28:26', 0),
(444909, 192, '2015-10-23', '2015-10-23 18:29:28', 0),
(444910, 238, '2015-10-23', '2015-10-23 18:31:00', 0),
(444911, 1, '2015-10-23', '2015-10-23 18:33:32', 0),
(444912, 126, '2015-10-23', '2015-10-23 18:35:07', 0),
(444913, 131, '2015-10-23', '2015-10-23 18:41:27', 0),
(444914, 191, '2015-10-23', '2015-10-23 18:44:35', 0),
(444915, 191, '2015-10-23', '2015-10-23 18:46:16', 0),
(444916, 172, '2015-10-23', '2015-10-23 18:46:37', 0),
(444917, 192, '2015-10-23', '2015-10-23 18:49:37', 0),
(444918, 1, '2015-10-23', '2015-10-23 18:51:41', 0),
(444919, 126, '2015-10-23', '2015-10-23 18:52:48', 0),
(444920, 192, '2015-10-23', '2015-10-23 18:54:16', 0),
...
What is going on?
Do you have "Log Database Queries" checked in your Logging Settings page?
Dashboard > System & Settings > Environment > Logging Settings
If so, I believe this can make the SystemDatabaseQueryLog table get big fast. A recommendation is to enable it only during debugging and development.