>> 3.What above error means from SQL Server prospective?

That would mean that your database (ReportServer) is using the full or bulk-logged recovery models. This means that the transaction...

Use DBCC CHECKDB. Preferably before the backup too. If after the restore, DBCC CHECKDB returns consistency errors, you can at least tell if the error was because the...

Things you should be aware of re. RESTORE VERIFYONLY here.

Verifying SQL Server backup files on a file server on a budget here.

The Lite version does support...

How can you tell for sure? In SQL Server 2005, there's a sp_delete_database_backuphistory stored procedure, that can be used to delete backup/restore history...

SQLBOT (10/17/2008)

Here is what happens on a full database backup

1. lock database blocking all transactions

2. place a mark in the tran log

3. release the database lock

4. back up all data...

Restoring an invididual table from a backup may not always give you the same data...

Have you ever tried doing this for real, to validate that statement?

Yes.

I would like to know what are the options I...

Inserting dummy records is no longer necessary in SQL Server 2005, as shown in the example. SQL Server handles that for you when you attempt to shrink the log....

I would suggest checking the permissions of the SQL Server service startup account against the folders where the database files are located, and the file permissions itself. The description...

You can shrink a transaction log file only up to the boundary of a virtual log file. See this link for details.

Your post suggests that your database is still active when the index rebuild is running. If so, you should also consider if you...

That would depend if you have ever performed a full backup of that database. If not, that database would behave as if it was running in the simple recovery...

So the performance impact is most noticeable when your database is UPDATE/DELETE heavy, but not if its INSERT heavy.