Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SQL Slowness w/ non-local SQL Server

Has anyone else experienced problems running v7.05 with a non-local SQL Server. Everything is OK until I try looking at an Interface Details page. The page never loads and the charts eventually timeout and show up as red x's. The SQL DBA's say the SQL server is not being overly burdened and we never had this problem in v6.4. We just upgraded to v7 on Friday and this problem showed up immediately.

Server: Windows 2003
Proc: 2 x 2.0 GHz
Memory 4GB
HW: Dell 2650

Find more posts tagged with

Accepted answers

All comments

Rob

I had a similar problem and my DBA's spotted the cause. Apparently SQl will allocate (to itself) all available memory, therefore leaving very little for the server to use itself. If your problem is similar you will notice that after a reboot the SQL server performs ok for a while and then starts to slow up as the SQL processes secure more and more memory. The answer is to set set the SQL process to only use a certain amount of memory. I have mine set to 800Mb for SQL, 200Mb for everything else and it's really quick now.

Regards,

Rob.

fenster24

quote:Originally posted by Rob

The answer is to set set the SQL process to only use a certain amount of memory. I have mine set to 800Mb for SQL, 200Mb for everything else and it's really quick now.

I am using the desktop version of SQL that comes with Orion. How can I limit the amount of memory my SQL Server uses? I found a query to run, but an error message said that it was an advanced feature and could not be executed. Is it possible to limit the memory usage of the desktop version of SQL?

Windows 2000 SP4
2GHz processor
2GB RAM

-Rusty

skrause

After working with SW support we found out that some of the COM components within Orion are locking up. They will occasionally make a call to the SQL server and then never return, even after the SQL timeout has elapsed. It seems to happen on the charts and gauges the most and the only fix that I've found once it's occurred is to boot the server. Supposedly they are working on a fix right now.

The next SQL problem I've happened across is when running a report, say from the Reports page of the web site, it seems like the pollers stop polling until the report completes. I tried running a report showing average frame-relay utilization stats for last month and not only did it timeout after a few minutes, but the polling never restarted until I booted the server. I suppose I could increase the default timeout period, but I don't want to cause problems for the polling engine. I haven't fully verified that's exactly what is going on, I've only ran a couple of experiments, but I was wondering if anyone else noticed similar problems?

charpham

I am experiencing similiar problems regarding the issue below... I have found this is true when I run Historial reports-(i.e. Average and Peak Traffic Rates-last month) I have even tried to query the SQL database from Report Writer and it times out.. I don't have the issue of the Pollers prematurely aborting though.. One thing to note I did have some issues with the pollers prematurely aborting after logging out of the server... I talked to TS about this and they sent me a patch (snmpv61.ocx) which fixed the problem

quote:Originally posted by skrause

The next SQL problem I've happened across is when running a report, say from the Reports page of the web site, it seems like the pollers stop polling until the report completes. I tried running a report showing average frame-relay utilization stats for last month and not only did it timeout after a few minutes, but the polling never restarted until I booted the server. I suppose I could increase the default timeout period, but I don't want to cause problems for the polling engine. I haven't fully verified that's exactly what is going on, I've only ran a couple of experiments, but I was wondering if anyone else noticed similar problems?

Network_Guru

quote:Originally posted by skrause

It seems to happen on the charts and gauges the most and the only fix that I've found once it's occurred is to boot the server.

I have had the same thing happen with the charts and gauges on the website, only I am using a local install of the SQL server.

quote:Originally posted by skrause

The next SQL problem I've happened across is when running a report, say from the Reports page of the web site, it seems like the pollers stop polling until the report completes. I haven't fully verified that's exactly what is going on, I've only ran a couple of experiments, but I was wondering if anyone else noticed similar problems?

I've noticed the same thing as well. I run the task manager to keep an eye on the CPU utilization while running a report/doing a query. The poller has only never recovered once in my case. You can watch the polling service CPU utilization pick up again right after the SQL service finishes hogging the CPU.
I am using a dual CPU server, so this may be less of an issue in this case.

-=Cheers=-
NG