Connect to specific TCP/IP endpoint?

Hello All,
I'd read in BOL that it is possible to connect "explicitly" to a
specific TCP/IP endpoint on the server. Does anyone know how to do
this? I can't find an example anywhere.
Thanks in advance.
-KJIn Enterprise manager, when you connect to a new server in a server group
enter the IP address of your server instead of the server's network name. If
your server is behind a firewall, you would have to implement NAT to the
actual server's Internal server's private IP address using port 1433 (the
default). Enter your EXTERNAL IP address as the server's address in the Ent
mgr in this case.
This way you can control a sql server from anywhere, but be aware that you
are opening a dangerous door. You should have a firewall that allows you to
filter the origin of the calls on port 1433 and only allow those requests
that originate from your safe Ip addresses to go through, that means that
your Ip address from which you make the calls should be a fixed IP. (costs
more)
HTH
Bob
"KJ" <n_o_s_p_a__m@.mail.com> wrote in message
news:1151340328.957952.169780@.c74g2000cwc.googlegroups.com...
> Hello All,
> I'd read in BOL that it is possible to connect "explicitly" to a
> specific TCP/IP endpoint on the server. Does anyone know how to do
> this? I can't find an example anywhere.
> Thanks in advance.
> -KJ
>|||I should have stated that I am actually looking for information on
connecting to TCP/IP endpoints (default or user-created) in SQL Server
2005.
Thanks Bob for your reply.
Bob wrote:
> In Enterprise manager, when you connect to a new server in a server group
> enter the IP address of your server instead of the server's network name.
If
> your server is behind a firewall, you would have to implement NAT to the
> actual server's Internal server's private IP address using port 1433 (the
> default). Enter your EXTERNAL IP address as the server's address in the En
t
> mgr in this case.
> This way you can control a sql server from anywhere, but be aware that you
> are opening a dangerous door. You should have a firewall that allows you t
o
> filter the origin of the calls on port 1433 and only allow those requests
> that originate from your safe Ip addresses to go through, that means that
> your Ip address from which you make the calls should be a fixed IP. (costs
> more)
> HTH
> Bob
>
> "KJ" <n_o_s_p_a__m@.mail.com> wrote in message
> news:1151340328.957952.169780@.c74g2000cwc.googlegroups.com...sqlsql

Confused Sending Order Confirmation

So, I've gone through the BOL walkthrough and all looks great however, I am confused about how to extend my application to send an order confirmation that contains an order header and order detail. I also have Shyam Pather's book but haven't seen this discussed yet. Does it make sense to do two inserts in my subscription? Something like "insert into orderedAlertHeader" and "insert into orderAlertDetail"? Can I create more than one table for the same subscription?

I think I've been looking at this for too long.

TIA

Ian

For those who are curious I think I've figured out a way to accomplish what I needed. I ended up creating an XML column on my alert table that I can load my detail into. My formatter then can do whatever I need it to.

I'll give an example if someone is interested.

Conflict between BOL and README - Which one is correct?!

BOL:
Microsoft recommends that you use the built-in account (NT AUTHORITY/SYSTEM)
when installing Reporting Services on a Windows 2000 server. If you use a
domain user account (even one that has local administrator privileges), it
will limit your choices on how to configure a data source connection for a
report as well as introduce new configuration steps that are not otherwise
required.
README-EN:
1.10 Domain user account requirement for subscriptions and ReportServer
Windows service running under Windows 2000 or Windows XP
If the ReportServer Windows service is running under Windows 2000 or Windows
XP, you must configure the service to run under a domain account. If you use
an account that does not have sufficient domain permissions, subscription
delivery will fail when the report server attempts to deliver reports to
domain user accounts. The following error occurs when report delivery fails
due to authorization and domain access issues: Failure sending mail: The
Report Server has encountered a configuration error.
I tried configuring the server using the SYSTEM account, however when
subscription SQL agent jobs are run I get the error listed in README 1.10.
When I reinstall the server and select a Domain Account for the ReportServer
service, I have to use a SQL account to connect. When I try this
configuration, the agent job runs and the Event table is populated, but
nothing else happens. The status shown in the Subscription is that the job
has not run. I'm at a loss. How are the accounts supposed to be configured?
Server is 2000 Advanced server with SQL 2000 Ent Ed.Hi,
I am having exactly the same problem as you report here. Did you get a
resolution to teh problem? If so please let me know!
Thanks
Laurence Neville
"Lifelongstudent" <dveit@.comcast.net> wrote in message
news:uRC9KxVZEHA.3228@.TK2MSFTNGP12.phx.gbl...
> BOL:
> Microsoft recommends that you use the built-in account (NT
AUTHORITY/SYSTEM)
> when installing Reporting Services on a Windows 2000 server. If you use a
> domain user account (even one that has local administrator privileges), it
> will limit your choices on how to configure a data source connection for a
> report as well as introduce new configuration steps that are not otherwise
> required.
> README-EN:
> 1.10 Domain user account requirement for subscriptions and ReportServer
> Windows service running under Windows 2000 or Windows XP
> If the ReportServer Windows service is running under Windows 2000 or
Windows
> XP, you must configure the service to run under a domain account. If you
use
> an account that does not have sufficient domain permissions, subscription
> delivery will fail when the report server attempts to deliver reports to
> domain user accounts. The following error occurs when report delivery
fails
> due to authorization and domain access issues: Failure sending mail: The
> Report Server has encountered a configuration error.
> I tried configuring the server using the SYSTEM account, however when
> subscription SQL agent jobs are run I get the error listed in README 1.10.
> When I reinstall the server and select a Domain Account for the
ReportServer
> service, I have to use a SQL account to connect. When I try this
> configuration, the agent job runs and the Event table is populated, but
> nothing else happens. The status shown in the Subscription is that the job
> has not run. I'm at a loss. How are the accounts supposed to be
configured?
> Server is 2000 Advanced server with SQL 2000 Ent Ed.
>