SQL Server Performance

not enough memory to run VERY URGENT

Discussion in 'Getting Started' started by kumarp, Nov 16, 2007.

  1. kumarp New Member

    hi , it is very urgent ...........
  2. martins New Member

    Your comment in the title conflicts with what you are saying. If you are out of disk space, then you would have to free some disk space in order for the server to operate normally. Shrink transaction logs and databases where you can. You might have to perform a backup first, which will be difficult if the disk is already full.
    Bottom line is that you will have to clean up the drives to free up more space.
  3. kumarp New Member

    thanks for reply . i shrinked t -logs files and data files .
    another one c: drive show 0 bytes free space .
  4. satya Moderator

    Don't you have any monitoring methods to go through available disk space and database growth, this is nothing but panic out of blue.
    The error message is quite clear that the server is unable to cope up the load or volume, so you have to make it clear to continue further. If the database files are located on C: drive and if you have enough free space on another drive then detach and attach the database.
  5. martins New Member

    And to add to Satya...if only your operating system is on the c: drive, then you really have a BIG problem. Try and clean up the c: drive through Windows system tools, but it sounds like someone really need to look at space issues on that box rather soon.
  6. kumarp New Member

    hi, 1 .data files and transaction logs files r in d drive.
    2. if i opened the sql profiler it shows low disk space .....
  7. satya Moderator

    Why you have opened Profiler?
    Are you having any slow performance issues or any monitoring requirement.
    Refer to the SQL Server error log to see what kind of errors & warnings are logged.
  8. kumarp New Member

    thanks for send reply........ok we r now clean up some unwanted files and c drive slowly shows the free space
    thanks satya garu...........
  9. satya Moderator

    That is the final workaround for you and I believe this is not a production server as your urgency doesn't sound like that.
    In any case make sure to differentiate non-sql server files from the SQL Server drives as suggested by Martin above.

Share This Page