Problem with MSSQL? .NET application? or Win Server?
Dear members,
Please help me in regarding my problem. I am very much confused on whom to blame for the problem........MSSQL? or .NET ? or Win server?
I have a dedicated server with 2GB RAM, SQL 2005, 150GB bandwidth, 160 GB disk space etc.,
I have created a .net application that fetches data from different servers using their XML feed (wether report, stock data, etc.,). I programmed it in such a way that it gets the data using XML and stores it in a DB table. From there my website gets the data and displays it.
Now when I try to install the application on my server, the CPU usage is peaking to 100%. The task manager shows that SQL is the main cause.
I tried installing the application on my local system and connected to the dedicated server DB and the server work fine (CPU 2%). I installed the application on the dedicated server and connected it to my other SQL DB that on other server and even then it worked fine (CPU 3%).
The problem arises when I install the application on the same server where the SQL DB is.
Can anyone help me please.............I dont know what to do. I am totally confused.
Thanking you in advance,
Warm regards,
Steve
Software/Hardware used:
Software/Hardware used:
ASKED:
December 15, 2007 5:09 AM
UPDATED:
February 22, 2008 5:25 AM
Answer Wiki:
You'll want to fire up SQL Profiler on the SQL database which isn't working and see what commands are taking a long time. Perhaps some indexes need to be added to that database.
My question would be, if you are simply downloading XML and storing it in the database, why not store those XML files directly on the web servers, and open the XML files from the web pages directly without the database. What purpose does the database serve in this setup? It sounds at first glance like the database isn't needed at all.
Can you elaborate more on what the database is used for and how the data is stored?
Dear Sir,
Thank you for your reply.
We are storing the data for the further use. More over this data is used to display on our thin client software that will be running on our members desktop.
It was running good some time ago. But all of a sudden, my website is taking very long time load as the server is CPU usage is touching 100% due to these applications running on the server.
If I stop the applications running, then CPU usage falls down to 2%.
It was not the problem with my other virtual dedicated server, where the same application is running. But the SQL is on different server.
It seems the problem arises where both application and SQL are on same server machine.
Please help me with this, as it has been more than a week since I am begging everyone on forums to help me.
Thanking you in advance,
George
To see all answers submitted to the Answer Wiki: View Answer History.
Be sure to check out my blog hosed on the IT Knowledge Exchange.
Denny
Sir, Thank you for you help.
We are storing the data for the further use. More over this data is used to display on our thin client software that will be running on our members desktop.
It was running good some time ago. But all of a sudden, my website is taking very long time load as the server is CPU usage is touching 100% due to these applications running on the server.
If I stop the applications running, then CPU usage falls down to 2%.
It was not the problem with my other virtual dedicated server, where the same application is running. But the SQL is on different server.
It seems the problem arises where both application and SQL are on same server machine.
Please help me with this, as it has been more than a week since I am begging everyone on forums to help me.
Thanking you in advance,
George
Sorry for not getting back to you, the site never told me that you had responded to the post.
It still sounds to me like something isn’t being called correctly. Are the indexes between the two servers the same? Is the code in the app the same when it’s being run on your local machine and the server?
Running the client app on the SQL Server won’t cause the SQL Server to use more CPU power than running it remotely.