Question on packages deployment

Hi, all experts here,

Thank you very much for your kind attention.

I am having a question on the deployment of the packages to integration services server. Why after I have deployed the whole solution, but my packages are not actually deployed to the integration services server?

Also, after we add the package manually to the integration services server, to users outside of local host, how could we add permissions for them to execute the packages?

Thanks a lot in advance for your help and I am looking forward to hearing from you shortly.

With best regards,

Yours sincerely,

Hi Helen999888,

I'm not sure how you are deploying the packages or what you mean when you say "add the package manually". Can you provide some detail about your current procedure?

I like to use the Deployment Utility for deployment. In Solution Explorer, right-click the project name and click Properties. On the Deployment Utility page, set the CreateDeploymentUtility property to True. The next time you build the project, a Deployment subdirectory will be created under the bin directory in the project path. Inside this directory will be at least two files: one for each package in the solution and another named the same as the project with the extension: SSISDeploymentManifest. If you double-click the SSISDeploymentManifest file, the SSIS Deployment Wizard starts and will walk you through deploying the package(s) in your project.

There are many ways to execute SSIS packages:

Manually - in either Business Intelligence Development Studio or using DTExecUI. Command Line - using DtExec. SQL Agent Job - using the SQL Server Integration Services step type.|||

Hi, Andy,

Thanks a lot for your advices and help.

With best regards,

Yours sincerely,

Question on Deployment

hello everyone,

I have a question on deployment of SSIS.

My team plans to develop a lot of SSIS packages.

I want my deployment environment to be as centralized as possible, but the processing environment to be distributed.

Here is what I had in mind. I have one server running SQL Server DB and SQL Server Agent. I have all the SSIS packages deployed on this server and schedule them as jobs in SQL Server Agent.

Now I have two other machines just running SSIS service (no other component). When the agent executes the packages, he should use either of the two machines. (Load balancing would be good, or I can manually assign the packages to the machines too).

is this possible? recommended?

Another approach would be that each SSIS Server, also has SQL Server and Agent installed. And respective packages are installed and scheduled on their respective servers. But here I have to maintain the packages and schedules on 2 machines.

regards,
Abhishek.

MSDN Student wrote:

hello everyone,

I have a question on deployment of SSIS.

My team plans to develop a lot of SSIS packages.

I want my deployment environment to be as centralized as possible, but the processing environment to be distributed.

Here is what I had in mind. I have one server running SQL Server DB and SQL Server Agent. I have all the SSIS packages deployed on this server and schedule them as jobs in SQL Server Agent.

Now I have two other machines just running SSIS service (no other component). When the agent executes the packages, he should use either of the two machines. (Load balancing would be good, or I can manually assign the packages to the machines too).

is this possible? recommended?

Another approach would be that each SSIS Server, also has SQL Server and Agent installed. And respective packages are installed and scheduled on their respective servers. But here I have to maintain the packages and schedules on 2 machines.

regards,
Abhishek.

You cannot execute packages remotely so the first scenario you outlined is not possible.

-Jamie

|||

OK. How about this one

On one machine I have SQL Server installed where I deploy all my SSIS packages. On the other two machines I have SQL Agent and SSIS Service installed.

The two machines will read the common SQL Server repository to read SSIS packages and execute them on the respective machines.

I will still be able to keep all the packages in one central SQL Server location, but I will have to configure the SQL Jobs on both the SSIS servers.

Will this work?

regards,
Abhishek.

|||

Yep, that will work fine.

I have to ask why do you want to do this? Unless you are re-using exactly the same (version) package across several machines, it seems like the central dependency doesn't offer that much.

Question on cube processing and deployment

Hi, all experts here,

Thank you very much for your kind attention.

I encountered a very strange problem processing and deploying the cube to the analysis services server. The fact table where the measure group coming from only got several hundred rows, while at the same time I have other 6 dimensions with many attributes. My system drive currently still has nearly 1 GB space left, but when I deployed the cube, it took ages to run and ended up with process failure because of running out of space on my system drive.

This problem never happened before and it is really frustrated and I dont know what is going on.

Would please any experts here give me any advices. (I have tried ages, but still nothing really changes).

I am looking forward to hearing from you and thanks a lot in advance.

With best regards,

Yours sincerely,

Any expers know what is the cause of that problem?

Thanks.

With best regards,

Yours sincerely,

Question on cube and dimension deployment in production

Hi, all experts here,

Would any of you here shed me any light on how could we deploy cubes and dimensions to other server rather than the one where they are created? And also what permissions at least are needed to be set up for them to be accessed in production enviornment?

Hope it is clear for your help.

Thanks a lot and I am looking forward to hearing from you shortly.

With best regards,

Yours sincerely,

Hi Helen,

Take a look at the functionality of the Deployment Wizard: http://msdn2.microsoft.com/en-us/library/ms176121.aspx

Regarding permissions, do you mean administrative access or the ability to query data? In either case BOL is again the best place to start: http://msdn2.microsoft.com/en-us/library/ms174517.aspx. Or do you mean the ability just to connect to the cube at all? In which case this new paper on connectivity problems might help - it discusses everything might might stop you from connecting:

http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/CISQL2005ASCS.mspx

Regards,

Chris

|||

Hi, Chris,

Thanks a lot for your very kind help. Definitely they've been very helpful to clear up my confusions and questions on that.

Yes, I am concerning about being able to access the cubes and dimensions after they are deployed to other production environment.

Thanks a lot again.

With best regards,

Yours sincerely,