Converting it to an integer will not get you what you want.  The result of COUNT() is an integer.  Since integers are whole numbers, dividing integers by integers will generate a...

This script will work in terms of limiting the rows in each batch, but you need a way to determine if the rows already exist in the target table.  As...

I am assuming that your current Recovery Model is Full.  You may want to consider switching it to Bulk-Logged temporarity while you are moving your data over.  If you are...

Also, I would recommend leaving it alone unless you've got a good reason to decrease the memory available to SQL Server.  If this is a stand-alone server, give SQL Server...

Your [Data] column must be a varchar?  To get it to order correctly, you'll need to strip out the MB value and convert it to a numeric value.  For example:

DECLARE...

If you have > 2 GB of memory and you are using AWE, you will also want to apply this patch after the SP4 upgrade:

http://support.microsoft.com/default.aspx?kbid=899761

PW beat me to it, but here's another flavor.

SELECT e.RespondentID

FROM EventLog e

    INNER JOIN tblLookup l

    ON e.RespondentID = l.RespondentID

    LEFT JOIN (SELECT DISTINCT RespondentID FROM EventLog WHERE...

Well, when you set up your trace, make sure that the DatabaseID column is listed in the 'Data Columns' tab on the Trace Properties.  You can then cross reference this...

You are correct as to the code that is causing the problem.  If you are inserting/updating multiple rows, the trigger will fire once after the update, not once per row. ...

You should be able to use the DBid column in Profiler to determine which database the stored procedure is comming from. 

What is the primary key on your table?  Can you post your table DDL?

Whoa, this is totaly different from what you've previously described.  It would be very helpful if you would post your table DDL for both tables as well as sample data...

Will all of the values have the same format of A10?  If so, this will work:

DECLARE @table TABLE (value char(3))

DECLARE @table2 TABLE (id CHAR(1), code CHAR(2))

INSERT INTO @table

SELECT 'A10' UNION...

http://www.sqlservercentral.com/columnists/bknight/stepbystepclustering.asp

If you search SSC for articles on Clustering, you'll find more.

Also, before changing your existing process, it may be worth finding out who or what is locking the file.  Check the virus scanning software on the server.  Make sure it...