Jeff's right.  There are goofy things you have to do to limit conflicts with this scenario.  Artificially long rows to force each entry onto it's own page, no indexes, and...

I'm not sure why you're doing the dynamic SQL.  What about:

CREATE PROCEDURE [dbo].[SEQVAL] @tblname varchar(100) AS

Begin tran

UPDATE CASE_NUM_SEQ SET CURRVALUE = CURRVALUE + INCR WHERE SEQ_CD = @tblname

SELECT CURRVALUE FROM CASE_NUM_SEQ WHERE SEQ_CD...

Does the account that SQL Server is running under have permission to the file on the other server?

Shouldn't this:

dbo.tblVENDOR ON dbo.tblRAIL.SuperClientVendorId = dbo.tblVENDOR.VendorId ON dbo.tblSPIKE.RailId =

be this:

dbo.tblVENDOR ON dbo.tblRAIL.SuperClientVendorId = dbo.tblVENDOR.VendorId AND  dbo.tblSPIKE.RailId =

The server still does checkpointing so there would be some very minimal log activity. 

Are there any other maintenance plans that run against the databases?  They could produce both log...

When you run it, you run it under your id.  When it runs automaticaly, it runs under the id you have set up for the SQL Server Agent.  Make sure...

This is only required if the names contain special characters that would otherwise render them unusable.  The practice guidelines for our shop state that such names should not be used...

I have one to add to the list:

Being able to explain what you did (or need to do) to people who don't know much about database management systems.

In my past...

There's probably a way to do this with native MS technology, but the way I did this in my last life was to download one of the freeware sets of...

If you can only send in one property id at a time, why do

WHERE

SA_PROPERTY_ID

IN (' + @PropertyID +...

How about:

declare

@auxdata varchar(100)

set

@auxdata = 'TAGmanager_nameTAG MR XX TAG/manager_nameTAG'

SELECT

First off, I'd recommend not using float for real money.  Float is an approximate data type and not very good for keeping dollars and cents straight.  Are the data types...

We're using LiteSpeed quite successfully.  I believe it's delivered with a tool that will uncompress a compressed backup so it can be restored through a normal restore process. 

Put the 'set' before the 'join' and set the table2 column like:

UPDATE Table2 SET Table2.ID = Table1.idcreated INNER JOIN Table1 ON Table2.Description = Table1.Description

Is there a trigger on the table you are inserting into?  Are there referential integrity constraints?