EXEC sp_MSForEachTable 'UPDATE STATISTICS ? with fullscan; print ''?'' '

DBAhawk (12/28/2007)

---

Sounds like I did the right thing, then. If the problem recurs, I'll shorten the log backup interval again perhaps first adding additional backups in the off hours...

Setting the DB to Truncate Log on Checkpoint means you've switched the recovery mode to Simple.

In Simple recovery mode, the inactive portions of the log are discarded once the data...

In 2005 only

SELECT TOP (@Variable) Columns FROM Table

select * from sys.procedures where modify_date > @Date

select * from sys.triggers where modify_date > @date

Or, if you want to check all objects

select * from sys.objects where modify_date > @date

p.s. Please post questions related to SQL 2005 in one of the SQL 2005 forums. Questions in the wrong place may get you inaccurate answers as we're assuming a different...

If you rebuild the index, you don't need to update the statistics. It's done as part of the index rebuild.

The ? is a place holder for the table name.

What error?...

Don't remember. I wasn't counting.

They do give you a fair amount...

Rather don't use the index tuning wizard. It's prone to giving rather sub-optimal suggestions. Learning to tune indexes yourself will get you much better results most of the time.

If you're...

sys.procedures doesn't exist in SQL 2000, and SQL 2000 doesn't have a modification date in sysobjects.

Both those are 2005 and higher features.

Try enclosing the DB name in square brackets

dump transaction [Rose-25-APR07] with no_log

Yes. My point exactly. Do you know why?

What's the compatability mode of the databases i works in and the ones it doesn't?

Dump transaction is deprecated in SQL 2005. You should use Backup Log with truncate_only, or, even...

Any form of function on a column in the where clause prevents index seeks, even something like UPPER, LEFT or the like.