Never rely on just an application to maintain the integrity of your database. Other applications (and DBAs!!) may also modify your data.

If there's nothing in the database to enforce...

A row could be missing from query 1, if the same delegate_name is against more than 1 edrs_no, and the one assigned to row number 1 is not '120211637'

Your sub...

Why not backup to disk, and then copy from disk to tape?

How good is the network between the subscriber and publisher?

Transactional replication has to commit changes to the subscriber as a whole transaction (or multiple of transactions, depending on your setting...

The FILE= option is only relevant when more than one backup is in a single backup file (i.e. backups are specified with NOINIT).

If it isn't working with FILE=2, then that's...

That shows more Data than Reserved... have you run sp_spaceused @updateusage=true

If you mean that you only want to allow Windows Authentication, then in Enterprise Manager, right click the server and select properties, then look on the Security tab

What else is the subscriber doing?

I have seen this sort of thing before, where the subscriber was being used for reporting. The activity on the subscriber was blocking the replication...

Again, as you have posted no schema details, I can only guess, rather than test a solution.

The WHERE clause is in the wrong place. So you will probably want something...

XP_cmdshell lives in the master database, so if you run this in the context of any other database, you have to specify

exec master..xp_cmdshell .....

As you didn't post any schema details, I couldn't test the first part of your script. The SET statements should be SELECT statements. Try this.

DECLARE @CALL int

SELECT @CALL = Call_Num...

I don't think there is an easy solution to this without formatting the dates to a known format.

You may find a solution that appears to work, as SQL Server knows...

I presume you are getting syntax errors on the xp_cmdshell line.

Try this instead

DECLARE @CALL int

SET @CALL = Call_Num From Table_2

DECLARE @PC nchar(10)

SET @PC = Schedular_PC From Table_2

DECLARE @cmd nvarchar(255)

set...

As long as you know what format the dates you are receiving are in, then format them into YYYYMMDD format.

That way, you shouldn't have a problem, regardless of the language...

I had a similar issue a few years ago when installing SP3 for SQL Server 2000. The installation failed on the passive node on a few occasions, saying it was...