I've had this problem. Since then I make sure that my login is ALWAYS set to default to the master database. In my case the database in question became suspect...

Try

ALTER DATABASE YourDB SET RECOVERY SIMPLE

In this situation you are better off using NOT EXISTS with a correlated subquery.

Hmmm... Upgrade to SQL2K so you can use User Defined Functions?

You can take this function and modify it to suit your needs.

CREATE FUNCTION...

Also, If you create a backup device on each of the machines then they can go anywhere on the machine and your TSQL becomes much easier...

BACKUP DATABASE MyDb TO MyDevice...

I don't have time right now to look up the actual syntax but what you need to do is use the "Parameters" collection and add it to the command object.

Give this a try...

SET NOCOUNT ON

IF EXISTS(SELECT * FROM tempdb..sysobjects WHERE id = object_id('tempdb..#Foo'))

    DROP TABLE #Foo

CREATE TABLE #Foo

    (

    FLD1            int

    , FLD2          nvarchar(25)

    , FLD3          int

    , FLD4         ...

This seems like a great place to use a function rather than a procedure. You would then be able to eliminate the cursor and use the function call directly in...

If you want to do this you can convert your SP to a UDF that returns a table. You will then be able to do something like the following

SELECT *...

The easiest way I have found to debug a trigger is to create a simple stored procedure that will fire the trigger. Then debug the stored procedure in Query Analyzer...

Since you need to do this monthly the best thing to do would be to set up a DTS package and then have a SQL Job run the package once...

Koyan,

Try running sp_helptext sp_help_job when you are in query analyzer in the msdb database.

I'm surprised no one has helped you out yet. I would probably go the OPENXML method. Have the XML passed into an SP as a parameter of type text or...

This could also have been done like this...

UPDATE Foo

SET Keywords = Keywords + @NewKeywords

WHERE...

Fred,

I would double check the DTS package and make sure that the transformations being done are indeed using nvarchar, nchar or ntext. Also make sure that if the package makes...