How about this?

Create 3 schedules for the partition process:

Monthly 1st Saturday of every 1 month

Monthly 2nd Saturday of every 1...

I think the underlying cause is the same on both instances. SQL Server Service must run as a domain account in order to send mail using xp_sendmail. ...

Could SSIS have been accidentally uninstalled? Confirm that the service exists in SQL Server Configuration Manager.

Granting permissions on sysdtspackages will achieve some of the same. Sysdtspackagelog, sysdtssteplog, and sysdtstasklog are seperate tables, but they're only important when executing a package.

Adam,

1) I think you're right about pulling rather than pushing the data if you can't put a package and a job on the SQL 2005 instance.

2) You can select the...

If you only want developers to work with legacy DTS packages, try creating a database role in msdb e.g. DTS_Developer and granting it EXECUTE permission to these stored procedures:

sp_enum_dtspackagelog

sp_enum_dtspackages

sp_enum_dtssteplog

sp_enum_dtstasklog

sp_get_dtspackage

sp_get_dtsversion

sp_drop_dtspackage

sp_add_dtspackage

Add developers...

The same way you'd rename any database. Either right-click in SSMS and select 'rename' or user sp_renamedb.

sp_renamedb 'Client.Database', 'NewDatabase'

or Alter Database

alter database [Client.Database] modify name = [NewDatabase]

Have you tried using DTS on the SQL 2000 instance to import from the SQL 2005 database or SSIS to export to SQL 2000? While you can't register 2005...

but I would like to occasionally make new...

I haven't worked with Oracle since we moved to SQL Server, but I got a lot of info from these sites. I recommend getting the classroom training as soon...

Heh, don't tell anyone, 😉 but you can create a new DTS package in SSMS by opening an existing legacy DTS package and saving it with a new name. ...

Packages in jobs run in the security context of the SQL Server Agent service account regardless of the job owner. If the SQL Servre Agent account is not a...

Try this. I'll bet you can use it to create scripts.

declare @username as varchar(50)

set @username = 'your role'

select O.name, U.name,permission_name from sys.database_permissions

join sys.sysusers U on grantee_principal_id = uid

...

To tell the truth, I usually add logins in SQL Server Management Studio though I have created scripts using CREATE LOGIN. I haven't had any particular problem with it...

And SSIS uses Bulk Insert which is a lot faster when copying a large amount of data.