3 added 4 characters in body; added 4 characters in body
source | link

There isn't a standard option to do this, but you can achieve this several ways.

  1. create a separate db aand move your log tables there. set a max file size.
  2. create a trigger which checks row count or table size aand limits inserts when value exceeded and/or deletes old data.
  3. create a foreign key constraint on an id column pointing to a table with a set number of rows. whenWhen your log table reaches the maximum it will stop.
  4. add a check constraint.

There isn't a standard option to do this, but you achieve this several ways.

  1. create a separate db a move your log tables there. set a max file size.
  2. create a trigger which checks row count or table size a limits inserts when value exceeded and/or deletes old data.
  3. create a foreign key constraint on an id column pointing to a table with a set number of rows. when your log table reaches the maximum it will stop.
  4. add a check constraint.

There isn't a standard option to do this, but you can achieve this several ways.

  1. create a separate db and move your log tables there. set a max file size.
  2. create a trigger which checks row count or table size and limits inserts when value exceeded and/or deletes old data.
  3. create a foreign key constraint on an id column pointing to a table with a set number of rows. When your log table reaches the maximum it will stop.
  4. add a check constraint.
2 added 29 characters in body
source | link

There isn't a standard option to do this, but you achieve this several ways.

  1. create a separate db a move your log tables there. set a max file size.
  2. create a trigger which checks row count or table size a limits inserts when value exceeded and/or deletes old data.
  3. create a foreign key constraint on an id column pointing to a table with a set number of rows. when your log table reaches the maximum it will stop.
  4. add a check constraint.

There isn't a standard option to do this, but you achieve this several ways.

  1. create a separate db a move your log tables there. set a max file size.
  2. create a trigger which checks row count or table size a limits inserts when value exceeded and/or deletes old data.
  3. create a foreign key constraint on an id column pointing to a table with a set number of rows. when your log table reaches the maximum it will stop.

There isn't a standard option to do this, but you achieve this several ways.

  1. create a separate db a move your log tables there. set a max file size.
  2. create a trigger which checks row count or table size a limits inserts when value exceeded and/or deletes old data.
  3. create a foreign key constraint on an id column pointing to a table with a set number of rows. when your log table reaches the maximum it will stop.
  4. add a check constraint.
1
source | link

There isn't a standard option to do this, but you achieve this several ways.

  1. create a separate db a move your log tables there. set a max file size.
  2. create a trigger which checks row count or table size a limits inserts when value exceeded and/or deletes old data.
  3. create a foreign key constraint on an id column pointing to a table with a set number of rows. when your log table reaches the maximum it will stop.