You canuse a script look up restore log in bol nd be sure to use the no recover option or you can use management studio.

Congrats on getting the data back, now is proably a good time for you to implement a proper backup strategy.

I believe this is when parallel processing is used and sometimes the SPID does block itself, although usually only for a very small amount of time before it is...

have you tried to restore all outstanding logs in sequence starting with the last log to be restored on the standby database.

I don't think its possible to split the clutered index from the table as the clustered index represents the physical ordering of the data in that table.

You could install the 64 bit version of sql and have one instance.

You can install 32 bit sql on 64 bit windows...i believe sql will have 32 bit memeory restrictions.

Search books online (BOL) for creating indexing and dropping indexes

You will setup the backup job on the virtual server not the physical servers. If failover happens the job will still be available when the other node is active.

Hi Gary i haven't got the commands at hand and i can't remeber them of the top of my head, but you can generate the scipts using the redgate backup...

I would imagine the process is similar to windows 2003, assuming that we are picking this up at the SQL Server installation and the windows cluster is already setup and...

Do you have a good recent backup and transaction log backups up to the point failure? When i've had this previoulsy i have had to restore from backup.

I know Paul...

But you are right, you can't rebuild an index using the 'online' option on the standard edition of SQL Server 2005. You can only rebuld indexes online using SQL Server...

thanks jeff

a covering index - Index contains all data returned by the query thus preventing the need for look ups.

You probably haven't lost any data but that's not the recommended wy of migrating, why did you not move the ldf files too?