We have a website with many users(betteen 300 and 1000 at any given time)
We decided to try and use the database to log how many users accessed the site by puting an insert statement into asp code on the website. The insert statement enters a "1" into a table every time someone accesses the page. (I know there are better ways to do this, we are just experimenting!)
For some reason when we impliment this, the processors on the database server go up to 100% all the time. Can someone please explain the database performance differences in detail between an insert and a select statment. There have always been select statements on the site which dont cause any problems, only insert statements.
Thanks
We decided to try and use the database to log how many users accessed the site by puting an insert statement into asp code on the website. The insert statement enters a "1" into a table every time someone accesses the page. (I know there are better ways to do this, we are just experimenting!)
For some reason when we impliment this, the processors on the database server go up to 100% all the time. Can someone please explain the database performance differences in detail between an insert and a select statment. There have always been select statements on the site which dont cause any problems, only insert statements.
Thanks