January 20, 2010 at 1:36 am
Hi Folks,
My Data base log file having the size around 17 GB. when i tried to take the transaction log back up it has taking long time and i cancelled the backup. when try to copy the log file it is showing message "cannot delete DB name: it is being used by another person or program". i tried to kill the process but the process also is not killing. please suggest me.
thanks in advance.
- Ramu
January 20, 2010 at 1:46 am
ramu.guggilla (1/20/2010)
when try to copy the log file it is showing message "cannot delete DB name: it is being used by another person or program". i tried to kill the process but the process also is not killing.
You cant delete the Log file while tat DB is still attached in SQL Server, AND running live.
That is why you are receiving the "in use" generic error.
Stop all SQL services should you need to trash the ldf (which I dont recommend since your backup also failed)
have you tried looking into the real problem? why is you tempdb so large? is it full or only using 5% of its size?
17 GB backup should not take longer than 10 minutes (depends on you hardware off course)...
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
January 20, 2010 at 1:57 am
Looks like your database is not of production as you are trying to delete the database; if so you can put the database into single user mode with no wait and delete the database if needed.
ALTER DATABASE <db_name> SET SINGLE_USER WITH NO_WAIT
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
January 20, 2010 at 6:04 am
Do not ever delete the log file. It's not an optional component of the database. If you delete it, there's a good chance that the DB will not come online.
Was the log backup blocked by another process? (check sys.dm_exec_requests)
How much of the log file is in use (check DBCC SQLPERF(logspace))
Where were you trying to back up to?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply