I do not think you can attach the database with just 1 file. Try and let us know if you are successful. if you want to get rid of 1 file....

The transaction log grow mostly because there is no proper Tlog backup or the recovery model is set to full and there is a reindexing or any bulk- insert activities...

what is the operating System

You can restrict the size of Transaction Log. Noeld answer is correct . Just to add you can use @job_id parameter to run a particular job if the event happens. Example...

I do not know what is your database size and disk space but make sure you have enough disk space for transaction log if the recovery model is set to...

Check the SQL Agent Error Log.

Make sure the database is defined properly in the job step.

Secondly never use direct SQL Commands (which refers to objects) in the jobs step. Create a...

First of all the reason for increase in the size of trnascation log is beacuse of Full Recovery. Are you running a bulk insert or optimizer on the database ?...

Does it return any error. Check the error log file also

Your database is victim of TORN_PAGE_DETECTION.

You should restore from backup but as you do not have a backup try using

sp_resetstatus database_name. Remember to reboot the server before trying to...

Troy

I would like you to interview me. I am not looking for a job just want to check how cruel you can be....

I am not administering 2005 database. All the database are of 2000 , I just installed 2005 beta version

I was suppose to test this. Good now i will wait for the answer and do other projects

KILL "SPID" with statusonly

Try this

SELECT rowcnt FROM Sysindex

WHERE Indid in (0,1) AND Id=Object_Id('<name of your table>')

If you have couple of steps in the job then narrow down as which step is taking the time, how many time the retry option is set up in the...