Import SQL Package!!

[Former Member]

Hi to all Experts,

I installed BPC MS 10.0 with SQL Server 2012.

I want to do a demo test on Import SQL data into bpc. For this, I searched for how to use Import SQL DM Package.

I created a sql table, and then ran import sql dm package via excel client. I get the following error.

Error occurred while updating the dynamic properties of a package

[dbo].[tblFAC2Copy] is missing or invalid source table.

I know for sure that I am missing some basic configuration in this matter, but could not figure it out.

Note: in Import SQL package properties, ApShell is used. which I think is not correct because I do not have any application with this name.

Any help would be highly appreciated.

Thanks,

Regards,

Nouman.

[former_member186498 · Accepted solution]

Hi Nouman,

in the parametrs you have to insert the sql DB and table and the transformation file.

Note: in Import SQL package properties, ApShell is used. which I think is not correct because I do not have any application with this name.

APShell is the old name for EnvironmentShell the standard environment that is create during installation.

Can you please explain better where you see it? Can you please share an image?

Regards

     Roberto

[Former Member · Accepted solution]

hi Roberto,

First of all Thank you for the reply.

This evening was so tough but somehow I can run the package without error

What I did was.(May be someone can find it helpful)

• Searched the internet for SSDT, and how to use it.
• Searched the internet that I have to change the Apshell old connection to my current actual ApplicationSet and application credentials.
• imported SSIS import SQL DM package into SSDT, and edited the SQL Connection(OLEDB).
• saved the package with another name in application package directory (e.g. Import SQL cursom.dstx)
• open excel client and the imported new package.
• Modify Package> Advanced. uncommented OLEDBCONNECTION commands (Why were these commands commented, I do not know)
• Ran the package.

Questions regarding knowledge only

Why should we change the apshell Name, serverName connectionstring in SSIS. BPC should have the option in package parameter window to change the values.

I did not  tested my complete scenario yet, but hope that issue is resolved.

[former_member186498 · Accepted solution]

Hi Nouman,

good that you solve the issue, please close the thread assigning "correct" to your answer, this can help other users to find quickly a solution.

Why should we change the apshell Name, serverName connectionstring in SSIS. BPC should have the option in package parameter window to change the values.

you mean in the connection manager in SSIS? The standard import package contains default values you have to change these values for your case by double-clicking on the connection.

Regards

     Roberto

[Former Member · Accepted solution]

Hi Roberto,

Import SQL.dstx in Modify Script window has this option which We must change.(See Image)

     "you mean in the connection manager in SSIS? The standard import package contains default values you have to change these values for your case by double-clicking on the connection."

Where should I double click? I cannot edit the highlighted connectionstring.

I will mark this thread as Answered today.

Regards,

Nouman

[former_member186498 · Accepted solution]

Hi Nouman,

Where should I double click? I cannot edit the highlighted connectionstring.

I meant to open the dtsx from Microsoft visual studio and set the parameters from there,

here you can double clicking on connection managers and data flow task settings all values, connections, tthere is also a "test connection" to see if you have inserted the right parameters.

Regards

     Roberto

[Former Member · Accepted solution]

Hi Roberto,

Thank you for quick response.

Yes, I had to use same window to change parameters.

My question was that why must we change these parameters in Visual Studio window?(Your image)

and not in BPC dynamic properties window (My Image). i.e. There should be a simple parameter change in BPC Properties.

Well, that is just a thought.

Regards,

Nouman.

[former_member186498 · Accepted solution]

Hi Nouman,

from BPC sometimes it's a little buggy editors and you're not able always to change the parameters that's why I prefer to change package directly with MS Visual Studio, but in 7.5 version I'm able to modify the import sql, through more->organize package list->modify package->view package

->advanced

I think you forget the last step (to click to advanced) or you have some lack in authorization.

Regards

     Roberto

[former_member186498 · Accepted solution]

... and don't forget to click on the several "save" and "ok" request

[Former Member · Accepted solution]

Hi Roberto,

I had that advanced window in view, but could not understand the that how can I change the value of variables.

Anyhow,

"that's why I prefer to change package directly with MS Visual Studio"

I will also use this.

Regards,

Nouman