You can see that information in the Job Activity Monitor screen which is displayed immediately under Jobs in the SSMS Object Explorer.

Open the failing package in DTS Designer, click on Package - Properties - Logging tab. Check the 'Log package execution to SQL Server' box and select the server where...

No, but if you do a side-by-side migration, you'll have to copy the packages from the SQL 2000 instance to the SQL 2005 instance. Here are the methods I've...

Yes. It's a hassle, compared to using Enterprise Manager in 2000, but it's all they've given us.

There you go. Glad you got it working.

Anil Kumar Kurra (4/23/2009)

---

Hi All,

Thanks for the reply. If we Back up & restore the database in another server whether all security Objects like Users,

Roles etc...

VG (4/23/2009)

---

Are sure you have added logging to the SSIS package. By deafult there is no logging, you have to define it , with connection string to msdb, or some...

You right to be hesitant. If applications are using the logins in connection strings to connect to SQL Server, there's no way you can change passwords without affecting them....

Actually, according to BOL, members of SQLAgentOperatorRole can enable and disable schedules they don't own.

4 SQLAgentOperatorRole members can enable or disable schedules they do not own by using the stored...

Philip,

I'm still a bit uncertain of what you want to script. The definitions of all jobs are in the sysjobs table in msdb. The definitions of stored procedures...

I've used this script, which is a modified version of sp_help_revlogin, to script out logins, server roles, database users, database roles, and object permissions. Remember that the databases need...

Where did the job originate? Is it still in a SQL 2000 instance? If it is, you can script it out and run the script in Management Studio...

You migrated a DTS package to SSIS, not a job, so you won't find it in SQL Agent. You'll have to create the job seperately.

To see the...

Try changing both workflows leading to 'Intersection Step' to 'On Completion' rather than 'On Success'. Also, take a look at the method described in this article: http://www.sqldts.com/218.aspx.

Please post the SQL code from the Execute SQL task. The CREATE and INSERT are in a single task, correct?

If you're using the table in another task, you might...