Hi - Use the default trace! Pl refer the below link, will tell you more in detail

https://www.simple-talk.com/sql/performance/the-default-trace-in-sql-server---the-power-of-performance-and-security-auditing/

Refer the other thread...

http://www.sqlservercentral.com/Forums/Topic1469888-146-1.aspx

Might be useful to you to find out.

Lowell - Thank you so much for providing more light.

Thank you Gail!

Excellent - Thank you Sean!!!

Hi Livingston - I understood now! Great Thanks!!!

Yes I got it from this link only. But I unable to understand the concept behind this query. Please clarify.

How it works when the same table name mentioned two...

Hi GilaMonster! Thank you so much for showed some light on the dark area. I'll dig into that more. Thank you for your time to clarify. Much appreciated.

Thanks

Bala

(i) Displaying Log_reuse_wait_desc as Log_Backup for a db in SIMPLE contradicts.

(ii) Is there any active transaction pending on this db?

(iii) Change the Recovery to Full.... and then again to SIMPLE...

First Screen shot is not clear - another image is on that. Moreover the log_reuse_wait_desc for t1 (if it is SIMPLE) looks as LOG_Backup... It can't be. How you created...

Please post the output

select name, recovery_model_desc, log_reuse_wait_desc from sys.databases where name = 'your db name'

dbcc sqlperf(logspace) [for the two databases]

Aplogies if I didn't mean what I actually mean.

I mean to say the content (data) of backup file will be same. If a full backup is taken on a database...

I tried the techniques those are mentioned in the link already but nothing released the memory.

One way I agree with Monster because the performance tab in Task Manager shows...

If db recovery model is simple and I take full back up every day. And if my recovery mdel is full and I take only fulll backup every day.

(I do...