Hello -

Is it possible to view all of the SSIS packages in SQL 2005 like we use to
be able to view the DTS packages in SQL 2000? I cannot find anywhere in SQL
Mgmt Studio that displays the SSIS packages.

Thanks
- will

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.

On Jul 15, 10:28 pm, dw <d... (AT) discussions (DOT) microsoft.com> wrote:
Hi Will,
assuming you've the right permission you can view the packages saved
in MSDB connecting to Integration Services.
In Mgmt Studio, Object Explorer instead of connecting to Database
Engine choose Integration Services (Server Type combobox).
In SQL Server 2005 IS is a separate service and most of all, you
cannot run a pkg if you have a Client installation like you did in SQL
2000.
Bye,
M.