January 18, 2011 at 3:46 am
Hi,
I am using MS SQL server 2008 enterprise edition.
A third party application communicates with it using ODBC connection for record selection and insertion. This application is deployed on a different server. This application can log 300 record per second.
I have some SQL jobs running on MS SQL server 2008, which transfers data from one table to another after making some changes.
SQL jobs are running after 2 minutes, and it takes approximate 10 seconds for completion. During the job execution we don't get any visible change for CPU usage on database server, while the CPU usage of application server surges to 90+.
Similar behavior is seen when i query any table with huge data.
Is it because of some configuration in SQL server or ODBC or anything else?
February 14, 2011 at 2:09 pm
One reason for that would be the notorious RBAR cursor
Since the application may be inserting the 300 rows per second one row at a time which causes the application server to peek
To see run the profiler and see what information is being written
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply