You can open and edit a package that is stored in msdb. After you've opened a solution in BIDS, right-click on SSIS Packages and select "Add Existing Package". ...

It means they're the same user if the user modifying the module is the current owner of module. You don't have own a module to modify it.

For example: stored...

What you want to do is change the login mapped to dbo in the database. Use sp_changedbowner to do that in the current database:

sp_changedbowner 'td'

Note: td cannot be a...

I think you're getting the error because SQL Server 2005 Upgrade Advisor will only analyze SQL 7.0 and SQL 2000 instances. The compatibility level of the databases doesn't matter.

You...

Depends on your definition of incremental backup. A differential backup backs up extents modified since the last full backup.

You would have to edit the config file after creating it if you want to keep any connection passwords in it. Passwords aren't saved in the file, so you...

You'll need to set the protection level of the package to EncryptAllWithPassword or EncryptSensitiveWithPassowrd before saving it. See BOL: http://msdn.microsoft.com/en-us/library/ms141747(SQL.90).aspx

After you save the package to a .dtsx file, you can import it into SQL Server by opening SSMS, connect to Integration Services, expand Stored Packages, right-click on MSDB, and...

If you're saving them to SQL Server, they're stored in msdb and will be backed up when you backup that database. If you save them to the file system,...

I recommend running SQL Server 2005 Upgrade Advisor to see which packages will migrate easily and which will need to be rewritten.

Some articles that have helped me:

http://msdn.microsoft.com/en-us/library/cc768544.aspx

http://msdn.microsoft.com/en-us/library/ms143501.aspx

If you open the top level of the package (the one with the name of the package), you'll get the latest version.

I would regenerate the DTSRUN command and past it...

In the half dozen migrations we've done, we've used the good old sp_help_revlogins method from MS:

http://support.microsoft.com/kb/246133/en-us. It outputs a script that can be executed in the SQL 2005 instance...

Re: scripting jobs, you can script all the jobs in an instance into one file in SSMS if you click on "Jobs" in Object Explorer then highlight all the jobs...

sri,

Create the job step and select "SQL Server Integration Services Package" in the "Type" dropdown. When you do, you'll see a bunch of tabs where you can enter the...

Is the source or destination datbase on the new SQL 2005 server? If so, did you change the connection in the package itself?