I not sure you have got your solutions or not? But as I know, you can
detach the database, delete the .ldf file, then attach agian the .mdf
file. For using this way, you should has the proficient right to delete
the file.
Some will suggest using shrinking database but this way will take time,
because it not reduce the database size in once. But this way still
work, it may suitable for certain situation.
Re: statement not allowed within multi-statement transaction (Long) ... So if I do have an open transaction I can't figure ... > 100 Database does not exist in sysdatabases can not dettach ... > --Verify database Exiists for detach... >> Wayne Snyder, MCDBA, SQL Server MVP... (microsoft.public.sqlserver.programming)
Re: ldf file missing... ... If so you could try a detach db command, ... then try a attach command.... >the database are wasn't cleanly detached, ... >> A new log file can only be created under certain ... (microsoft.public.sqlserver.server)
Re: SQL Server 2008 and background commit ... Those tests create database, tables, procedures, fill some ... then detach.... I would like to have the same behavior like on SQL 2005 is possible. ... That is, when you delete many rows, SQL Server... (microsoft.public.sqlserver.programming)
Re: how to do backup of msde? ... I can't give you a complete answer as there are others better suited to explain however in general terms when you detach a database the logs files are flushed, statistics updated and completed transactions committed to the database. ... In my experience most backup regimes involve stopping the server processes, backing up all MDF & LDF database files required and then restarting the server processes. ... >we use Protection Pilot, it installs a MSDE that it uses ... (microsoft.public.sqlserver.msde)
Re: statement not allowed within multi-statement transaction (Long) ... 100 Database does not exist in sysdatabases can not dettach ... --Verify database Exiists for detach... >> I have a sample script that is available on request. ... >> I am getting the above error message when executing a stored procedure. ... (microsoft.public.sqlserver.programming)
