April 1, 2018 at 7:49 am
Hi all, I have the following set up (imposed by our IT team, not by choice).
Locally (where i write the packages)
BIDS
Remote(deployment location):
SQL Server 2008 R2
Integration Services
I am writing the packages in BIDS then attempting to deploy to a remote SQL Server Instance on another Server.
I do not have integration services installed locally where I am writing the packages and I cannot get direct access to the server where SQL Server and SSIS are installed.
Obviously when I run the manifest file of the project, it determines that I don't have SSIS installed locally and so will not allow the deployment.
I cannot sign into SQL server as Integration Services on my local machine, only Database Engine.
Does anyone have any suggestions as to whether it is possible and if so, how, I can deploy to the remote server and also log into the server with Integration services from the remote machine?
Sorry if anything isn't clear, ask me to clarify if needs be.
N.B. the set up is fixed and i am unable to get anything changed/installed etc.
Dave
April 1, 2018 at 11:18 pm
Can you remote login into the machine you want to deploy to , and run the manifest there? If you dont have the permissions to deploy the package to the package store then that pretty much settles it. One of the thoughts behind a manifest is to be able to deliver the solution for someone else to deploy in their machine where they have permissions and avoid configuration mishaps. Any one you can pass it off to?
----------------------------------------------------
April 2, 2018 at 1:17 am
Hi, thanks for clarifying. I am getting RDP access arranged in the next couple of weeks. Sadly the DBA who controls all of this has never used SSIS and prefers a mixture of power shell and stored procedures for his ETL needs so I am having to teach him as we go along.
I guess I will have to wait a while. Thanks and Happy Easter.
Dave
April 2, 2018 at 10:08 am
Happy Easter. Don't overlook that you also get the access to push this into the package store and create a job, have the job run with an appropriate proxy account and/or whatever else needs to happen. You may not want to wait a couple weeks each time 🙂 Thanks for the update.
----------------------------------------------------
April 2, 2018 at 12:05 pm
Hi, good point re the package store.
He is setting me up a service account ( as he controls the AD on that domain) and then setting me RDP access to the server so I can load and deploy to my hearts content. I have asked for the access to cover agent jobs as well. 2 weeks is as he is on holiday - won’t have to wait again hopefully.
Dave
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply