Hello, I'm Jason
I live with my family in the rolling hills of Northeastern Pennsylvania. I'm a web developer by trade, but have broad experience in various business areas. Want to know more about me?
Today I received an error message within one of our applications stating that
The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space. I posted to the ASPAdvice.com lists and received more information than I bargained for. Mike Campbell and Wally McClure provided some very valuable information regarding this issue. Here is Mike’s post below:
Let your log file grow a bit more in size and/or jump on query analyzer and run the following:
1 2 BACKUP LOG <database\_name> WITH TRUNCATE\_ONLY GO
That will truncate your log (meaning recoverability won’t allow point-in-time recovery… though I doubt you’ll need it).
1 MB may not sound like much, and really isn’t the issue. The issue is that SQL Server will only allow a certain amount of space for logging transactions/activity. when that space is up it’s game over (unless you allow the log file to grow – and then if you allow it to grow, it can grow until there are only 5MB left on the disk, and when that fills up you’ll get the same message). The best way to deal with this: make your log file 25% of the size of your .mdf and do nightly backups, which truncate the log after recording all of the changes to the backup. If you do LARGE transactional changes during the day you may run into this a bit.
Here’s a quick overview of some other info (but the sql statement above will get your app working again… then you’ll just need to solve the problem, not just the incident). http://blogs.sqladvice.com/aweiker/archive/2004/03/31/883.aspx
Turns out that the issue wasn’t necessarily with the transaction log. In fact, the C: drive on the server dipped below 500 MB of free space. Once temp files were cleared out and the free space hit 2 GB, the web app started working again. Go figure!Read More
Make sure that before you install a later version of Visual Studio 2005 no matter the edition that you completely remove all previous version components first. I had two installations and I got caught. I forgot to remove SQL Express and when I tried to reinstall .NET to then remove it, I received an error stating that some pointers are no longer valid and that there is no memory available to remove it. So, I need to reformat my PC to fix this issue.Read More
I ran into an issue when installing a new version of Visual Studio 2005. I forgot to uninstall SQL Server 2005. So, the .NET Framework versions were different. This caused tons of issues leading to me not being able to have SQL Server 2005 at all on this particular machine. So, remember to uninstall everything first! ;)Read More
Don’t forget to sign-up for Code Camp 2005 for the Greater PA (Eastern Pennsylvania) region. Code Camp 2005 will take place April 23-24 in Philadelphia. For more information, visit http://www.dotnetvalley.com/Events/258.aspx. All .NET Valley members and other IT professionals from Eastern Pennsylvania are encouraged to attend. To attend this event, click the link above. On the event information page, there will be a link for you to register.Read More
I read a fairly decent article today about getting ready for SQL 2005. So, I thought I’d share…Read More