Well............. it is often my experience that blaming the server or database is usually the cop out for poor code or processes... however, I'd suggest you turn autoupdate stats on,...

here have been a number of articles in SQL Mag which have attempted to define what a DBA does and more importantly the skills required. I'm sure you'd be able...

I note you have auto create stats turned on, however unless you update them regularly you'll probably have problems as the stats go out of date.

A number of problematic etl...

sp_spaceused is known to sometimes be inaccurate

Firstly if you intend to use multiple filegroups it is better to place each on a seperate array.

Second using multiple filegroups means you have to start figuring out how your...

I've air con probs in a server room with disk boxes, found that the practice of not leaving gaps between equipment can be unhelpful, I managed to put single U...

quite so - I actually have a combination of queries and procs that I use to monitor for locking/blocking when the need arises .. ...

Never done this with raid 5 but done several raid 10's.  I never had any problems and "popping" disks in and out of raid 1 mirrors is an accepted method...

You also need to be aware that the performance using a table variable can be far worse than using a #temp table or a temporary permanent table created in tempdb.

table...

you missed the      - please don't missquote me  < grin >

"Those who answered NO must have no idea how real enterprise database environment looks like and how it works."

So harsh!  So true! 

Ah ... but it's not creating a sp as the system stored proc already exists, it's the process of piping the output from a system proc back into a table...

Yeah sort of, as I say we don't have any probs with index rebuilding and transactional replication, technically yes a clustered index rebuild can do as suggested, the downside of...

No the correct answer is yes .. but is this question really worthy of QOD , no offence to the author, but this is a question of the wording of...

we have a large database that is fully replicated and log shipped, the dbcc dbreindex never gave us probs with replication but killed the log shipping !!  12 Gb transaction...