None of those will do anything...

Are you sure it's the correct log backup?

How are you doing the restores?

Any other way to do what?

Did you read the article I referred you to?

In simple recovery the log is auto-truncated on checkpoints and transaction log backups cannot be run. C00ler, why are you recommending a switch to full recovery?

Pols, is the replication working?...

On what exactly? There are lots of good books with good authors on all sorts of aspects of SQL.

Full backup or log backup?

If log backup,...

Please run the following and post the full and complete output.

DBCC CheckDB(<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Do you have a clean backup of this database? A backup without corruption?

Take a look...

There isn't supposed to be a msdb.log file, so that's not the problem. The MSDB transction log is MSDBLog.ldf

Can you do as the message said and check the SQL error...

Won't help performance. That just fixes incorrect metadata.

Somehow I suspect this query is going to need a rewrite to get...

Happy new year everyone.

Still 5 hours to midnight, but I'm off to a party.

ss-457805's script shows indexes, and only ones where the table has more than 1000 rows. In fact, it will filter out column statistics (stats not associated with indexes) because they...

Per books online (under sys.database_principals)

INFORMATION_SCHEMA and sys

Every database includes two entities that appear as users in catalog views: INFORMATION_SCHEMA and sys. These entities are required by SQL Server. They are...

Create a maintenance plan, drop the 'update statistics' task. Make sure the settings are for all stats and full scan. Save it and run it or schedule it for a...

Run the stats updates regardless. It's one of the things that has to be done with a 2000-2005 upgrade, it's also the one thing that so many people don't do....

So this is a very recent upgrade? In that case you absolutely must run a statistics update on all tables. The stats from SQL 2000 are not great and the...