You don't need to enable AWE but you may need configure "Lock in pages memory"..

Migration of databases is just backup restore....

It may recompile the all the procedures the database in which you changed compatability....

You may need to start logging the agent info to see what is causing...

How to enable replication agents for logging to output files in SQL Server

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

SQL server is behaving as it suppose to...

When you use wild card at the beginning of the search SQL is always scans the table/index....

Check the following thread...

Transact-SQL Query SQL Server...

AdventureWorks;

name, snapshot_isolation_state

I believe this setting will take effect after SQL agent restart....so restart the agent and check the value...

I have seen the cases even IIS installed server will have this problem...

If IIS already install, uninstall-reinstall will solve the problem...

I can Maintenance cleanup task in MP wizard...

What sql build you are on?

Are you using right CD/media?

I have seen some installation 2 CDs...one contains only client tools other has sql server...

I don't think it is anything to do with server...try on the...

Full backup is required if your dbs are recovered on sql 2005...

You need to copy the logins also after restore...

Check the following article for login transfer...

How to transfer logins and...

Check the following... and use domain account instead of local sa account...

http://msdn2.microsoft.com/en-us/library/ms179530.aspx

Under what did you loging to the machine to install sql server?

Check the sql server installation error file...if there are any other clues...

Check the following links which give you good info...

Improving Data Security by Using SQL Server 2005

http://www.microsoft.com/technet/itshowcase/content/sqldatsec.mspx

http://www.sql-server-performance.com/da_encryption_2005_1.asp

http://www.sql-server-performance.com/da_encryption_2005_2.asp

http://blogs.msdn.com/yukondoit/archive/2005/11/24/496521.aspx

The following article has good info about index usage and procedure too...

Troubleshooting Performance Problems in SQL Server 2005

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

Then use sql trace/profile to do auditing....

What kind of auding you want to do?