Showing posts with label setting. Show all posts
Showing posts with label setting. Show all posts

Friday, March 23, 2012

Parent Child Integration using Configuration File

Hi All,

I though i'd been going about setting up my SSIS package to run via a SQL job in the correct way. It would appear however that is not the case.

I have 4 SSIS packages, one of which is the parent package which calls the other three in sequence. I want to run this from a SQL job so that it calls the parent package and it deals with the others. There are connection managers in the package which use a SQL account to access the relevant databases. In addition i have encrypted the package.

I have set up a configuration file which holds the password package and the BillingSystem connection manager password. This file is re used by each package.

After deployment i have set up the SQL agent job to run the parent package. The job returns an error. Looking at the SSIS logging it appears that it completes the SQL task in the parent package and then fails when trying to launch each of the sub packages with an error stating that the SQL account used in the connection manager login failed. It looks as though the sub packages are not getting the password value from the configuration file and this is causing the failure. I though that each package would automatically pick up the config file as it has been setup to do. I have specified the configuration file in the SQL job but this appears to make no difference. Running the integrations seperately i have to add the configuration file in manually to the Run Package dialog box before they will work. This is not saved for the next run.

Can anyone help me get around this problem as i think i have the wrong idea as to how it is supposed to work.

Cheers,

Grant

Are your packages stored in the filesystem or in MSDB?|||

MSDB; Does that make a difference in this case?

Grant

|||Is the SQL server connection for each of the Execute Package task part of a configuration file?|||

Initially the config file contained the connection manager password. It now has the connection string but doesn't seem to be used for the packages called from the initial package. I had to manually alter the i config xml to include the password in the connection string.

Grant

Tuesday, March 20, 2012

ParameterValueClass for setting Parameters Property of ReportViewer

I am trying to set the ReportViewer (the one that runs as a .net control)
Parameters property, which is looking for an array of ParameterValue
objects. Where is the ParameterValue object defined? I cannot find it in
the ReportViewer, or the Web Services. Any ideas how to pass a set of
parameneters to the Parameters property of the ReportViewer?
Thanx, BobAre you referring to the ReportViewer sample control that ships with
Reporting Services?
The Parameters property of the control refers specifically to the parameters
area of the toolbar which can display input fields for report parameters.
This is not a property that can be used to pass report parameters. The
ReportViewer sample utilizes the report server built in parameters support.
--
Bryan Keller
Developer Documentation
SQL Server Reporting Services
A friendly reminder that this posting is provided "AS IS" with no
warranties, and confers no rights.
"Bob Feller" <bob@.nospam.morningdew.net> wrote in message
news:eoz$ml2aEHA.1644@.tk2msftngp13.phx.gbl...
> I am trying to set the ReportViewer (the one that runs as a .net control)
> Parameters property, which is looking for an array of ParameterValue
> objects. Where is the ParameterValue object defined? I cannot find it in
> the ReportViewer, or the Web Services. Any ideas how to pass a set of
> parameneters to the Parameters property of the ReportViewer?
> Thanx, Bob
>

Friday, March 9, 2012

Parameters in SSRS with OLAP

Hi - I have a report that uses an OLAP cube. I cannot figure out how to pass
parameters into the report using URL. I've tried setting the parameter to
the value I desire, but that doesn't work. Here's an example:
http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
When I look at how OLAP passes parameters into reports, it's not the same as
when I use straight SQL tables. So I tried:
http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
but then I get an error message saying that the text is too long. Any help
would be appreciated.What is the MDX of the statement you are trying to execute based on the
parameter?
This has to be set up as a concatenated string in the DS for the report.
Chris E
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:2582B5B0-C2AE-4327-8A66-FECA58B19754@.microsoft.com...
> Hi - I have a report that uses an OLAP cube. I cannot figure out how to
> pass
> parameters into the report using URL. I've tried setting the parameter to
> the value I desire, but that doesn't work. Here's an example:
> http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
> When I look at how OLAP passes parameters into reports, it's not the same
> as
> when I use straight SQL tables. So I tried:
> http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
> but then I get an error message saying that the text is too long. Any help
> would be appreciated.
>|||Thanks for your response, Chris. The MDX statement is:
SELECT NON EMPTY { [Measures].[Responses], [Measures].[Quantity],
[Measures].[Total Cost], [Measures].[Revenue] } ON COLUMNS, NON EMPTY { ([Dim
Expire Group].[Dim Expire Group].[Dim Expire Group].ALLMEMBERS * [Dim
Notice].[Dim Notice].[Dim Notice].ALLMEMBERS * [Dim Notice].[Notice
Order].[Notice Order].ALLMEMBERS * [Dim YOF].[YOF Name].[YOF Name].ALLMEMBERS
* [Dim YOF].[YOF Order].[YOF Order].ALLMEMBERS * [Dim HPC].[HPC Id1].[HPC
Id1].ALLMEMBERS * [Dim HPC].[HPC Name1].[HPC Name1].ALLMEMBERS * [Dim
HPC].[HPC Order1].[HPC Order1].ALLMEMBERS * [Dim YOF].[Dim YOF].[Dim
YOF].ALLMEMBERS * [Dim Package].[Package Type Id].[Package Type
Id].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON
ROWS FROM ( SELECT ( STRTOSET(@.DimHPCHPCName, CONSTRAINED) ) ON COLUMNS FROM
( SELECT ( STRTOSET(@.DimExpireGroupDimExpireGroup, CONSTRAINED) ) ON COLUMNS
FROM ( SELECT ( STRTOSET(@.DimPackagePackageTypeId, CONSTRAINED) ) ON COLUMNS
FROM ( SELECT ( STRTOSET(@.DimProgramDimProgram, CONSTRAINED) ) ON COLUMNS
FROM [FactSourceCode])))) WHERE ( IIF( STRTOSET(@.DimProgramDimProgram,
CONSTRAINED).Count = 1, STRTOSET(@.DimProgramDimProgram, CONSTRAINED), [Dim
Program].[Dim Program].currentmember ) ) CELL PROPERTIES VALUE, BACK_COLOR,
FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
I pass several parameters into the statement. I thought I'd figured it out
by using the codes that represent the [, ] and &. But I'm still getting the
same issue when it tries to pass the parameter in the URL.
"Chris" wrote:
> What is the MDX of the statement you are trying to execute based on the
> parameter?
> This has to be set up as a concatenated string in the DS for the report.
> Chris E
> "Jim" <Jim@.discussions.microsoft.com> wrote in message
> news:2582B5B0-C2AE-4327-8A66-FECA58B19754@.microsoft.com...
> > Hi - I have a report that uses an OLAP cube. I cannot figure out how to
> > pass
> > parameters into the report using URL. I've tried setting the parameter to
> > the value I desire, but that doesn't work. Here's an example:
> >
> > http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=301
> >
> > When I look at how OLAP passes parameters into reports, it's not the same
> > as
> > when I use straight SQL tables. So I tried:
> >
> > http://mysite/reportserver/report.rdl&rc:toolbar=true&rc:LinkTarget=_top&DimParameter=[DimParameter].[MEMBER].[301]
> >
> > but then I get an error message saying that the text is too long. Any help
> > would be appreciated.
> >
>
>|||I had a similar problem. My solve was:
the konfiguration of report paramters must set
available evaluates = not asked
and
standard value = zero
then it should function with the parameters [DimParameter].[MEMBER].[301]
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com|||I had a similar problem. My solve was:
the konfiguration of report paramters must set
available value = not asked
and
standard value = zero
then it should function with the parameters [DimParameter].[MEMBER].[301]
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Wednesday, March 7, 2012

parameters default value remains "Query based" in spite of setting

Hello,
In my report manager I am not able to set a default value for a report
parameter, because the default value is indicated to be "query based".
I do not seem to be able to change that whatever I do. Surely I tried
setting the report parameters to "non-queried" and "none".
The default values I set in report designer also do not show in the
deployed report. (Even though other changes do.)
Anybody some ideas? Thanks.In Solution Explorer, right-click on the Project and choose Properties. Change OverwriteDataSources
to True and redeploy.
Optionally, you can use Report Manager (http://yourserver/reports) to do this by navigating to the
report you want to modify, clicking the Properties tab and selecting Data Sources on the left. You
can them make your changes on the server.
Thanks.
Donovan R. Smith
Software Test Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul vO" <info@.vanoordt.nl> wrote in message
news:200e5c1b.0408230349.39c8c5d0@.posting.google.com...
> Hello,
> In my report manager I am not able to set a default value for a report
> parameter, because the default value is indicated to be "query based".
> I do not seem to be able to change that whatever I do. Surely I tried
> setting the report parameters to "non-queried" and "none".
> The default values I set in report designer also do not show in the
> deployed report. (Even though other changes do.)
> Anybody some ideas? Thanks.