Performance tuning may be a very complex task. Whether or not to use covering indexes also depend on data types of these columns. Changing indexes may do good for one...

How about this one,

sp_msforeachtable 'UPDATE STATISTICS ? WITH FULLSCAN'

Port number will not be changed. Connection string may need to be changed. In SQL Server 2005, the client tools use SQL Native Client driver.

A lot of jobs can cause slowness of an SQL Server because of they may eat up most resources on this server. Once I wrote a snippet to freeze an...

I did come across it. You may try to kill the process in the Task Manager.

I guess that it is because of memory leak in MS.

In a regular replication setup, these stored procedures should not be there. Please check whether or not there was any other application, or the third party software, applied to your...

Did you check whether or not there is a firewall in between?

Did you shorten the retention time to see whether or not the issue will be gone?

I would like to recommend LOG SHIPPING. Using triggers may result in performance headache when so many rows are added.

By default, BUILTIN\Adminstrators, has sa role.

If you would like to audit the change, you may consider to add triggers on sysusers and sysxlogins tables.

May this link help

http://www.builderau.com.au/program/sqlserver/soa/How-to-import-an-Excel-file-into-SQL-Server-2005-using-Integration-Services/0,339028455,339285948,00.htm

Although it is a doable task, I wonder why we have to do so. If we create a stored procedure in myDB after myProc, why cannot we use the script...

How about adding a trigger in the sysobjects table?

May this link help.

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