Here is the working code.

IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[spCoverageLog]') AND type in (N'P', N'PC'))

DROP PROCEDURE [dbo].[spCoverageLog]

GO

CREATE PROCEDURE [dbo].[spCoverageLog] ( @spName VARCHAR(100) )

AS

BEGIN

UPDATE dbo.CodeCoverage

SET...

Remove the first line in the code that hsould work. Else add a drop procedure statement and a go after that for the code to work fine.

Yes why can't you move the archive to another database. That should do the simple solution for you.

Okie can we do this for our testing. create a stored procedure in the remote server database with the same select query. then call the stored procedure in the linked...

So when you run the query with the linked server do you get any errors. or it returns o rows available.

Use it as [first name] instead of using as "first name"

Use the following

backup log with truncate only and then

dbcc shrinkfile(logname,targetsize)

but be careful doing this in PROD environment.

Delete the previous database backup files and then start the backup job.

Don't go configuring log shipping for 100 of databases in a single server. i am sure you are going to end up in a hardware bottleneck.

You do a detach and attache method so that you can rely on the correct data. Also script jobs and logins and run in the other server.

You can also use the GUI to modify the backup device properties.

You have to restore only a copy of the backup which you say that you don't have. better go for the prod copy and restore there.

USe SQL 2000 MPs to create Mps for those databases don't use 2005 servers as you will land in trouble.

We do have our own CMD script to truncate the timestamp in it and send us the log file. You can create one for your self.

You have used command 1 and the database shows recovery use

alter database dbname with recovery to bring it online. you need not restore it again.