sp_helpfile will give you the info you want, but you would need to run it against each database.

Alternately use:

SELECT * FROM dbname.dbo.sysfiles ...

Note that

ALTER DATABASE DBNAME

SET MULTI_USER;

Will "work" on a database in READ_ONLY mode, i.e. it doesn't return an error, but it also doesn't take the database out of READ_ONLY mode. The...

Have you tried running the command out of Managment Studio. I often find I get much better feedback here than when I tests directly from the SQL Agent.

My typical build...

Try

ALTER DATABASE dbname

SET READ_WRITE;

Leo

Is it Friday yet?

You could add more columns to the INCLUDE clause. This doesn't increase the size of the root or intermediate index pages, only the leaf level pages. If you don't want...

These are the actual two lieces of code causing the problem:

The table is _Log

SELECT TOP (@Count) ID, Data, FROM _Log

WHERE ProcInstID = @ProcInstID

ORDER BY ID ASC

DELETE _Log...

Are you using Standard or Enterprise edition?

With Enterprise (if you have the space in TempDB) you could rebuild the index WITH (online = on). Having the indexes defraged would...

Profiler!

Run a trace, filter on the database ID (SQL 2000 or less) or on the DB Name (SQL 2005 up).

Leo

This is what I would call an Intra-table deadlock. Most people think of a deadlock as between two process accessing two tables (inter-table) in different orders, but here the two...

I used these notes. Very comprehensive with good screen shots.

http://www.mssqltips.com/tip.asp?tip=1687

http://www.mssqltips.com/tip.asp?tip=1698

http://www.mssqltips.com/tip.asp?tip=1709

http://www.mssqltips.com/tip.asp?tip=1721

Watch out for the bugs. And I strongly reccomend you Slipstream service pack 1 as this makes things a lot easier.

Leo...

The simple answer is SP1...

My recommendation if you are building a new cluster is that you Slipstream the service pack. It will solve a lot of issues during the install,...