well, basically output the counter you want to monitor to a CSV file format.

Later files can then be imported into database PerfmonCounterLogs using DTS, for further...

...Latches are short term light weight synchronization objects.  Latches are not held for the duration of a transaction.  If high, check PERFMON for  memory pressure, disk bottlenecks. Did you perfrom benchmarking?...

it is correct for the tempdb. Besides, if you have a lot of tempdb t/a's you might want to consider adding an extra .mdf ( or.ndf) file to it.

Check if you have enough space for tempdb as well as: There is a database option called  "torn page detection" that can be turned on and off at the database...

Or:

select max(employeeId) from employees

where employeeId <> (select max(employeeId) from employees)

Do that in 2 steps:

Backup LOG YourDB WITH NO_LOG

GO

DBCC SHRINKFILE ('YourDB_Log',TRUNCATEONLY)

GO

http://vyaskn.tripod.com/differences_between_set_and_select.htm

You may want to explore SQL Litespeed. You will be able not only save the time, while doing backup(compare to the regular by MS), but also you will be able to...

Check if it was reflected in SQL Server Error Log. It should. And then you can use master..xp_readerrorlog to check error log for whatever info you need.

Check another link:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=146326

Older version of SQL Litespeed doesn't allow to restore from network. It is a known issue (at least we got a confirmation on that from vendor).

With new version 2005...

AFAIK there are 2 stored proc (by MS)  which do that for you. So you would have the exact clone of your database without data. Unfortunately, I used it last time...

I would also add the status of a db, like: Offline/Suspect, etc

You can either use ping servername or use OSQL -L for accomplishing that.

Smth like that:

     create table #t (Pingoutput varchar(255) null)

     Declare  @cmdM varchar(30)

     Declare @servername varchar(80)

     Set...

It works, Jeet. Thanks.