I'm sure you noticed, but the script that I posted will generate trigger code for all of your user tables.  If you need to exclude certain tables, you can add...

Because you will need to know each tables archive table in order to create the triggers, I don't see a way to build one trigger and have it work for...

declare @RowData varchar(100)

SET @RowData = 'http://www.google.com/intl/en_ALL/images/images_hp.gif'

PRINT SUBSTRING(REPLACE(@RowData,'http://',''),1,(CHARINDEX('/',REPLACE(@RowData,'http://',''),1) - 1))

Are you planning on having one archive table for each of your core tables, or one archive table that needs to house all inserts to all 300 tables?

It sounds like you've got a problem with inaccuracies in your indexes.  Is your application frequently dropping and adding indexes? 

What type of login are you using to call xp_cmdshell in SQL Server?  Is it a SQL Server login, or are you using a domain account?  If this is permissions,...

What is the error?

Have you tried to redirect the command shell output to a file?  This could give you some possible error messages to look at.  If it is permissions related, you may...

I know that you can use BCP to generate a format file.  Since BCP is a command line utility, you may want to try to generate an input file programatically. ...

I think that depends on how often your network guys are performing their file system backups.  I would want the backup on tape, whether it be part of a file...

You can kill the processes all at once using EM.  If you right-click the DB and select Detach, you can clear all of the database connections there.  If you do...

It looks like you've covered many of the reasons when to use a named instance.  Other reasons could be security/permissions reasons where you want the SQL Server service account to...

select name, createdate from sysusers where issqluser = 1

Scott does bring up a good point regarding scheduled backup times.  I still don't like the idea of having a problem with one database that affects all of the others in...

It sounds like this may be a datatype issue.  Make sure all of your datatypes in your SQL Server table match the data type and length of the incomming data. ...