It will rollback.

Also see this

http://msdn.microsoft.com/en-gb/library/ms187844.aspx

Restore latest full backup and subsequent log backups.

Why are you running sp_updatestats on the database? why these cant be done off peak hours. If you really require more complex index maintenance (if the size is big) try...

I think this is the intended behavior. It is recommended you use set for assignment. Select = will leave the variable untouched if the statement returns no rows.

Try enabling 'include execution trace' in agent properties. You will get more information in the agent log.

Performance Dashboard

Do you have many bulk operations? if so you can try changing recovery model to Bulk logged (After some reading on the topic).

Have you tried using port number in the connection string?

http://blogs.msdn.com/sql_protocols/archive/2006/02/27/unable-to-connect-to-a-sql-server-named-instance-on-a-cluster.aspx

Forcing an index may not be good always.

It says for the plan to use the index even if the optimizer thinks otherwise.

Nolock hint may seem faster since the query...

Sorry my earlier post gives you the instance nam

to get hostname,

select serverproperty('ComputerNamePhysicalNetBIOS')

EXEC master..xp_getnetname

Check the service. does the instance use the default port? How do you connect using ip/hostname. Some times if you have issues with dns the hostname may not work. Ping...

can you post the execution plan?

Also CPACKET denotes parallelism waits. You might want to expiriment with MAXDOP settings

You can also query this counter

select * from sys.dm_os_performance_counters where counter_name like '%user connections%'