I'm able to edit the packages after moving them to the server select "Package Configurations" from the BIDS menu, and edit the configuration file path.

Create an operator with multiple email addresses and use that in the job notification. You create operators by expanding SQL Server Agent in SSMS, right-clicking on Operators, and choosing...

I move the packages and config files to the server then fix the paths. Don't forget to set the Protection level in the packages to something other than the...

Check these:

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

http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

There are also lots of articles on SSC about upgrading and migrating from SQL 2000 to SQL 2005. Just use the search function at the top of the...

dtexecui only works for SSIS packages. You have to have the dtsrunui utility to generate DTSRUN commands. If you have an SQL 2000 installation, you should be able...

Hansen,

Are you talking about login passwords in connections or owner passwords on packages? It sounds like Adi's vbscript is a good option for changing connections, but I don't know...

I agree with Brian about permission for sp_attach_db, but SQL 2000 BOL says only members of sysadmin can execute sp_detach_db (I'm assuming the OP is using SQL 2000).

What method...

Protection level

Since your client is going to run the package, I suggest using EncryptAllWithPassword because if you use one of the ...UserKey options, only the package creator...

If the server name is hard coded in the package connection, there isn't a way to change it as you're copying it. You'll have to open each package and...

In msdb, deny EXECUTE permission to public (and the developer if he's a user in the database) to sp_add_dtspackage.

In early versions of SQL 2000, members of public could create DTS...

You can find the all the service accounts by looking at SQL Server 2005 Services in SQL Server Configuration Manager on the server where SQL Server is installed. Look...

Do you mean you're trying to connect to the...

If you use the syntax that Lowell suggested i.e. "CREATE USER [bob] FOR LOGIN [bob]" the user bob is mapped to the login bob. Otherwise, you end up with...

The first thing that comes to mind is that the user isn't being created for an existing login.

Check these tutorials:

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

http://www.jumpstarttv.com/Channel.aspx?cat=c871236d-8554-42e3-8683-4d422356c0bd