I have never had to restore the msdb so I can't say for sure if the packages would be restored as well. Seems logical to assume they would.

However, it does...

The question does specifically request the results from SQL Server 2005.

If it is an error in trying to run the SP, also check to make sure the Agent user has execute rights on the SP.

I'm assuming you are seeing a validation error when you open the package (a yellow bang)? When I see those, I'm usually able to click on the yellow bang and...

UNION ALL won't work unless you have the same number of columns returned in both queries.

From a performance standpoint, I have heard lectures that swing both ways. One says that...

Can you run the package successfully in BIDS?

Do you have the SQL Agent setup to use email? It seems a little quirky but adding the setup for database mail does NOT setup the SQL Agent to use...

We actually have a number of stored procedures that modify data every night and then the SSRS reports are setup to kick off at pre-scheduled times either every morning or...

How about creating the SSRS report and setup the report to run at a particular time after the job has had a reasonable amount of time to complete?

I would setup a separate backup task for each "type" (transaction vs. non-transaction) of database and put them in different folders. Then, you can setup two cleanup tasks to traverse...

In my experience with DB2, I found it easier to create a view with the same query that is running in the management studio. This will allow SSIS to get...

I personally have not had any experience with changing the specific user a package runs under. My understanding is that the package always executes in the Agent User context. As...

It would be helpful if you had a copy of the original package so you could open and test using the development studio. Does anyone there know who developed the...

Do you have another machine you can try this from (do you perhaps have the Business Intelligence Development Studio loaded on the server)?

I just created a new SSIS package, added...

Close the SQL Execute Task and create the variable as part of the SSIS package. Once created in the package, it should be available to map in the SQL Execute...