Why do you want to execute the package from a stored procedure instead of executing it in a job step?

There are ways to execute a package in a stored...

Are you using a mapped drive in the file path?  If so, try using a UNC path.  Does the Package fail and generate an error message?

Greg

Sysjobhistory doesn't get written to until the job completes.  You have to look at sysprocesses to see what's currently executing.

Try this:

select RTrim(J.Name),last_batch

    from msdb..sysjobs J with (nolock)

    inner join  master..sysprocesses RP with...

Yes, you can export to files then import the files to the new database.  You'll just have to be able to either see the files from the new server or...

Log shipping is a warm standby solution rather than hot standby because there is no automatic failover.  Since log shipping isn't available in SQL 2000 Standard Edition, you'd need to...

Use this query to find which Product_ids are duplicated:

SELECT

DuplicateCount = COUNT(*),

           Product_id

FROM TableWithDuplicates

GROUP BY Product_id

You can use DTS to copy the data after you've created the new database.  Try the Import/Export wizard and choose "Copy objects and data between SQL Server databases".

Greg

What kind of backup is it?  Database or log?  I've seen that message when the job tries to do a log backup of a database that's set to Simple recovery...

Sorry, I don't know anything about that.  Try http://www.sqlsecurity.com.

Greg

Arun,

There's a script in the script section of this site that will script out all the linked servers in an instance.  I used it recently to transfer linked servers from...

Hi Eamon,

I'll bet the names you'd like to see are the descriptions you entered when you created the tasks.  Unfortunately, those aren't stored in sysdtssteplog.  Are you set on finding...

I don't know if you can get it in T-SQL, but you can see the version by looking at the properties of C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.exe, which is the executable...

No. 

Greg

Bob,

You should be able to run the package with no changes.  I've created a package in SQL  2000 that exports data to a database in a SQL 2005 instance and...

Aside from the GUID thing I mentioned, I didn't have any trouble running a legacy DTS package in a job in SQL 2005.  I guess you should make sure the...