Database performance side effects of huge inserts

Question

All,
I know this might not be the right place to raise this question. Just thought any of you might have come across this in db programming.
I have a table in database in which there would be huge no. of insertions through out the day. The volume of insertions per day would be around 20000 rows. And there is no process other than this which would be querying this table.
My question is whether so many INSERTs on one table would affect in any way the performance of the whole database ?
Would this affect the response time of the processes working with other tables in the same database ?

Answer 1

My question is whether so many INSERTs on one tablewould affect in any way the performance of the whole
database ?
Would this affect the response time of the processesworking with other tables in the same database ?
Yeah since it's running on the same PC.
The volume of insertions per day would be around20000 rows. And there is
no process other than this which would be queryingthis table.
But 20000 rows is a very small insert number for
database, so you needn't to consider too much about
performance. If you wish to insert quicker, you
should use PreparedStatement to insert your rows, or
use batch insert.
One exception is that you'r inserting 20000 rows into
a very big table with many index expressions on that
table or imported/exported keys on other big tables.
That will be slower.Well this table wont have any foreign keys on any big table...
though the table size would be huge... would gross upto 1 gb data in a month. I am not concerned about the performance of queries on this table at any stage.. but would continuous insertions... 10 INSRTS a sec in this table affect the performance of the rest of the tables in the db in any way