I try to store a SSIS-configuration value in the registry.
But it's failed. I get a warning, that the registry-key is not found.
What is the syntax ? I have searched in BO,MSDN and Google/Internet ==> nothing.
There is no example.
The syntax of how to specify the name of the registry key is straightforward. See BOL: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uirfsql9/html/212e52e7-27a7-48bb-8bad-34aa290d2003.htm
If you're asking how to define the syntax of a configuration (i.e. The thing that should be IN the registry key) then that's a bit more difficult. A quick scan of BOl didn't bring anything up. The way I always do it is to create an XML COnfiguration file from within SSIS Designer and then copy and paste the resultant configuration into the registry key.
Hope that halps.
-Jamie
|||Hey Jamie,
there is no example:
Configuration Type Option = Registry Entry
Specify configuration settings directly
Use to specify settings directly.
Value Description
Registry entry
Type the registry key that contains the configuration information.
I think it is very easy, but I don't know how to type the registry key!
With regedit I have defined a new entry:
HKEY_LOCAL_MACHINE\SOFTWARE\SSIS\Var
Var is a string and contains for example the servername.
What is the syntax in the SSIS-Configuration-Wizard?
You create an XML-Configuration file then you copy and paste the result into the registry key?
The registry key can store only one proberty. The XML-Configuration can store many proberties. You have an example?
Thanks
Loom
|||It sounds to me as though you have done everything that you need to do. What error are you getting when you try and usee it?
-Jamie
|||
In the german version I get this warning:
Warnung: 0x80012015 bei Package: Der Konfigurationsregistrierungsschlüssel 'HKEY_LOCAL_MACHINE\SOFTWARE\SSIS\Var' wurde nicht gefunden. Für einen Konfigurationseintrag ist ein nicht verfügbarer Registrierungsschlüssel angegeben. überprüfen Sie die Registrierung, und stellen Sie sicher, dass der Schlüssel vorhanden ist.
Translation:
The Configuration-Registry-Key 'HKEY_LOCAL_MACHINE\SOFTWARE\SSIS\Var' was not found.
Loom
|||The key must be defined in HKCU.
The Value must be stored in the Value key.
HKCU\Configuration\FirstConfig\Value
HKCU\Configuration\SecondConfig\Value
The ConfigString is Configuration\FirstConfig , this is the string you put into the Configuration String field in the Configuration Wizard.
The Registry Configuration assumes the HKCU and Value sections. Everything in between can be whatever you want.
HTH,
K
|||
Kirk,
Is this information in BOL anywhere? If it isn't, it should be.
-Jamie
|||Nah, don't think so. I couldn't find it anywhere...|||
Bingo!
I have tried everything, but not the value key....
To store the configuration in the registry has an advantage compared with an environment-variable. A change in the registry automaticly change your configuration.
A change of an environment-variable has no effect in the BI-Studio. The only way to refresh the variable is: Close the BI-Studio and then reopen it.
And this is a problem for a developer. Environment-variables are not the first choice for switching between Dev / Test / Pro - Servers.
Or I have missed something?
Loom
|||You're right that you need to shut down BIDS for the EV Config to take effect, but, why does that matter? You can simply change the value of the configured property as though the configuration had been applied.
Again, it's a preference thing. That's why there are several options.
Environment Variables are the only option for Indirect Configurations.
K
|||There is another option for Indirect Configuration: The SQL-Server option.
The SQL-Server use a normal connection-manager and you can configure the proberties of this connection-manager.
In the FirstConfig you can change the ServerName and the InitialCatalog of the connection-manager.
In the SecondConfig you use the SQL-Server-Option with the changed ServerName/InitialCatalog.
In my opinion it is an indirect configuration too.
Loom
|||Yep, got that right. Very flexible, yes.
K
|||Loom wrote:
Bingo!
I have tried everything, but not the value key....
To store the configuration in the registry has an advantage compared with an environment-variable. A change in the registry automaticly change your configuration.
A change of an environment-variable has no effect in the BI-Studio. The only way to refresh the variable is: Close the BI-Studio and then reopen it.
And this is a problem for a developer. Environment-variables are not the first choice for switching between Dev / Test / Pro - Servers.
Or I have missed something?
Loom
Its a matter of opinion isn't it? there isn't one right answer. Personally I think the issue about having to close BIDS isn't really a problem as long as you know about the issue.
I use indirect configurations exclusively. That's just my choice.
-Jamie
|||
I try to use this option to change the "conenction string" property of a Flat file connection, but nothing happens.
What is the correct format of registry Key string to fill the box?
I try :
HKEY_LOCAL_MACHINE\SOFTWARE\ProjectName\Connections\ConnectionString1
and
[HKEY_LOCAL_MACHINE\SOFTWARE\ProjectName\Connections\ConnectionString1]
and
"HKEY_LOCAL_MACHINE\SOFTWARE\ProjectName\Connections\ConnectionString1"
The value Key "ConnectionString1" is a String Value that contains the address of file like: C:\input files\Test.csv
Don't Work!!!! What′s wrong?
Thanks
|||In the registry you have this entry:
HKEY_LOCAL_MACHINE\SOFTWARE\ProjectName\Connections\ConnectionString1\value
In Value you store your connection string
In the SSIS-Configuration the reference is:
SOFTWARE\ProjectName\Connections\ConnectionString1
Loom
No comments:
Post a Comment