Lowell and Ninja have hit it right on the nose. The only caveat I would add is to NOT take the Tuning Advisor 'literally' and as an absolute expert. If...

"It's on a developer machine with a gig of ram, but the machine is not doing anything else."

SET SARCASM_MODE ON -- with a dose of reality

... and you expect performance...

US English 20+ years.

IUf you are transferring logins, soimetimes users within databases need to be 'tweaked' as well. Below is a SP to assist:

---

--- fix_users_login.sql

---

 use master

 go

 set quoted_identifier off

 go

 if exists (select * from dbo.sysobjects...

If the environment is stable then I would leave it alone for the time being. The idea of no support for SP3a is not quite correct. If you have an...

You will not be able to bcp in syslogins (it is actually a view). The underlying table is actually sysxlogins. Again you will not be abkle to bcp in to...

The only database that I know of is the one between the DBA's ears

hmmm ... it does not add up .... one drive failing on RAID 5 still leaves the array, which shows as one logical unit, usable. Is this a shared RAID...

hmmm ... WTAWTAW and what I read are 2 different things ...

Glad to be able to share the information.

Unless you are having performance complaints, I'd reindex weekly. As for STATS and USAGE, daily with 100% sample.

On 90% of my databases (the ones smaller than 100 Gb) I do STATS and USAGE nightly. On the larger databases I execute weekly. As for the reindex, It's kind...

No - unless that is the only application database on the SQL Server. sp_recompile 'tablename' marks any stored procedure that executes against that specific table for recompile the next time that it...

Agreed.

In this case UPDATEUSAGE may help performance because of the possibly high insert activity.

sp_recompile for the table is a must. After updating statistics, the execution plans of any stored procedures...