Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 SQL Server 2005 Express; login failed; CPU usage

Author  Topic 

gregorio
Starting Member

2 Posts

Posted - 2010-08-06 : 15:33:56
Hi guys,

I created a login for my database. Authentication is working fine. The default database for the login is set to this database.

The problem is: Without fail, under high CPU usage on the overall server (95% and above), this error occurs:

Login failed for user 'user_xyz'
Error: 18456 Severity: 14 State: 16.


When CPU usage settles down, logging in works fine again.

Now, the server's memory is running low too by the way. Only a few hundred megabytes of actual memory are left.

Any thoughts?

Thanks,

Greg

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-08-06 : 15:44:23
Fix the CPU usage issue. A well tuned system should be less than 50% CPU usage.

High CPU utilization is typically due to missing indexes. Identify the slow running queries and then add the appropriate indexes.

Also, check the SQL Server Error Log when this happens.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

gregorio
Starting Member

2 Posts

Posted - 2010-08-06 : 16:05:06
Thank you Tara. And, agreed.

The server is a web and email server too. A lot of the usage is from IIS and email serving. Very little usage is from SQL Server.

(I'll be setting up a dedicated system for SQL when possible)

Does this sound right though? Logging into SQL Server completely ceases under high load?

I wonder if there's a way around this, in addition to optimizing the server.

(Right now, I never know when there will be a high usage 'blip' that will trigger this problem and break web page-to-SQL connectivity.)

Thanks very much,

Greg



Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-08-06 : 16:38:26
If SQL can't get system resources, then it can't authenticate you or do other simple things.

Perhaps you can restrict how much other system processes can use, although I'm not sure how you'd do that with regards to CPU.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -