Hi all,

I am very new to sql server 2005. So please bear with me.

I created a couple ssis package through import and export wizard for our
current testing database in sql management studio. Here are my questions.

I will restore a full backup prodution database and will overwrite this
database later on. To prevent this restoration wipe out my ssis packages, I
can export the ssis packages before doing that and import them after the
restoration, right? How then?

Can these ssis packages be scheduled to run just like schedule run dts in
sql server 2000 using agent job agent?

can these ssis package re-edit in management studio? when I right click and
select property, I didn't see any edit option.
Please instruct. Thank you so much in advance.
--
Betty

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Betty,
I understand that you have three questions:
1. How can you export and import your SSIS packages?
2. Can the SSIS packages be scheduled as job?
3. Can the SSIS packages be re-edited in Management Studio?
If I have misunderstood, please let me know.

For your first question, yes, if you originally saved your SSIS package as
a file, you do not need to do anything for exporting. If you saved the
package in your SQL Server, you can export your SSIS packages via the
following steps:
1. Open SSMS and connect to your Integration Services;
2. Expand the File System folder, click Import Package..., select Package
Location as SQL Server, input your SQL Server instance, select your proper
Authentication Type and click the button right side of Package path, and
then select your package and click OK.
3. Right click your package under File System folder and click Export
Package...,
4. Select Package Location as File System and then select the path you want
to export it to and click OK.

You can import your package according to the step 1 and 2 in above steps.

For your second question, yes, sure. In SSMS, expand your SQL Server Agent,
right click Jobs folder, click New Job..., type a job name, then select
Steps, click New..., input the step name and select Type as SQL Server
Integration Services Package, select Run as "SQL Agent Service Account",
input your SQL Server instance name into Server combo box and select your
proper Windows Authentication type, and then select your package. You can
also switch to other tabs to see if you want to configure other settings.
Then click OK.

For your third question, No, you cannot edit it in SSMS, however you can
edit it in SQL Server Business Intelligence Development Studio (BIDS). Open
BIDS from your SQL Server 2005 start menu, create a new project with the
type of "Integration Services Project", input the project Name and select a
location to store it and then click OK. After that, in Solution Explorer,
right click your SSIS Packages folder, click Add Existing Package in the
shortcut menu, and then select your package and click OK. After that, you
can see your package details in the Control Flow pane and you can also edit
the task by yourself.

You may also want to refer to the following articles regarding developing
SSIS packages:
Creating a Simple ETL Package Tutorial
http://msdn2.microsoft.com/en-us/library/ms169917.aspx
SQL Server Integration Services Samples
http://msdn2.microsoft.com/en-us/library/ms160740.aspx
SQL Server Integration Services
http://msdn2.microsoft.com/en-us/library/ms141026.aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Charles,

Thanks for very detailed instructions.
Does that mean when I do another full backup restoration to overwrite our
current database,
the SSIS packages under MSDB(sql server) will be wiped out, but the SSIS
packages under
Stored Packages/File System will stay, right? so later on I can import them
from
file system into sql server which
will show under Stored Packages/MSDB right?

For BIDS development tool, it seems that it can be installed with either sql
server 2005
or visual studio 2005. If in our sql server 2005 standard edition that I did
not see BISD, where I can download this tool? are there any different
versions because of sql server versions?
I only see Analysis Services, Configuration Tools, Documentation and
Tutorial, Performance Tool and SSMS on our server.

Thank you

--
Betty


"Charles Wang[MSFT]" wrote: