Check BOL topic "orphaned transactions [SQL Server]"

Here is the list of bugs fixed in sp2...

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

I am not sure it is a bug and as pervious poster mentioned your create index is not online operation unless...

You get the could not bulk-copy error when your disk ran out of space where replication fold exists...

I don't think your snapshot cause anything to remove your columns...

Some one might...

What kind of encryption you are doing?

SQL server 2005 has SMTP mail called database mail check BOL for more details...

Check body format option in sp_send_dbmail procedure...

There is no problem running queries across two or more databases is not a problem and it will not be a peformance trade off.

Did you enabled database mail procedures in SAC?

Check sql error and mail log for more info...

Check msdb..backupset system table which contains backupsize column...

I don't know how DDL trigger is useful in this case but...

You can try granting  DDL admin rights....

You need to use SQL SERVER MANAGERMENT STUDIO...

Start/All programs/sql server 2005/sql server management studio

connect to database serivices...

You can make use of xp_delete_file  or xp_cmdshell...

xp_delete_file  procedure is used in maintenace plans to delete old backups...

DECLARE

@ThreeDays VARCHAR(255)

By default in SQL express edition remote connections are disabled...

Enable remote connection using SARFACE AREA CONFIGURATION ....

Load the text files to a permanant temp table using bulk insert...and insert required data from temp table to main table....

select count(*) from sysprocesses where db_name(dbid)= '<dbname>'

Do you/sql have read/write access to the drive...

http://sqljunkies.com/WebLog/madhivanan/archive/2005/07/27/16233.aspx