With the function app_name() you can know if the trigger is being called by a job.

the result is that is being called by SQL Agent and also is gives you...

Yes it can be done. But be shure you don't have upadtes or deletes from old records, because replication will fail.

When you subscribe to the publisher you can choose that...

You can change the identity property to NOT FOR REPLICATION and assing different seeds and values to each server, or you can also change to Merge replication that will manage...

Are you using replication?

If using transactional replication the hard work will be in the distributor. So my advice is to separate the distribution server into a separate server than the publisher.

DECLARE @test-2 varchar(50)

SET @test-2 = '('+'''Rialto'''+','+'''Vernon'''+')'

SELECT @test-2

EXEC ('IF '+'''Rialto'+'''IN '+@Test+' SELECT '+'''True'''+' ELSE SELECT '+'''False''')

Is seems you create a media set before with that file. To re use it execute the backup with the FORMAT option.

BACKUP DATABASE DBNAme TO DISK = 'e:\backupfilename.bak' WITH FORMAT

You should check for the SET LOCK_TIMEOUT option in the trace to know id the app transaction is setting a lokcing option. But you should find anything.

You should also check 'locks',...

Also:

CREATE PROCEDURE Sp_RepHour

@MaxTime AS INT OUTPUT

AS

SELECT @MaxTime = MAX(CAST(REPLACE(Objvar,':','') As int)) FROM TblBid

GO

And then when calling it:

DECLARE @MaxTime AS INT

EXEC Sp_RepHour @MaxTime = @MaxTime OUTPUT

PRINT @MaxTime

I think you didn't do it in the correct order.

Fist you should delete all the subscriptions to your publicacion, on both server. (In this way you won't have to use...

I think SQL doesn't write in parallel to Log files. It just will use another file, when the first is full. So adding log files won't help.

But it might help...

The Restore verifyonly is the same that "Verify the integrity of the backup upon completion".

But it only checks that the the backup is readable, not the integrity of the data.

So...

In QA:

Tools\Options\Results tab\Maximun characters per column

If the dial up connection goes down the active transaction in the replication process should be roll backed. So you shoudn't have any inconsistant problem.

About the restore, that is easy...

SQL doesn't has to recovery tempdb when restarted, so it doesn't need to log everything in the log file as much as in a user db.

So write...