• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Strange problem with SQL Server 2005

StageLeft

StageLeft

No Lifer
I have a few sites on SQL 2005 that stopped working this morning, symptoms being an unresponsive database. The db server was up and fine. I used management studio to go to some of the supporting databases and expand the table list. This expansion took a long time. Normally it's immediate or a couple of seconds, but this took maybe 10-30 seconds for each database. Finally, the tables listed, and then the sites all started to work.

I've never had this happen before. Any ideas on what happened?

Around a similar time this started, I was trying to use my windows account to access the sql server and my client was using cached and incorrect credentials, as I recently changed my password. I logged off my dev machine, logged back in, and was able to authenticate. None of our production apps use my account, though, but I mention this because I saw at least for SQL 2000 something about existing users possibly getting kicked on a 2000 instance if another user takes too long to authenticate. It seems unlikely anything to do with me could impact everything else, though.
 
Could check for open transactions or too many connections open in the pool.

Also check file system, you're db files are separate from the actual server application so if they become corrupt or you don't have enough room for growth there could be some slowness as the OS deals with paging things in and out.
 
Hmmm, trouble communicating with the active directory? Then suddenly it realized that it could communicate and the short delay was it authenticating? Just a thought.
 
File system has lots of room. Regarding AD communication, windows search service uses an account that is constantly--although it has for MONTHS--been unable to authenticate sometimes. It's a domain account and normally can authenticate but dozens of times/day for no obvious reason the login of this account from the sharepoint machine to the sql machine will fail, as noted in sql machine's application logs.

Finally this morning one of the supporting databases entered a "SUSPECT" state and was unreachable. The machine was rebooted and I think possibly the admin did a restore and it's good now.

Still of interest is that habitual inability to authenticate, though from time to time...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top