Are you starting the SQL Server service with the local system account or are you using something else?

Here's a link to an article that you might want to take a look at.

http://www.sqldts.com/default.aspx?204

Although with there only being 20 i'd probably just do it manually if it were...

Sounds very much like a permissions problem to me, is the account you're using to run the SP the same one as the DTS execution?

I think it'll be slow

fine for a development or QA environment but i wouldn't do it for anything production related.

The downfall of GUID's are that they're not guarenteed to be unique, mearly random and because of this they are a pain to use in any sort of PK as...

If you post some specific questions you'd like answering i'm sure that there's loads of people that could give you the relevent information.

Right now it's like you're saying 'Hi I...

Hi Jeff,

Chris Hedgate has a good article on moving system databases.

http://www.sqlservercentral.com/columnists/chedgate/movingsystemdatabasesachecklist.asp

The DTS packages are held in the MSDB database so moving that will also move the DTS's at the...

I tend to go with the plain old backup and restore method myself.

If downtime is a problem then you can always do a full backup followed by a differential the...

Useful bit of information that

Hi Jeff,

Nope, they don't let you create triggers on system tables, probably just as well because come SQL 2005 you wont get access to most of them anyway.

Getting back to...

Oh dear,

the old chestnut of whether to keep files in the OS or in the DB rears it's head again

I'm sure that CLR will be usefull for situations where TSQL isn't quite up to the job.

Speaking personally, if a developer (with a lot of assistance) can't write something in...

I agree, with that number of records you'd be better off doing it in batches and controlling the transaction log size yourself.

An index on the date would still be beneficial...

If it were me i'd be thinking of moving all of the data >= '20050501' into a seperate table and then truncating the original, better yet, drop it completely and...

You should just be able to execute the jobs against the msdb database on the new server, the only problem you will face is if they refer to databases that...