Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I'm executing sql query on my database. I have SQL Server 2008 installed on my D harddrive which has 55 GB free space.

I have also C drive which has sth like 150 MB free (right now).

While executing that query on quite a big table (16 GB) I have an error:

An error occurred while executing batch. Error message is: Not enough disk space.

I would like to know if there is any possibility that I can make SQL Server to use D drive instead of C

Or maybe there is any other problem with what I'm doing ?

Thanks for help

share|improve this question

migrated from stackoverflow.com Jun 16 '10 at 19:39

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

3 Answers 3

This is likely a logging issue. You can move the log file to a different drive and use a lower level logging.

share|improve this answer
    
Log file is set to be written on D drive, executing this query takes a lot of free space on my C drive dont even know which file is beeing modified, what else can I do ? –  potatoMan Jun 16 '10 at 21:23
3  
What about the TEMPDBs? –  ITGuy24 Jun 16 '10 at 22:05
    
there are also stored on D drive according to options which are set :/ –  potatoMan Jun 16 '10 at 22:13
    
Wild Guess: Try setting the TEMP and TMP system variables to a directory on the D drive. –  joeqwerty Jun 17 '10 at 2:24

This is likely to be the TEMPDB, one of SQL Server's System databases. It will have been created in the default database location by the installer.

This article talks about moving the tempdb.

Equally you could add additional (expandable) files on D: to the tempdb database's primary filegroup, then set the default ones to fixed size (and eventually flush, then remove them).

share|improve this answer

Are you running the query using a client application on the SQL server, like SSMS? If so, it could be, probably is, using the C drive to store the output for display, especially if you're running the output to a grid. Try running the query using the SQLCMD command line.

share|improve this answer

Your Answer

 
discard

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.