Use method 2 described in this article to transfer logins: http://support.microsoft.com/kb/246133. As for jobs and schema, it's so much easier to script them in SSMS or Enterprise Manager that...

In SSMS, expand the database, Security, Users, properties of the user you want to delete. The General pane of user properites shows the schemas owned by the user. ...

Please post the error message.

sa won't be able to access files since it's a SQL Server login. Just grant permissions on the file to FNS\SYSTEM.DTSRun.

You're probably using Windows Authentication in your Transform Data task. When you run the package it uses your login and you have permission to access the flat file, so...

I don't understand your question. Would you elaborate please?

Thanks

Like I said, sa has the same privileges as the SQL Agent account so we didn't have to do anything special for permissions.

It's a bad idea to logon...

John Paul-702936 (3/3/2010)

---

Hi .. thanks for reply ...

Just want to know if any of the Step a,b,c,d fails .. need to get failure message ... it should not pass...

We used to make the SQL Agent account, which is a domain account, the owner of all jobs and it almost always worked well. However, when the SQL Server...

That will work. You could also use a Send Mail task in DTS if you have MAPI on the server.

Have you seen this one? http://www.sqlservercentral.com/scripts/SQL+Server+7%2c+2000/61878/. I've used it to document some of my instances.

SQLAgentUserRole works if you want a non-admin to run a job. The drawback, in my mind, is that the user can also modify or delete the job.

An...

1- The objects are created in the current database, not master.

2- Any user with access to the database can create a diagram.

In addition, the diagram is only viewable by it's...

The objects are dbo.sysdiagrams, dbo.upgraddiagrams, dbo.helpdiagrams, dbo.helpdiagramdefinition,dbo.sp_creatediagram, dbo.sp_renamediagram, dbo.sp_alterdiagram, and dbo.sp_dropdiagram.

They're created when a member of syadmin or a member of db_owner answers yes to the install question. ...

Just substitute R2\501253666 for DOMAIN\NEWLOGIN. Repeat the two statements for each login and run the script in a query window in SSMS