Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We recently moved to a SQL Server that's on a VPS and every now and then we get a 9001 error when trying to do an update.

Rebooting the server fixes the problem.

I changed the maximum server memory (in MB) to 2000 because it's a 4GB VPS.

But I just don't know what's causing the error.

share|improve this question

migrated from Apr 24 '13 at 19:34

This question came from our site for professional and enthusiast programmers.

What version of SQL Server? – RBarryYoung Apr 24 '13 at 18:41
sql server 2008 – Phillip Senn Apr 24 '13 at 18:53
up vote 7 down vote accepted

Is your database set to auto-close? If auto-close is on your database shuts itself down and the update statement would then cause the database to come back online, kick off automatic system checks, and could raise this error if the update statement comes in at the same time.

What other SQL Server error messages are coming in at or around the same time as the 9001 error?

What Windows error messages are coming at around the same time? Are there any error messages for your underlying disk structure? This error can be caused by disk failure as well.

share|improve this answer
I moved tempdb according to [… instructions. Auto-close is set to true, so I'll turn it off as well. – Phillip Senn May 9 '13 at 20:22
Here's the link I posted it wrong the first try. – Phillip Senn May 9 '13 at 20:29
+1: good catch. – RBarryYoung May 9 '13 at 22:15

That error means that the log for your database (or for tempdb) is not avaialble for some reason. That's a serious problem that is usually fixed by restarting the server.

If the problem recurs, it could be many things having to do with problems with your storage system. One possible thing to check is to see if your database's log file (or tempdb's log file) is running out of space (not sure if that can cause this error or not).

share|improve this answer
Don't you just hate it when people never come back to accept answers? – RoKa May 9 '13 at 8:17
Well, a bounty has been added to the question, so I assume that the OP is looking for something more than what I provided. However, if that is the case, some feedback to let us know what else is needed would be helpful. – RBarryYoung May 9 '13 at 12:50
Thanks @RBarryYoung! It's inconceivable that tempdb is running out of disk space, but I moved it to it's own folder according to thse instructions. I've also turned off auto-close, so now I'll see if the problem still exists after applying those two solutions. – Phillip Senn May 9 '13 at 20:32
@Phillip You had auto-close on?!? Ah. Well yes, auto-close can cause all kinds of errors and other havok. – RBarryYoung May 9 '13 at 22:13

Make sure you are on the latest service pack version of SQL Server 2008.

Restarting SQL Server is just duct taping the problem. I would suggest you to collect diagnostic information using SQLDiag when the problem actually occurs.

Also, run a DBCC CHECKDB against the database so that it will give you more info about the corruption. A last resort would be to run a CHECK DISK (chkdsk) to see if the OS sees any problem with the disk subsystem.

Max memory setting has nothing to do with 9001 error.

share|improve this answer
If I go to help, About, I get this: – Phillip Senn May 9 '13 at 20:35
Microsoft SQL Server Management Studio 10.50.1600.1 Microsoft Data Access Components (MDAC) 6.1.7600.16385 Microsoft MSXML 3.0 6.0 Microsoft Internet Explorer 8.0.7600.16385 Microsoft .NET Framework 2.0.50727.4927 Operating System 6.1.7600 – Phillip Senn May 9 '13 at 20:36
@Phillip that is the SSMS version. Can you do a select @@version -- or -- SELECT SERVERPROPERTY('productversion')as ProductVersion, SERVERPROPERTY ('productlevel')as ServicePackInstalled, SERVERPROPERTY ('edition') as Edition, serverproperty ('collation') as collation – Kin May 9 '13 at 20:38
10.50.1600.1, RTM,Express Edition with Advanced Services (64-bit) – Phillip Senn May 9 '13 at 21:04
I'm looking into using SQL Azure because of the problem we're having. – Phillip Senn May 9 '13 at 21:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.