I've had a similar problem before when trying to restore a full backup with several successive logs, I had to restore the logs individually one by one to get it...

Obviously on a cluster you want the package to keep on working on failover, in which case you may want to store the package in the msdb, rather than in...

added a few more '

--ALTER PROCEDURE Activity

--AS

Declare @id as nvarchar(2)

Declare @sql as nvarchar(4000)

Declare @fld...

Try downloading the File Properties task from http://www.pragmaticworks.com/FilePropertiesTask.htm which will get you the file details to calulate the latest file.

I've not worked with SP3 before, but I have run into replication problems before when servers were patched at different levels, I wouldn't recommend it without testing it out first,...

As sp_send_dbmail is already geared up to accept variables, it would make most sense to send the email directly from the trigger and not go to the extra overhead of...

try:-

UPDATE tablename

SET [fieldname] = REPLACE([fieldname],'"','')

SSIS can be memory intensive, have the servers have different amounts of memory?

Have you altered the database properties to set trustworthy on?

ALTER DATABASE Databasename SET TRUSTWORTHY ON;

From BOL

Because a database that is attached to an instance of SQL Server cannot be immediately...

Restarting SQL Server should clear tempdb, you could try backup log tempdb with no_log which is a little less dramatic and could work.

You could try writing and saving the query in SQL Server as a stored procedure and linking to that in Access, that's worked for me before.

From BOL

Syntax

SET ARITHABORT { ON | OFF }

SET ARITHABORT must be ON when creating or manipulating indexes on computed columns or indexed views. If SET ARITHABORT is OFF, CREATE, UPDATE,...

I would try stopping SQL Server then setting SQL Server Agent to Manual, then starting SQL Server and then trying to start the agent manually. Just a thought but that...

I have been having similar problems with the SQL Server service, on 2 old SQL Server 2000 boxes after some windows patches have you tried:-

Start / Run

net stop SQLSERVERAGENT...

Can you post the script you are using to create the backup and the script that you use to restore it?