First, check the path of the files of Principal and Mirror DBs- they should be if possible identical,

then check account permissions.

This can help-BOL: "Troubleshooting Database Mirroring Setup"

In Sql Server 2005 FTS works on whole table, i.e. first all records are searched and then indexes applied

(another words, first FTS returns let say 1 M records and then...

Can you please clarify what is "image table"?

Check BOL: "Administering Multiple Servers Using Central Management Servers"

Hope this can help

We used Red Gate SqlBackup 5.0 (great stuff- compression, multiple CPUs, friendly UI) to backup to disks

DBs from 20 GB to 5 TB and then Symantec Backup Exec to...

Just to add my 2 cents-

pay attention to versions compatibility. I recently migrated 2005 Ent to 2008 Std and because of this issue (downgrade versions) could not use detach/attach.

Thanks Paul-

that means there is actually way to confirm that particular transaction was backed up.

But still there is no warrantee that all changes were backed up.

"Essentially, both full and differential backups only back up the data, although they do also back up enough of the transaction log to enable recovery of the backed up data,...

It can be Statistics related issue (as rebuild index updates statistics)

For 2-3 years (do not remember exactly)- no problem at all.

I use it for pretty big DBs backup (> 1 TB) and small ones.

Before (when MD did not have backup...

Just to share my experience with 4.5 TB database backup -

use Red Gate Sql Backup 5, compression- 2, backup locally first then move to remote storage

Make sense.

Thanks a lot.

Gail,

Just to clarify- if physical order for clustered index in not always the same as logical order (and I read this before) why in this case page split happens...

OK, this is what I found (may be it can help somebody else with same issue):

from this article http://msdn.microsoft.com/en-us/library/cc917695.aspx#Full-text_Configuration

I got that unfortunately my assumption was correct: "As...

What you said make sense, i.e. under no possible condition sql service reboot can result in something bad (does not matter- corruption, integrity break, etc). This is good. But probably...