Outbound SQL Connections

Hello Everyone,

I have two SQL 2005 clusters, one at a Corporate HQ and another at a hosting site. On each cluster there are several SQL instances each tied to a seperate Cluster Group meaning that there is a virtual cluster IP address assigned to the cluster group which should translate to the instance.

The issue that I am seeing is that in the connection manager, the IP addresses aren't listed correctly and there is sometimes just junk in there -- up to 10 IP addresses listed. There are many replication and service broker jobs running between the clusters all tied to specific IP addresses and ports which map to NAT and ACLs on the firewalls.

Here is the crux of it: While I can change the listening port and IP in the connection manager, how to I ensure that the outbound replication traffic is coming from the right source? If I add the correct IP address into the connection manager for the instance and disable the others, will it send from that IP address?

I have inherited this system and we are making the first strides into intagling this mess, but I am trying to surgically fix this rather than opening up all kinds of security holes in the interim.

Suggestions?

Ryan

Moving to Availability folder.

Outbound SQL Connections

Hello Everyone,

I have two SQL 2005 clusters, one at a Corporate HQ and another at a hosting site. On each cluster there are several SQL instances each tied to a seperate Cluster Group meaning that there is a virtual cluster IP address assigned to the cluster group which should translate to the instance.

The issue that I am seeing is that in the connection manager, the IP addresses aren't listed correctly and there is sometimes just junk in there -- up to 10 IP addresses listed. There are many replication and service broker jobs running between the clusters all tied to specific IP addresses and ports which map to NAT and ACLs on the firewalls.

Here is the crux of it: While I can change the listening port and IP in the connection manager, how to I ensure that the outbound replication traffic is coming from the right source? If I add the correct IP address into the connection manager for the instance and disable the others, will it send from that IP address?

I have inherited this system and we are making the first strides into intagling this mess, but I am trying to surgically fix this rather than opening up all kinds of security holes in the interim.

Suggestions?

Ryan

Moving to Availability folder.

outbound SOAP requests from native SQL

Hi everyone
I'm trying to find a way to query data from a web service and bring it
back into SQL to join with other relational data already in the
database. From what I've read you're required to compile an assembly
(which serves as a middle tier between the database and web service)
and register that assembly in sql server. Your T-SQL query then calls
the assembly which calls the webservice to get the data.
1. Is this correct?
2. If there was so much effort to make SQL procedures exposed via
webservice, why can't SQL do the opposite? I think that consuming a
webservice is much easier than providing it... is this a feature that
no one asked for in SQL server?
3. I can't seem to find any documentation on what is required in these
assemblies... does anyone have any good links on how to write one of
these?
Thanks!
Brandon
Hello
You are saying SQLCLR. Type the word in MSDN search box and you may see some
walkthrough as the first result.
Interesting question is #2. One thing is Microsoft makes the CLR not for
webservice but for including whole dotnet framework functionalities. Now
they become so lazy as not to do anything more;;
<brandon.richter@.gmail.com> wrote in message
news:1162912948.288024.140830@.e3g2000cwe.googlegro ups.com...
> Hi everyone
> I'm trying to find a way to query data from a web service and bring it
> back into SQL to join with other relational data already in the
> database. From what I've read you're required to compile an assembly
> (which serves as a middle tier between the database and web service)
> and register that assembly in sql server. Your T-SQL query then calls
> the assembly which calls the webservice to get the data.
> 1. Is this correct?
> 2. If there was so much effort to make SQL procedures exposed via
> webservice, why can't SQL do the opposite? I think that consuming a
> webservice is much easier than providing it... is this a feature that
> no one asked for in SQL server?
> 3. I can't seem to find any documentation on what is required in these
> assemblies... does anyone have any good links on how to write one of
> these?
> Thanks!
> Brandon
>

outbound SOAP requests from native SQL

Hi everyone
I'm trying to find a way to query data from a web service and bring it
back into SQL to join with other relational data already in the
database. From what I've read you're required to compile an assembly
(which serves as a middle tier between the database and web service)
and register that assembly in sql server. Your T-SQL query then calls
the assembly which calls the webservice to get the data.
1. Is this correct?
2. If there was so much effort to make SQL procedures exposed via
webservice, why can't SQL do the opposite? I think that consuming a
webservice is much easier than providing it... is this a feature that
no one asked for in SQL server?
3. I can't seem to find any documentation on what is required in these
assemblies... does anyone have any good links on how to write one of
these?
Thanks!
BrandonHello
You are saying SQLCLR. Type the word in MSDN search box and you may see some
walkthrough as the first result.
Interesting question is #2. One thing is Microsoft makes the CLR not for
webservice but for including whole dotnet framework functionalities. Now
they become so lazy as not to do anything more;;
<brandon.richter@.gmail.com> wrote in message
news:1162912948.288024.140830@.e3g2000cwe.googlegroups.com...
> Hi everyone
> I'm trying to find a way to query data from a web service and bring it
> back into SQL to join with other relational data already in the
> database. From what I've read you're required to compile an assembly
> (which serves as a middle tier between the database and web service)
> and register that assembly in sql server. Your T-SQL query then calls
> the assembly which calls the webservice to get the data.
> 1. Is this correct?
> 2. If there was so much effort to make SQL procedures exposed via
> webservice, why can't SQL do the opposite? I think that consuming a
> webservice is much easier than providing it... is this a feature that
> no one asked for in SQL server?
> 3. I can't seem to find any documentation on what is required in these
> assemblies... does anyone have any good links on how to write one of
> these?
> Thanks!
> Brandon
>sql