Need Help with out of hand log file - \Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\TPM250_log.LDF

  • I have been trying to make sure that all databases, logs, and full text catalogs etc are located or are moved off of our C (operating system) drive and onto other drives that we have designated for these things.  Problem I am having is that this C drive is losing space rather quickly and I think I have narrowed it down to the file "TPM250_log.LDF" under the directory  \Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\.  I have the log files for the database going to a seperate drive and they appear to be working as such but I dont know what this file is or how to move/control it. 

     

    Does anyone know what it could be and how to move it if needed?  THank you !!


    New to the DBA world...thank you for your help!,

    IanR

  • Ian

    Do you have a database called TPM250?  If you do, detach it, move the log file, and then re-attach the database.  Search for "attaching and detaching a database" in Books Online.  If there is no such database, then chances are the file isn't doing anything anyway so it'll be safe to move it.

    John

  • THank you very much.  Based on the naming convention used for that file I didnt even think to associate it with a database becuase we wouldnt name a db anything like that and the system DB's are easy to recognize.  Turns out it really was a DB on the server that may have been placed there by a 3rd party application that was being tested for monitoring and performance and it was filling the db up rather quickly.  We deleted the db all together and then deleted the ldf and db associated with it.  Free'd up 5gb.

     

    Thank you.

     

    BTW - We are considering moving the logs and db files for a other db's on this server but I want some opinions on wether its possible or even wise to move system_db file locations.

    Thanks again!

     

     


    New to the DBA world...thank you for your help!,

    IanR

  • Ian

    It's certainly possible to move system database files, and in many instances it's also wise.  For example, you may want your system databases to be on different disks from your user databases.  And if your application uses tempdb a lot then you will want that on its own disk.  It can be a bit fiddly and you can even get your fingers burned if you re-attach msdb and model in the wrong order, but if you follow these instructions http://support.microsoft.com/default.aspx?scid=kb;en-us;224071 faithfully then you should be OK.

    John

  • Excellant information!! Thank you so much John!


    New to the DBA world...thank you for your help!,

    IanR

  • Happy to help.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply