What I like to do is open the package in DTS Designer and execute each step individually. Since it seems to export data to some of the .xls files,...

If you have Enterprise Edition, MS log shipping is available and you can implement it using a wizard. If you have Standard Edition, these articles walk you through setting...

Database mirroring isn't available before SQL 2005. Maybe you could use log shipping?

That would work, but remember that msdb also contains jobs and backup information. A less intrusive way to recover DTS packages would be to export them to files or...

You can't import SQL 2000 system databases into SQL 2005. IMO, the best option for moving logins and jobs is to script them out in SQL 2000 and run...

Maybe what you're experiencing is the ability in SQL 2005 to create a user without mapping it to a login. See CREATE USER in BOL and this article: http://blogs.msdn.com/raulga/archive/2006/07/03/655587.aspx.

I...

bisso21 (2/10/2009)

---

i'm trying to export the tables and views in a database to another and i'm using ms sql server 2005 enterprise but the problem is that the wizard will...

I don't know what "$" means. I asked who the login belongs to because, if the connection manager in the package specifies Windows authentication, it will use the credentials...

It looks like a login failure one one of the servers. Is the login 'NDIMS\NDIMS-DB13$' you or the SQL Server Agent account? Does it have access to both...

I don't have a script, but I can tell you that you'll find most, if not all, the data you want in two views in msdb: backupfile and backupset.

Also, some...

On way is to use the MS recommended method (see "deploying packages in BOL) and build an Integration Services project in BIDS to create a package depoyment utility that specifies...

See the post by Vinu Verma above where he lists the steps to open a package in Businees Intelligence Development Studio (BIDS; he transposed a couple of the letters).

raphi.levine (2/4/2009)

---

I am having the same issue. I have created an SSIS package using the import data to import data from a flat file and have opted to save...

No. A logical backup device isn't explicitly associated with a database. The only way to imply an association is by naming and by using the device in backup...

Do you get any kind of message when you try to execute the package on the server using the Execute Package utility?