Hi Guys,

I have just moved from SS2000 to SS20053 and I can not find SSIS packages.
I have created a SSIS package and I now want to modify it.

Can anyone tell me where to look for SSIS packages saved on the server?

TIA
Peter

Hi Peter,

Try this -

Launch Microsoft SQL Server Management Studio

Look for the Object Explorer on the left-hand side

Click Connect

Choose "Integration Services"

Connect to the appropriate database server

You should now see a new item in the Object Explorer


Hope that helps!!

Glen




Peter Longstaff wrote:

Thanks for that Todd,

one more simple question. How do I schedule the packages to run ?

TIA
Peter

=?Utf-8?B?VG9kZCBD?= <ToddC (AT) discussions (DOT) microsoft.com> wrote in
news:FDEF2B41-A21E-49BB-B3C4-CB9A3D6E45DF (AT) microsoft (DOT) com:

Todd C wrote:

I hope that is not the case. My packages are now in msdb.
In BIDS, I created a project to make some changes.
In this project, I added existing package (one at a time) and made my
edits.

Are you telling me that my saved changes are not now reflected in msdb?
Are you writing that I have to re-import the packages?
If so, is there a "Replace" option on the import?

Say it isn't so.

IanO

Hello IanO,


Correct. When you opened an existing package in BIDs you will note that
the package was copied to your project folder.


Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Hello Peter,

Have a look here

http://wiki.sqlis.com/default.aspx/S...gesInSSMS.html


Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Todd C wrote:
Hello Todd and Alan
Let me cast this in another light. My instincts of how SSIS works
(so far) have been wrong, wrong and wrong. It seemed to me, if I
exported the package from msdb to file system location for changes and
testing then I would, of course, expect to re-import the package.

However, in the case of some emergency patch, I presumed that when I
said add existing package to this project (and did not do an import)
that what was happening was some sort of pointer to the package in msdb
and that the edits would be there implicitly.

Earlier, I was confused about the Project metaphor. I expected the
entire project with all the contained packages to be compiled and
linked for execution. So the requirement for a connection object to
tell the system where a child package was located was not on my radar
scope.

Now that I am becoming more SSIS aware, I realize that I could use your
help to make sure the package that is executed is really the last one I
changed. So I propose to write to the existing log for each package
"Date Last Changed 15 Dec 2006 9:49 AM".
This morning I found:
Dim dataBytes(0) As Byte
Dts.Log("My custom message here", 0, dataBytes)

Is this sufficient?

I will add another Script control to every package to do this unless
you can recommend another way to accomplish this goal.

Thanks again,
IanO

Todd C wrote:
Hello Todd and Alan
Let me cast this in another light. My instincts of how SSIS works
(so far) have been wrong, wrong and wrong. It seemed to me, if I
exported the package from msdb to file system location for changes and
testing then I would, of course, expect to re-import the package.

However, in the case of some emergency patch, I presumed that when I
said add existing package to this project (and did not do an import)
that what was happening was some sort of pointer to the package in msdb
and that the edits would be there implicitly.

Earlier, I was confused about the Project metaphor. I expected the
entire project with all the contained packages to be compiled and
linked for execution. So the requirement for a connection object to
tell the system where a child package was located was not on my radar
scope.

Now that I am becoming more SSIS aware, I realize that I could use your
help to make sure the package that is executed is really the last one I
changed. So I propose to write to the existing log for each package
"Date Last Changed 15 Dec 2006 9:49 AM".
This morning I found:
Dim dataBytes(0) As Byte
Dts.Log("My custom message here", 0, dataBytes)

Is this sufficient?

I will add another Script control to every package to do this unless
you can recommend another way to accomplish this goal.

Thanks again,
IanO

I'm not a Script expert so can't advise you on that front.

However, I can tell you what I do:
I have started a Package Log table for my Data Warehouse packages. Then in
each Package, I do this:
1) Very first Task is an Execute SQL that runs a SP that 'seeds' the log
table with one new row and returns the @@Identity integer value to the
package through the Result Set and stores it in a Variable.
2) In the Data Flow, I use Row Count Transforms to count rows in the various
paths and store those in variables.
3) The last step is another SQL Task, running a second SP that UPDATES the
log table record from step 1 with the various Row Count variables.

There are also a lot of System variables that you can make use of, like
VersionMajor, MachineName, PackageName, ContainerStartTime, etc.

I bet all those can be accessed inside a Script task.

One last hint: Once you have a good design, make yourself a package template.

HTH
--
Todd Chittenden


"IanO" wrote: