The only reason to use a DTS or SSIS package is if you're importing or exporting data. The OP didn't indicate that she was doing that so a T-SQL...

You're welcome. It seems a lot of people forget that a job can have multiple schedules.:D

Here's what I came up with. Someone else might have a better method.

if CHARINDEX('@',@input_str,1) > 1

set @startstr = SUBSTRING(@input_str,1, PATINDEX('%@%',@input_str)- 1)

set @endstr = RIGHT(@input_str,LEN(@input_str) - PATINDEX('%@%',@input_str))

I don't think square brackets are allowed in the command string. Try using quotes around the server/instance name and the package name e.g.

DTSRun/S "CHI-SQL-Servername\instance" /E /N "PackageName"

You can still import all the tables in a single package with precedent constraints controlling flow between data flow tasks and it will still be pretty fast.

It sounds like you're trying to schedule the package by right-clicking the package in Enterprise Manager and selecting "Schedule Package". That method allows you to create one schedule for...

Are you using SET IDENTITY_INSERT ON for each table? Only one table at a time can have it on.

Try DTSRun without the server parameter.

I used xp_getfiledetails for this in SQL 2000. It's not included in SQL 2005, but a couple of guys have created CLR replacements:

http://blogs.conchango.com/jamiethomson/archive/2006/08/24/4400.aspx

http://www.simple-talk.com/sql/learn-sql-server/building-my-first-sql-server-2005-clr/

I haven't tried either of them yet.

Dtexec only works for SSIS packages. You still have to use DTSRun for DTS packages.

The viewing and updating question answered here: http://www.sqlservercentral.com/Forums/Topic491442-5-1.aspx#bm491529. I kind of suspect that if a user can create or update a package, he can execute it also.

Add a role e.g. DTS_Developer to msdb, grant the following permissions to the role:

sp_add_dtspackage EXECUTE

sp_enum_dtspackages EXECUTE

sp_get_dtspackage EXECUTE

sp_get_dtsversion...

This is what SSIS is best at. A package with an Execute SQL task to empty the SQL Server tables and a series of Data Flow tasks to import...

You can see how the syslogins view translates xstatus by looking at the definition of the view. The MS sp_help_revlogin http://support.microsoft.com/kb/246133 uses it to duplicate logins transferred between servers.

Search SSC for "scripting packages". There are a couple of scripts in the Script section that describe how to output all packages.