|
Home > Archive > BizTalk Server Framework > September 2004 > How to change SQL Adapter connection string information
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 |
How to change SQL Adapter connection string information
|
|
|
| Hi,
I created SQL Adapter to insert data into DB in BizTalk project using "Add
Generated Items" wizard. So it created SQL Service.xsd schema according to
the stored proc specified. Now, I'm moving from Test database to production
database and I would like to change the connection string info as it is
different from Test DB. Where should I change this info to work with my
production DB? I didn't find way to modify in SQL Service Schema. Did any one
has faced the same problem?
--
Thanks
-Hari
| |
| Nabeel Prior 2004-09-15, 10:19 am |
| Your connection string is set on your send port or receive location,
and had nothing to do with the schema.
Kind Regards,
Nabeel Prior
2004/09/14 00:05:09
Hari <Hari@discussions.microsoft.com> wrote in message
<43B6232F-EB3B-47BD-B0A1-61866D6338FC@microsoft.com>
> Hi,
>
> I created SQL Adapter to insert data into DB in BizTalk project
using "Add
> Generated Items" wizard. So it created SQL Service.xsd schema
according to
> the stored proc specified. Now, I'm moving from Test database to
production
> database and I would like to change the connection string info as
it is
> different from Test DB. Where should I change this info to work
with my
> production DB? I didn't find way to modify in SQL Service Schema.
Did any one
> has faced the same problem?
>
> --
> Thanks
> -Hari
| |
|
| Thanks for the reply. But here is my confusion. While I was creating SQL
Adapeter to the SQL Server, BizTalk wizard asked me to enter connection
string info; like, server name, db name and user id and password info. Now, I
have to test the same with Production box. Does it work with out changing
Server name? May be, I'm missing some info here.
Thanks
-Hari
"Nabeel Prior" wrote:
> Your connection string is set on your send port or receive location,
> and had nothing to do with the schema.
> Kind Regards,
>
> Nabeel Prior
>
> 2004/09/14 00:05:09
> Hari <Hari@discussions.microsoft.com> wrote in message
> <43B6232F-EB3B-47BD-B0A1-61866D6338FC@microsoft.com>
>
> using "Add
> according to
> production
> it is
> with my
> Did any one
>
| |
| Nabeel Prior 2004-09-15, 10:19 am |
| When you create a schema with the BizTalk Wizard, you reference a
port that has already been setup with the relevant connection string
information. Although you do get a chance to change the connection
information in the wizard, the concept is that you should use the
connection information from the port you select on the first screen
of the wizard.
The wizard then uses this connection information and the SQL command
to create a schema matching the retrieved xml data returned by the
FOR XML statement. Whether in production or dev, when you want to
insert data into SQL, your BizTalk process sends the SQL adapter an
XML document containing the data to be inserted, which is passed
through the send pipeline to the send port. On the send port, the
SQL adapter is invoked with the connection information set on the
port, and the xml document is then sent to the configured SQL server.
The schema is only there for validating that the xml document is
correctly structured, etc., and has no bearing on how the connection
to the SQL server is established.
If you are wanting to test on the production server, you should
deploy your assembly (containing the schema, any maps, orchestrations,
etc) to the Production environment, then export the bindings file
(an XML file) from your dev environment. Open this bindings file up
and change the SQL connection string to the connection information
for your production environment. Then import this bindings file
using the deployment wizard on the production server.
Kind Regards,
Nabeel Prior
2004/09/14 23:37:07
Hari <Hari@discussions.microsoft.com> wrote in message
<46A5B980-A90A-4E01-B795-BDB5D58BD3DF@microsoft.com>
> Thanks for the reply. But here is my confusion. While I was
creating SQL
> Adapeter to the SQL Server, BizTalk wizard asked me to enter
connection
> string info; like, server name, db name and user id and password
info. Now, I
> have to test the same with Production box. Does it work with out
changing[vbcol=seagreen]
> Server name? May be, I'm missing some info here.
>
> Thanks
> -Hari
>
> "Nabeel Prior" wrote:
>
location,[vbcol=seagreen]
[vbcol=seagreen]
to[vbcol=seagreen]
as[vbcol=seagreen]
[vbcol=seagreen]
Schema.[vbcol=seagreen]
| |
|
| Thanks Nabeel for the clarification and I will test it on production box.
"Nabeel Prior" wrote:
> When you create a schema with the BizTalk Wizard, you reference a
> port that has already been setup with the relevant connection string
> information. Although you do get a chance to change the connection
> information in the wizard, the concept is that you should use the
> connection information from the port you select on the first screen
> of the wizard.
>
> The wizard then uses this connection information and the SQL command
> to create a schema matching the retrieved xml data returned by the
> FOR XML statement. Whether in production or dev, when you want to
> insert data into SQL, your BizTalk process sends the SQL adapter an
> XML document containing the data to be inserted, which is passed
> through the send pipeline to the send port. On the send port, the
> SQL adapter is invoked with the connection information set on the
> port, and the xml document is then sent to the configured SQL server.
> The schema is only there for validating that the xml document is
> correctly structured, etc., and has no bearing on how the connection
> to the SQL server is established.
>
> If you are wanting to test on the production server, you should
> deploy your assembly (containing the schema, any maps, orchestrations,
> etc) to the Production environment, then export the bindings file
> (an XML file) from your dev environment. Open this bindings file up
> and change the SQL connection string to the connection information
> for your production environment. Then import this bindings file
> using the deployment wizard on the production server.
>
> Kind Regards,
>
> Nabeel Prior
>
> 2004/09/14 23:37:07
> Hari <Hari@discussions.microsoft.com> wrote in message
> <46A5B980-A90A-4E01-B795-BDB5D58BD3DF@microsoft.com>
>
> creating SQL
> connection
> info. Now, I
> changing
> location,
>
> to
> as
>
> Schema.
>
|
|
|
|
|