Deploying Packages

Question

Deploying Packages

Scott Thornton-407727

SSCrazy

Points: 2271
More actions
August 28, 2007 at 12:27 am

#176457

Hi,
I am progressing through the MS Tutorial on Deploying packages, and a few questions:
Do I REALLY need to copy the package deployment files to the server directly to install the package?
Does this mean my user account will require file system access on the server?
Where should the files be placed?
Does it matter if they are deleted after the package is deployed?
I am using a 64bit cluster...... does this complicate the process?

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Baskar B.V SSCrazy Points: 2823 More actions · Answer 1

Hi,

If you have network access to the server then you can deploy the files from your local machine to the network server. Run the package deployment utility specify the deployment path and you are done. You don't need to copy the files over there.

[font="Arial"]BASKAR BV
http://geekswithblogs.net/baskibv/Default.aspx
In life, as in football, you won’t go far unless you know where the goalposts are.[/font]

Scott Thornton-407727 SSCrazy Points: 2271 More actions · Answer 2

Hi,

So what you are saying is, I DO need access to the file system on the server?

When running the 'Package Installation Wizard' on the 'Select Installation Folder' page, I can specify a share on the sql server?

Does it matter where the share is on the server?

The default suggests something like 'C:\Program Files\Microsoft SQL Server\90\DTS\Packages\packagename': Is this where it has to go on the server?

I will need to get my systems guys to give me access, and I want to ask for the correct thing the first time around.

Thanks,

Baskar B.V SSCrazy Points: 2823 More actions · Answer 3

Yes you are correct. You need access to folder on the server where you deploy your files.

You can do the file based deployment in two ways. You can directly copy all the SSIS packages from your local machine bin directory into the server directory and run it. The same you can do using deployment utility wizard that gets created inside bin folder when you build the project.

HTH

[font="Arial"]BASKAR BV
http://geekswithblogs.net/baskibv/Default.aspx
In life, as in football, you won’t go far unless you know where the goalposts are.[/font]

Baskar B.V SSCrazy Points: 2823 More actions · Answer 4

in the first approach, you donot need to run deployment wizard if you are going for file based deployment. Just copy them to the server folder and run the package using DTEXEC or using sql agent.

[font="Arial"]BASKAR BV
http://geekswithblogs.net/baskibv/Default.aspx
In life, as in football, you won’t go far unless you know where the goalposts are.[/font]

Scott Thornton-407727 SSCrazy Points: 2271 More actions · Answer 5

Scott Thornton-407727

SSCrazy

Points: 2271

August 29, 2007 at 4:31 pm

#730285

thanks for all replies.......

shank-130731 SSC Eights! Points: 890 More actions · Answer 6

I'm having problems deploying a package also. I'm trying to deploy to a shared SQL Server 2005 where I'm supposed to have access. However, I'm getting the following error. I think the host has permissions setup wrong. Has anyone had this same issue? Is there something obvious that I can suggest to the SQL host to setup permissions in a certain way?

- - - - - - - - - - - - - - - - - - - -

Additional information

- The SavetoSQLServer method has encountered OLE DB error code 0x80040E09

(The EXECUTE permission was denied on the object sp_dts_putpackage...

- - - - - - - - - - - - - - - - - - - -

thanks!

Scott Thornton-407727 SSCrazy Points: 2271 More actions · Answer 7

Hi,

Check that your user account has permissions withing the MSDB account on the SSIS ( DTS ) roles.