Maybe because its Friday afternoon but I've been looking for a
definitive statement on the method of specifying that this next build
will be for Production and all the Debug overhead will be deleted from
the result.

It has been decided that we will run our production jobs from the MSDB
database. When the Build button is clicked, is there some sort of
compilation that creates msil or machine code that can be directed to
the MSDB database (or anywhere else)? All during my development, I
have just clicked the green arrow button on the toolbar. Years of
development using 3G languages still inhabit my thinking of development
vs production.

Yesterday, Allan replied to my question saying that the Project really
has no consequences in the production environment, its just an
organizational tool for the developer. So I now ask, "Am I supposed to
"compile / build' each package individually and somehow move the
compiled /built results to the MSDB database.

What other question should I have asked?

Thanks,
IanO

Hey Ian,

You can import the package into sql server 2005.

1. Open SQL Manager,
2. Open object explorer.
3. Click Connect and select Integration Services.
4. type in the name of sever and security info and click connect.
5. right click msdb and select import.

You should be able to browse to the folder your package is located and
import the package. Let me know if this helps. Have a good weekend!

Jay


IanO wrote:

Hey Ian,

You can import the package into sql server 2005.

1. Open SQL Manager,
2. Open object explorer.
3. Click Connect and select Integration Services.
4. type in the name of sever and security info and click connect.
5. right click msdb and select import.

You should be able to browse to the folder your package is located and
import the package. Let me know if this helps. Have a good weekend!

Jay


IanO wrote:

Hey Ian,

You can import the package into sql server 2005.

1. Open SQL Manager,
2. Open object explorer.
3. Click Connect and select Integration Services.
4. type in the name of sever and security info and click connect.
5. right click msdb and select import.

You should be able to browse to the folder your package is located and
import the package. Let me know if this helps. Have a good weekend!

Jay


IanO wrote:

Hello IanO,


There are a number of ways of deploying your packages to MSDB.

You can simply take the .dtsx file that is in your solution and import that
from SSMS into the SSIS Service.
You can create a deployment manifest to do this as well.

Have a look in BOL here

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqltut9/html/de18468c-cff3-48f4-99ec-6863610e5886.htm


Regards

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

Thanks for the replies. I will be going through the BOL exercise this
morning.

A couple more questions, please:

1. Copy the file from the Solution...Or Copy from the bin directory.

2. Am I to understand that we continue to deal with the Package
Source and not a compiled version in production?

3. If we deal with Sources, how to I determine which one was last
changed?
The one on the Server in msdb or the the one on the file system?

[In DTS, I have always used just the version where it was created with
Enterprise Manager, I never had a need to save it to VB or move to
another server.]

IanO

I found some answers:
Deployment is just Copying!
No compilation involved.

http://forums.microsoft.com/MSDN/Sho...31578&SiteID=1