Packages and jobs are stored in the msdb database.  Back up the database.

Greg

1. No issues with our clusters, but we've been using per process licensing since installation.

2. I don't think it will affect them at all.

3. I looked at several of our...

Maybe you can use this query with a little tweaking.

select Object_name = o.name,

          Object_type = o.xtype, 

          Data_located_on_filegroup = g.groupname,

          Data_located_on_file = s.name

   from sysobjects o, sysfiles s, sysindexes i, sysfilegroups g

   where ...

It's okay to delete from the tables.  There are even stored procedures in MSDB that will do it - sp_dump_dtspackagelog and sp_dump_dtssteplog, though your idea of keeping them for x...

To find dependencies for the stored procedure, run this in Query Analyzer:

sp_depends 'dpeter.storedprocedurename'

No.  The columns are presented in the order they occur in the table.

Greg

One thing I've read about TargetServersRole is that it's not guaranteed to be supported by MS in the future.  It's security was changed in SP3a and I'm sure that threw...

Just ask for a full database backup of the database on whatever media your new ISP wants.  I assume the database hasn't been created on the new ISP's server yet,...

Can you get a backup of the original database from the first ISP?  That would be better than an export to Access because it would include all the database settings,...

You might be stuck with something kludgy like having the child package update an error table when a task fails and having the parent package query the table on return from...

Try setting in the child package properties logging Tab: Fail Package on First Error. Otherwise even if the task fails, the package does not - and your calling package still...

Also see "Clustered Indexes" in BooksOnLine.

Greg

Helen,

Here's an ActiveX Script that will overwrite the log each time the package runs.

Greg

http://www.sqldts.com/default.aspx?240

I've used this for a couplr of years and it seems to work pretty well:

-- search for string in stored procedures in DB

--

-- note: the reason this joins...

Dan,

You could import into a "staging" table with separate name columns, then concatenate as you move the data from there to your "real" table.

Greg