|
Home > Archive > BizTalk Server Orchestration > May 2004 > Database lookup functoid and database connect string
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Database lookup functoid and database connect string
|
|
| Peter Timkó 2004-05-30, 10:47 am |
| Dear All!
I would like to use the database lookup functoid in a map, but I don't want
to hard wire the database connection string to the functoid. Unfortunately
the name of the sql server different in the development and in the test
environment. How can I set this from a parameter?
Thanks
Peter
| |
| Yves Peneveyre 2004-05-30, 10:47 am |
| Hello Peter,
Here is a way you can use. I don't know if it is the best way....
You can use a .udl file and, in the database lookup functoid, set the second
parameter to :
File Name=D:\ThePath\ToTheUDL\File\connection
.udl
The content of this .udl file could be :
[oledb]
; Everything after this line is an OLE DB initstring
Provider=SQLOLEDB.1;Password=thePassword;Persist Security Info=True;User
ID=theUser;Initial Catalog=theDatabase;Data Source=SERVERNAME
Or, you can create an empty file with the .udl extension and double-click on
it to set the parameters.
The drawback for this is that the file must always be in the same location
(development and production).
Hope it helps
Best Regards
Yves Peneveyre
"Peter Timkó" <ptimko@online.com> wrote in message
news:uFkTqY%23QEHA.3596@tk2msftngp13.phx.gbl...
> Dear All!
>
> I would like to use the database lookup functoid in a map, but I don't
want
> to hard wire the database connection string to the functoid. Unfortunately
> the name of the sql server different in the development and in the test
> environment. How can I set this from a parameter?
>
> Thanks
>
> Peter
>
>
| |
| Martin Marinov 2004-05-30, 10:47 am |
| the UDL file is good approach but it is bound by the location of the file
and it must be always there
other solution is to create a rule that will set the connection string to
the database - if you have Business RUle Composer on the production Server
you can easy to maintain the connection string
Unfortunatelly, i couldn't manage to set a variable in the orchestration by
System.String type so i've created a .NET class that has been set and get
for this variable
Best Regards
Martin Marinov
"Yves Peneveyre" <ypeneveyre at lookware dot ch> wrote in message
news:eV9NpN$QEHA.3452@TK2MSFTNGP10.phx.gbl...
> Hello Peter,
>
> Here is a way you can use. I don't know if it is the best way....
> You can use a .udl file and, in the database lookup functoid, set the
second
> parameter to :
>
> File Name=D:\ThePath\ToTheUDL\File\connection
.udl
>
> The content of this .udl file could be :
>
> [oledb]
> ; Everything after this line is an OLE DB initstring
> Provider=SQLOLEDB.1;Password=thePassword;Persist Security Info=True;User
> ID=theUser;Initial Catalog=theDatabase;Data Source=SERVERNAME
>
> Or, you can create an empty file with the .udl extension and double-click
on
> it to set the parameters.
> The drawback for this is that the file must always be in the same location
> (development and production).
>
>
> Hope it helps
>
> Best Regards
>
> Yves Peneveyre
>
>
>
> "Peter Timkó" <ptimko@online.com> wrote in message
> news:uFkTqY%23QEHA.3596@tk2msftngp13.phx.gbl...
> want
Unfortunately[vbcol=seagreen]
>
>
|
|
|
|
|