Check the execution plan of both executions and see what is the difference...

It might be parameter sniffing issue...if it is then use RECOMPILE Query Hint to Solve Parameter Sniffing Problems...

http://blogs.msdn.com/khen1234/archive/2005/06/02/424228.aspx

http://www.microsoft.com/technet/prodtechnol/sql/2005/recomp.mspx

It is the same as regular server...

Change the service account and restart the sql services to take effect. you don't need to failover...just offline/online should be fine.

Here is the MS article...

How to configure SQL Server to use more than 2 GB of physical memory

http://support.microsoft.com/kb/274750

Add the /3GB switch in BOOT.ini and enable AWE using SP_Configure...

Insert the Restore Header only information into a table and check the latest backup and restore...

http://www.karaszi.com/SQLServer/util_restore_all_in_file.asp

Check the following...

http://www.sqlservercentral.com/articles/Backup/recoverytoapointintime/1914/

http://www.databasejournal.com/features/mssql/article.php/3530616

http://www.mssqltips.com/tip.asp?tip=1229

Take the sql services offline in cluster admin and start it sql in single user mode from command window to resolve the issue and follow the instruncations in the article...

No, you see the replication agents in replication monitor...

These monitors execute the jobs...so you can stop and disable the job too...and you need to reenable and restart the job...after your...

You can stop the replication agent too...

Only option would be SQL trace (profiler) or check for third party tools...

When you use sp_rev_login script to copy the logins it will generate the script of logins with passwords...means what ever the password at your source server the destination server will...

You may need open a ticket with MS 🙂

If you have previous backup of this database, restore and see if there IS any problem...

Are you able able run the tlog...

Did you run the procedure in the same db where you have the issue...?

If you want to create a text file with procedure output then you can use SSIS or BCP or SQLCMD or osql too...

bcp "exec procedurename" queryout "file.txt" -T -c

1. You can reapply sp2 if neccessary...

if you want to go back to sp1 follow the readme file instructions...

2. You can't drop the table when it is participating in replication...