|
|
|
|
||||||
| ms.sqlserver.setup Questions about SQL Server. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Can someone give me an example of the setup values to configure an ODBC
connection via the Internet to an SQL server? After opening and securing a port to the server through the firewall, I tried <IP Address>:<port> in the connection parameters and <server name> in the server alias, but I can't seem to get the right string. Thanks, Ross |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Take a look at http://www.connectionstrings.com
-- Denny MCSA (2003) / MCDBA (SQL 2000) MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration) MCITP (dbadmin, dbdev) "Ross Culver" wrote: > Can someone give me an example of the setup values to configure an ODBC > connection via the Internet to an SQL server? > > After opening and securing a port to the server through the firewall, I > tried <IP Address>:<port> in the connection parameters and <server name> in > the server alias, but I can't seem to get the right string. > > Thanks, > > Ross > > > |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Ok, I finally got what I wanted ... almost.
By creating a point-to-point VPN connection between my two servers, I've been able to expose both to one another. I can connect via SQL management to both servers, awesome! However, since they're on separate subnets, I can only connect via the server's IP address and not by name. So the linked server ends up with a name like 10.0.0.247 which cannot be used in Transact SQL like "select * from openquery(10.0.0.247, 'select .....)". So what should I do now? Perhaps setup WINS? Thanks, Ross "Ross Culver" <rculver@warrenalloy.com> wrote in message news:%23TFEp6muHHA.5028@TK2MSFTNGP02.phx.gbl... > Can someone give me an example of the setup values to configure an ODBC > connection via the Internet to an SQL server? > > After opening and securing a port to the server through the firewall, I > tried <IP Address>:<port> in the connection parameters and <server name> > in the server alias, but I can't seem to get the right string. > > Thanks, > > Ross > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
You've got a few options. I'll list them in order of preference.
1. Add each server and IP address to the remote site's DNS. 2. Add each server and IP address to the remote machines host file. 3. Stick with the IP address only for connectivity. Setup the linked server with the host name of the machine, for but the actual data source put the IP. 4. Stick with the IP address for the linked server name. Put it in [] when using it in an openquery. SELECT * FROM OPENQUEY([10.0.0.247], 'select ...') -- Denny MCSA (2003) / MCDBA (SQL 2000) MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration) MCITP (dbadmin, dbdev) "Ross Culver" wrote: > Ok, I finally got what I wanted ... almost. > > By creating a point-to-point VPN connection between my two servers, I've > been able to expose both to one another. I can connect via SQL management > to both servers, awesome! However, since they're on separate subnets, I can > only connect via the server's IP address and not by name. So the linked > server ends up with a name like 10.0.0.247 which cannot be used in Transact > SQL like "select * from openquery(10.0.0.247, 'select .....)". > > So what should I do now? Perhaps setup WINS? > > Thanks, > > Ross > > > "Ross Culver" <rculver@warrenalloy.com> wrote in message > news:%23TFEp6muHHA.5028@TK2MSFTNGP02.phx.gbl... > > Can someone give me an example of the setup values to configure an ODBC > > connection via the Internet to an SQL server? > > > > After opening and securing a port to the server through the firewall, I > > tried <IP Address>:<port> in the connection parameters and <server name> > > in the server alias, but I can't seem to get the right string. > > > > Thanks, > > > > Ross > > > > > |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Thanks, Denny. I opted for the 4th and it works fine.
"mrdenny" <mrdenny@discussions.microsoft.com> wrote in message news:99817F2E-6931-41C6-85BF-6C271542A955@microsoft.com... > You've got a few options. I'll list them in order of preference. > > 1. Add each server and IP address to the remote site's DNS. > 2. Add each server and IP address to the remote machines host file. > 3. Stick with the IP address only for connectivity. Setup the linked > server > with the host name of the machine, for but the actual data source put the > IP. > 4. Stick with the IP address for the linked server name. Put it in [] > when > using it in an openquery. > > SELECT * > FROM OPENQUEY([10.0.0.247], 'select ...') > -- > Denny > MCSA (2003) / MCDBA (SQL 2000) > MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration > / > Microsoft Office SharePoint Server 2007: Configuration) > MCITP (dbadmin, dbdev) > > > "Ross Culver" wrote: > >> Ok, I finally got what I wanted ... almost. >> >> By creating a point-to-point VPN connection between my two servers, I've >> been able to expose both to one another. I can connect via SQL >> management >> to both servers, awesome! However, since they're on separate subnets, I >> can >> only connect via the server's IP address and not by name. So the linked >> server ends up with a name like 10.0.0.247 which cannot be used in >> Transact >> SQL like "select * from openquery(10.0.0.247, 'select .....)". >> >> So what should I do now? Perhaps setup WINS? >> >> Thanks, >> >> Ross >> >> >> "Ross Culver" <rculver@warrenalloy.com> wrote in message >> news:%23TFEp6muHHA.5028@TK2MSFTNGP02.phx.gbl... >> > Can someone give me an example of the setup values to configure an ODBC >> > connection via the Internet to an SQL server? >> > >> > After opening and securing a port to the server through the firewall, I >> > tried <IP Address>:<port> in the connection parameters and <server >> > name> >> > in the server alias, but I can't seem to get the right string. >> > >> > Thanks, >> > >> > Ross >> > >> >> >> |
|
![]() |
| Outils de la discussion | |
|
|