You can take the help of RPC...

exec LinkedServerName.DatabaseName.dbo.sp_executesql N'

create table dbo.TableName  (colName Varchar(200))'

How to manually remove a replication in SQL Server 2000 or in SQL Server 2005

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

Import the data from excel into permenant temp tables and then write your own tsql based on your needs to parse....

How to import data from Excel to SQL Server

http://support.microsoft.com/default.aspx/kb/321686

I don't think there is any ALTER DATABASE commnad to move the table/index to different filegroup but you can add the filegroup using ALTER DATABASE command...

CREATE CLUSTERED INDEX mynewfilegroup ON...

I think you are right statistics is created on index...

Take a look the following document which explains a lot about statistics and optimizer...

Statistics Used by the Query Optimizer in Microsoft...

I believe you are using 2005 because you posted in 2005 forum so check the Pivot and unpivot ...

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

I believe Jason is right and you have to qualify with database and user name....at the same time make sure user has sufficient rights...

declare @filepath sysname

select @filepath = 'c:\boot.ini'

exec master.dbo.xp_fileexist...

Based on your answers I miss understood Obsolete word...

I though you trying to say some thing wrong with DBCC SHOWCONTIG....

Thanks, for the explanation...

http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/gems-top-10.mspx

Triggers for Logon Events (New in Service Pack 2)

How to stop the transaction log of a SQL Server database from growing unexpectedly

http://support.microsoft.com/default.aspx/kb/873235

A transaction log grows unexpectedly or becomes full on a computer that is running SQL Server

If I am not mistaken DBCC SHOWCONTIG is deprecated but not obsolete.

What about SQL Server 2005 Logon Triggers!!!

http://www.sqlservercentral.com/columnists/FVandeputte/sqlserver2005logontriggers.asp

Run RESTORE HEADERONLY against your tlog backups and  see if there is any issue with LSN...

And mostly log LSN mismatch only when you run log truncation or recovery model changed.

Just shrinking the log file using DBCC SHRINKFILE should not cuase log sequence to break...

There might be something else cuasing to break...mostly truncating the log.

If the tempdb is suspect, I don't think without restarting sql services of the instace will create another tempdb with scripts...