Once you determine which step failed and where you want to restart, right-click on the job in SSMS and select "Start Job at Step...". Then you can select which...

Yeah, sorry. Use this for SQL 2000:

declare @username as varchar(50)

set @username = 'user name'

select cast(o.name as varchar(45))as 'object'

,case p.action

when...

You could just copy code you want to use out of sp_helprotect. Or search this site's script section for "list database permissions". I use this to quickly get...

Only Windows authentication is available for SSIS.

You can see this by clicking on "Members" in the upper right corner of this page and sorting by number of posts. The numbers shown are actually points which...

select LEFT(Column1,CHARINDEX('-',Column1)- 1)

from Table1

You can see all string functions by searching for "String Functions" in BooksOnLine.

You're correct in your interpretation of cross-database ownership chaining. The objects in both databases must have the same owner unless you grant the applicaton user SELECT permission on the...

You'll need to rebuild the table. Create a new table with the identity seed and increment set to what you want, insert data from the original table, drop the...

I don't blame you for not wanting to make developers members of db_owner, but I haven't found any way to make the database diagrams shareable. The only choices seem...

You're still trying to run the package in a job step, right? I have lots of jobs that run legacy DTS packages and their steps look like this:

Type:

Operating system...

You have the right idea. The difference is that TRUNCATE TABLE is a "non-transferable" permission, unlike SELECT, DELETE, UPDATE, and INSERT. See "TRUNCATE TABLE (Transact-SQL)" in BOL.

I'm stumped. Maybe you should enable package logging and see if you get any more error details.

Is the service account a domain login?

Right. Backup the location where the packages are run from. It should be obvious where they are when you look at the step in the SQL Server job....

Please post the error that occurs when the package is run in a scheduled job. This sure sounds like a permissions problem so I want to clarify something. ...