Sorry, I don't have any Oracle databases.  Hopefully, someone who does will see this thread.

Greg

I think the original poster is thinking of scripting as a way to backup his database.  Hopefully, the responses in this thread have dissuaded him of that notion.

Greg

It worked for me when I scripted linked servers on a SQL 2000 instance and created them on a SQL 2005 instance.  Keep in mind that you can't find a...

I'm glad you found a workaround.  It's curious that the article says the problems was corrected in SP1, yet you still have it with SP3 applied.

Greg

Yeah, if you want the user to be able to read all the user tables in the database.

Greg

I think you can query sysprocesses to see which database is being backed up.

select dbid, cmd

from master.dbo.sysprocesses

where cmd like '%backup%'

Greg

Additionally, a backup save everything in the database: tables, views, stored procedures, functions, users, etc.  Scripting tables only allows you to recreate the table schema.

To get started with backups, maybe you...

1. create a login, preferably one that uses Windows authentication

2. create a database user by granting database access to the login

3. give the user SELECT permission to the objects you...

You can't control the permissions for the role.  As the name suggests, permissions are "fixed" and can't be changed. 

If both logins are members of the sysadmin role, they should...

Was this database attached or restored from another instance?  Users go with a database when it's moved, but logins don't. 

Greg

What kind of workflow leads into the task that doesn't run?  Try setting it to "on completion" and see if the task executes every time.

Greg

Maybe I misunderstood your original question.  Do you want the job to succeed even if the step that executes the DTS package fails or do you want to figure out...

If you open an error log in Enterprise Manager, you'll see a message at startup that says, 'Logging SQL Server messages in file filepath'.

Greg

Script jobs in Enterprise Manager and run the script in SQL 2005.

Save DTS packages as files and open them in SQL 2005 Management Studio - Management - Legacy - Data...

Have you enabled package logging in the DTS package?  That should tell you what error, if any, is generated when the package executes.

Greg