Make sa to be the owner of the job

Try to run it through query analyzer and turn on the server trace option and then monitor the performance. This would give you some idea about what statement is taking the...

I think you might want to have more than 10% additional space.If you run dbcc log or also ::fn_dblog, it shows almost 80 columns  which includes objectid, pageid, element length,...

You can use the nolock hint in your select statement or you can set the transaction isolation to read uncommitted.

I think you did cover everything. But something you might want to look at is any locking/blocking in the databases. This will give you a good idea about the health...

You can specify the authentication mode to Windows or Mixed. When you set to mixed, you can log in with your SQL or Windows id. By default, the BUITIN\Administrators group has...

Sorry, please ignore the above post.

3.2 Place the index and data files on different disks(RAID10). Place the log file on a different disk(RAID 1) . Place the tempdb on its own drive.

3.3 Depends. Weekly...

3.2 Place the index and data files on different disks(RAID10). Place the log file on a different disk(RAID 1) . Place the tempdb on its own drive.

3.3 Depends. Weekly full,...

There is an advanced parameter called query governor cost limit which you can set using sp_configure. The default value is 0 which means that however long the query is, it...

Can you post your query

When you rebuild indexes, the statistics do get recomputed. If you want to create indexes without rebuilding statistics, than you can use the create index statement with STATISTICS_NORECOMPUTE clause.

DECLARE @query varchar (8000)

declare @varoutfile varchar(20)

declare @bcp varchar(500)

declare @status int

set @varoutfile = 'c:\test.xml'

SET @query = 'SELECT ''<ROOT> ''SELECT name FROM sysobjects FOR XML AUTO,ELEMENTS SELECT ''<ROOT>'''     

SELECT @bcp...

I think your best bet would be  to rebuild your indexes after you perform the de-frag.

min = 0 means dynamic allocation. max =32 is the max. no. of processors that SQL Server supports. your run_value should be set to 0 in your case.