I do face the same issue, with the output of the "memory used by objects", I could see tempdb come in the first place with huge buffer pages.

Could you please...

I tested it in SQL Server 2008R2 dev edition, may I changed the setting in the same query analyzer. I'll try with different server after changing the setting with new...

It's for one of our local old dev servers to cut short the sql error log growth.. I dont want to do it prod server 🙂

Perfect, it worked now. But to take the setting apply we need to restart the SQL SErver service 🙂

Appreciate your help

Thanks for your reply. However I had reviewed this article before itself. but it doesn't list the trace number which need to used to this particular event

Exactly said. checking SAN is in progress now and expecting our Storage guys to see any abnormal settings done.

BTW. Could you please let me know what SAN Setting was wrong...

This is what I get as on wait stats output

WaitTypeWait_SResource_SSignal_SWaitCountPercentageAvgWait_SAvgRes_SAvgSig_S

OLEDB103923.24103923.24025341970.730.41010.41010

CXPACKET23462.7122882.71580372167415.970.00630.00610.0002

LATCH_EX7059.456811.85247.652829814.80.00130.00130

PAGEIOLATCH_SH4573.954555.518.452213093.110.02070.02060.0001

WRITELOG1256.891212.0644.838804830.860.00140.00140.0001

I haven't done yet. I'll check it out and update the output to start the investigation.

Thanks a lot for script, I'll use it and get back to you surely

Thanks for the information Steve and all. I have the down time to perform this task over this weekend.

I'll work on it and let you know. Btw is there...

hi Mak,

I'm too curious to know, how a single .bak file is listing 3 .mdf file.

Have you just made any change to the screen shot of the picture?

Let me...

Hi,

I would to know, how do you get 3 .mdf files in a bak. Whether you will be able to create more than one .mdf file for a database...

hi,

Exactly said.. steve.. If there is disconnection between the nas filer and the user database, then db will be marked to suspect mode.

Once the Nas filer connection is established,...

If the backup log has been issue with Truncate_ONLY after any t-log, the Fist_LSN of the backup set with be set to the same of LAST_LSN. So at that time...

Exactly Said.. Tempdb cant be changed to any other recovery mode, it is always set to Simple.

You could shrink the file or bounce the SQL Instance... 🙂