Currently, I have a window application with using SQL 2008 R2.
This application is used by 200 users at the same time.
The database's size is almost 20gb.
The db server uses 16gb RAM, 200gb HDD.
And server is slow now, the CPU is over 80%, RAM was configured 14gb limit.
Does anyone have a tool or best practice to find out why the server is slow down?
Thanks.
Related
We have around 20 Different physical servers in which SQL Server has been installed and configured( various versions MS SQL servers)
Need to monitor the complete SQL servers using one tool Which includes Database Performance, wait time, expensive queries currently executing, Log size utilization, disk space utilization ,Monitor CPU, memory and disk space utilization of the SQL Servers,Get complete details about SQL Server sessions, buffer, memory, locks and latches
If there is any Microsoft product available then preferred or possible other tools.
Please suggest
Looks like a lot of requirements. FYI, there is no Microsoft tool to manage On-Premise MS SQL Server instances. But, you can create your own utility using SQL scripts or SSIS packages.
The SQL Server is running on a well o:) configured server. The server configuration is given below.
OS - Windows Server 2012 R2
RAM - DDR3 24 GB ECC
RAID 10
The NAV SERVER is also installed on the same server. Almost 112 concurrent end-users are accessing the NAVISION database through different clients system.
I have noticed that at a particular time (5PM/6PM) the SQL as well as the NAV SERVER are consuming the whole (20GB+) RAM of the server everybody & makes the server unstable.
How can I solve this issue? Thanks in advance!
If it's always happening in a particular time you should have to figure what is hammering it.
SQL job? Something in NAV? Windows Task? Antivirus? Some user is running something which affecting it (copying thousands of files to network share for example)?
But yes - adding more RAM is always good.
I have a classic ASP application with SQL Server Express that includes a couple of maintenance scripts that take potentially a few minutes to run. On the old Windows Server 2003 and 2008 installations, SQL Server Express would be capped at 50% of CPU during a long-running script, which was fine.
Recently I got a new machine with Windows 2012 Server, and on this one, SQL Server Express is capped at only 10% of CPU in long-running scripts. As a result, the new machine is marginally slower at running the scripts, despite being much more powerful. Is there a way to control and increase the CPU quota for SQL Server Express in this situation, to perhaps 25%?
I realize that SQL Server Express is limited to using 4 cores, but my new machine is only six cores, and the theoretical limit would seem to be 67% from this factor.
Where would this parameter be managed? Would it be a Windows setting, or a SQL Server Express setting, or an IIS setting that governs the CPU quota for a single script?
A couple of possibilities I think I have ruled out:
IIS allows setting a limit on the CPU usage by an application pool, but this is not enabled by default, and was not enabled on my server.
Windows has a utility called "Windows Server Resource Manager" but
this also is not installed on my server. In any case, it would only
act when total CPU usage was above 70%, and I notice the apparent
limitation on SQL Server Express even when the CPU is otherwise idle.
Well, it is not capped at a certain percentage. It is ONE CORE ONLY. Want more - get another version (i.e. not express).
I realize that SQLExpress is limited to using 4 cores, but my new
machine is only six cores, and the theoretical limit would seem to be
67% from this factor.
Aha. Interesting.Where did you pick up that "knowledge"? It has never been that.
I have statistical math functions that use intense sql queries and run in an sql assembly. I just increased the RAM on my db server (IIS 6, SQL Server 2005) but my queries still suck up 100% of my CPU for the 5 minutes I allow for the assemblies to run. Is there any way to allow the assemblies to cap their CPU? At 100% the server becomes unresponsive. Any sql tuning would help too.
SQLServer 2008 has a resource governor that allows you to throttle the CPU and/or I/O based on the db username that is used for a given connection. If upgrading to SQL Server 2008 is an option for you, your stats assembly could use a dedicated database username that allows it to consume 100% of the CPU unless another db connection needs CPU, then it yields to the other processes.
This works very well. We have queries and reports that do complex statistical analysis of thousands of data points. It too is CPU intensive. Before we upgraded to SQL Server 2008, we have all sorts of performance issues. Now everything runs smooth. The other new features of 2008 are nice, but the resource governor is the real reason we upgraded.
I have both SQL Server and SQL Server Express installed on my desktop PC, and have the AdventureWorks database installed out-of-the-box separately for each.
When I run the same application against the AW database on SQL Server Express, each query takes more than twice as long to complete. These are simple queries - not particularly demanding. None of the processor cores are under any significant load.
This has surprised me. I would expect that the (commercial) SQL Server would run faster in an enterprise environment with thousands of users: I would not expect to see any difference in performance for a single-user running a very simple set of queries on a local database.
Has anyone else had a similar experience, or can shed any light on what might be going on here? Thanks.
SQL Server Express is limited to use a single CPU and 1GB RAM, so that could be causing the queries to run slower than the paid editions.