hi,
Could any one tell me what is the diff between remote server and linked
server?
I know linked server is for current sql server to access tables......
what about remote server>
thanks,"remote server" is another instance of sqlserver that the local sqlserver
connects to and queries data on behalf of the user. "linked server" is very
much the same thing, except it allows you to connect to any oledb data
source.
-oj
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OyW3DV4TGHA.5500@.TK2MSFTNGP12.phx.gbl...
> hi,
> Could any one tell me what is the diff between remote server and linked
> server?
> I know linked server is for current sql server to access tables......
> what about remote server>
> thanks,
>|||oj wrote:
> "remote server" is another instance of sqlserver that the local sqlserver
> connects to and queries data on behalf of the user. "linked server" is ver
y
> much the same thing, except it allows you to connect to any oledb data
> source.
>
I'm not quite sure about that definition - A remote server could just
as well be on another server.
AFAIK Remote server is just in there for backward compatibility and you
should use linked server.
Regards
Steen|||indeed, remote server is there for backward (sql6x) compatibility.
"Configuring Remote Servers
A remote server configuration allows a client connected to one server
running Microsoft SQL ServerT to execute a stored procedure on another
server running SQL Server without establishing another connection. The
server to which the client is connected accepts the client request and sends
the request to the remote server on the client's behalf. The remote server
processes the request and returns any results to the original server, which
in turn passes those results to the client.
Remote server configurations have been superseded by linked server
configurations in SQL Server version 7.0. Both stored procedures and
distributed queries are allowed against linked servers; however, only stored
procedures are allowed against remote servers. Support for remote servers is
provided for backward compatibility only. If you are interested in setting
up a server configuration to execute stored procedures on another server,
and do not have existing remote server configurations, use linked servers
instead of remote servers.
Remote Server Details
Remote servers are set up in pairs. To set up a pair of remote servers,
configure both servers to recognize each other as remote servers. Then,
verify that configuration options are set properly for both servers, so that
each server running SQL Server allows remote users to execute procedure
calls. Check the configuration options in the Server Properties dialog box
on both the local and the remote servers.
In most cases, you should not need to set configuration options for remote
servers; the defaults set on both local and remote computers by SQL Server
Setup allow for remote server connections.
For remote server access to work, the remote access configuration option,
which controls logins from remote servers, must be set to 1 (the default
setting) on both the local and remote computers. If the setting for either
server's remote access option has been changed, you must reset the option
(for one or both servers) back to 1 to allow remote access. This can be
accomplished through either SQL Server Enterprise Manager or the
Transact-SQL sp_configure statement.
From the local server, you can disable a remote server configuration to
prevent user access to that server. "
-oj
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:eShq9KkUGHA.6048@.TK2MSFTNGP11.phx.gbl...
> oj wrote:
> I'm not quite sure about that definition - A remote server could just as
> well be on another server.
> AFAIK Remote server is just in there for backward compatibility and you
> should use linked server.
> Regards
> Steen
Showing posts with label diff. Show all posts
Showing posts with label diff. Show all posts
Tuesday, March 20, 2012
Remote server VS linked server
hi,
Could any one tell me what is the diff between remote server and linked
server?
I know linked server is for current sql server to access tables......
what about remote server>
thanks,"remote server" is another instance of sqlserver that the local sqlserver
connects to and queries data on behalf of the user. "linked server" is very
much the same thing, except it allows you to connect to any oledb data
source.
-oj
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OyW3DV4TGHA.5500@.TK2MSFTNGP12.phx.gbl...
> hi,
> Could any one tell me what is the diff between remote server and linked
> server?
> I know linked server is for current sql server to access tables......
> what about remote server>
> thanks,
>|||oj wrote:
> "remote server" is another instance of sqlserver that the local sqlserver
> connects to and queries data on behalf of the user. "linked server" is very
> much the same thing, except it allows you to connect to any oledb data
> source.
>
I'm not quite sure about that definition - A remote server could just
as well be on another server.
AFAIK Remote server is just in there for backward compatibility and you
should use linked server.
Regards
Steen|||indeed, remote server is there for backward (sql6x) compatibility.
"Configuring Remote Servers
A remote server configuration allows a client connected to one server
running Microsoft® SQL ServerT to execute a stored procedure on another
server running SQL Server without establishing another connection. The
server to which the client is connected accepts the client request and sends
the request to the remote server on the client's behalf. The remote server
processes the request and returns any results to the original server, which
in turn passes those results to the client.
Remote server configurations have been superseded by linked server
configurations in SQL Server version 7.0. Both stored procedures and
distributed queries are allowed against linked servers; however, only stored
procedures are allowed against remote servers. Support for remote servers is
provided for backward compatibility only. If you are interested in setting
up a server configuration to execute stored procedures on another server,
and do not have existing remote server configurations, use linked servers
instead of remote servers.
Remote Server Details
Remote servers are set up in pairs. To set up a pair of remote servers,
configure both servers to recognize each other as remote servers. Then,
verify that configuration options are set properly for both servers, so that
each server running SQL Server allows remote users to execute procedure
calls. Check the configuration options in the Server Properties dialog box
on both the local and the remote servers.
In most cases, you should not need to set configuration options for remote
servers; the defaults set on both local and remote computers by SQL Server
Setup allow for remote server connections.
For remote server access to work, the remote access configuration option,
which controls logins from remote servers, must be set to 1 (the default
setting) on both the local and remote computers. If the setting for either
server's remote access option has been changed, you must reset the option
(for one or both servers) back to 1 to allow remote access. This can be
accomplished through either SQL Server Enterprise Manager or the
Transact-SQL sp_configure statement.
From the local server, you can disable a remote server configuration to
prevent user access to that server. "
-oj
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:eShq9KkUGHA.6048@.TK2MSFTNGP11.phx.gbl...
> oj wrote:
>> "remote server" is another instance of sqlserver that the local sqlserver
>> connects to and queries data on behalf of the user. "linked server" is
>> very much the same thing, except it allows you to connect to any oledb
>> data source.
>>
> I'm not quite sure about that definition - A remote server could just as
> well be on another server.
> AFAIK Remote server is just in there for backward compatibility and you
> should use linked server.
> Regards
> Steen
Could any one tell me what is the diff between remote server and linked
server?
I know linked server is for current sql server to access tables......
what about remote server>
thanks,"remote server" is another instance of sqlserver that the local sqlserver
connects to and queries data on behalf of the user. "linked server" is very
much the same thing, except it allows you to connect to any oledb data
source.
-oj
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OyW3DV4TGHA.5500@.TK2MSFTNGP12.phx.gbl...
> hi,
> Could any one tell me what is the diff between remote server and linked
> server?
> I know linked server is for current sql server to access tables......
> what about remote server>
> thanks,
>|||oj wrote:
> "remote server" is another instance of sqlserver that the local sqlserver
> connects to and queries data on behalf of the user. "linked server" is very
> much the same thing, except it allows you to connect to any oledb data
> source.
>
I'm not quite sure about that definition - A remote server could just
as well be on another server.
AFAIK Remote server is just in there for backward compatibility and you
should use linked server.
Regards
Steen|||indeed, remote server is there for backward (sql6x) compatibility.
"Configuring Remote Servers
A remote server configuration allows a client connected to one server
running Microsoft® SQL ServerT to execute a stored procedure on another
server running SQL Server without establishing another connection. The
server to which the client is connected accepts the client request and sends
the request to the remote server on the client's behalf. The remote server
processes the request and returns any results to the original server, which
in turn passes those results to the client.
Remote server configurations have been superseded by linked server
configurations in SQL Server version 7.0. Both stored procedures and
distributed queries are allowed against linked servers; however, only stored
procedures are allowed against remote servers. Support for remote servers is
provided for backward compatibility only. If you are interested in setting
up a server configuration to execute stored procedures on another server,
and do not have existing remote server configurations, use linked servers
instead of remote servers.
Remote Server Details
Remote servers are set up in pairs. To set up a pair of remote servers,
configure both servers to recognize each other as remote servers. Then,
verify that configuration options are set properly for both servers, so that
each server running SQL Server allows remote users to execute procedure
calls. Check the configuration options in the Server Properties dialog box
on both the local and the remote servers.
In most cases, you should not need to set configuration options for remote
servers; the defaults set on both local and remote computers by SQL Server
Setup allow for remote server connections.
For remote server access to work, the remote access configuration option,
which controls logins from remote servers, must be set to 1 (the default
setting) on both the local and remote computers. If the setting for either
server's remote access option has been changed, you must reset the option
(for one or both servers) back to 1 to allow remote access. This can be
accomplished through either SQL Server Enterprise Manager or the
Transact-SQL sp_configure statement.
From the local server, you can disable a remote server configuration to
prevent user access to that server. "
-oj
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:eShq9KkUGHA.6048@.TK2MSFTNGP11.phx.gbl...
> oj wrote:
>> "remote server" is another instance of sqlserver that the local sqlserver
>> connects to and queries data on behalf of the user. "linked server" is
>> very much the same thing, except it allows you to connect to any oledb
>> data source.
>>
> I'm not quite sure about that definition - A remote server could just as
> well be on another server.
> AFAIK Remote server is just in there for backward compatibility and you
> should use linked server.
> Regards
> Steen
Remote server VS linked server
hi,
Could any one tell me what is the diff between remote server and linked
server?
I know linked server is for current sql server to access tables......
what about remote server>
thanks,
"remote server" is another instance of sqlserver that the local sqlserver
connects to and queries data on behalf of the user. "linked server" is very
much the same thing, except it allows you to connect to any oledb data
source.
-oj
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OyW3DV4TGHA.5500@.TK2MSFTNGP12.phx.gbl...
> hi,
> Could any one tell me what is the diff between remote server and linked
> server?
> I know linked server is for current sql server to access tables......
> what about remote server>
> thanks,
>
|||oj wrote:
> "remote server" is another instance of sqlserver that the local sqlserver
> connects to and queries data on behalf of the user. "linked server" is very
> much the same thing, except it allows you to connect to any oledb data
> source.
>
I'm not quite sure about that definition - A remote server could just
as well be on another server.
AFAIK Remote server is just in there for backward compatibility and you
should use linked server.
Regards
Steen
|||indeed, remote server is there for backward (sql6x) compatibility.
"Configuring Remote Servers
A remote server configuration allows a client connected to one server
running Microsoft SQL ServerT to execute a stored procedure on another
server running SQL Server without establishing another connection. The
server to which the client is connected accepts the client request and sends
the request to the remote server on the client's behalf. The remote server
processes the request and returns any results to the original server, which
in turn passes those results to the client.
Remote server configurations have been superseded by linked server
configurations in SQL Server version 7.0. Both stored procedures and
distributed queries are allowed against linked servers; however, only stored
procedures are allowed against remote servers. Support for remote servers is
provided for backward compatibility only. If you are interested in setting
up a server configuration to execute stored procedures on another server,
and do not have existing remote server configurations, use linked servers
instead of remote servers.
Remote Server Details
Remote servers are set up in pairs. To set up a pair of remote servers,
configure both servers to recognize each other as remote servers. Then,
verify that configuration options are set properly for both servers, so that
each server running SQL Server allows remote users to execute procedure
calls. Check the configuration options in the Server Properties dialog box
on both the local and the remote servers.
In most cases, you should not need to set configuration options for remote
servers; the defaults set on both local and remote computers by SQL Server
Setup allow for remote server connections.
For remote server access to work, the remote access configuration option,
which controls logins from remote servers, must be set to 1 (the default
setting) on both the local and remote computers. If the setting for either
server's remote access option has been changed, you must reset the option
(for one or both servers) back to 1 to allow remote access. This can be
accomplished through either SQL Server Enterprise Manager or the
Transact-SQL sp_configure statement.
From the local server, you can disable a remote server configuration to
prevent user access to that server. "
-oj
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:eShq9KkUGHA.6048@.TK2MSFTNGP11.phx.gbl...
> oj wrote:
> I'm not quite sure about that definition - A remote server could just as
> well be on another server.
> AFAIK Remote server is just in there for backward compatibility and you
> should use linked server.
> Regards
> Steen
Could any one tell me what is the diff between remote server and linked
server?
I know linked server is for current sql server to access tables......
what about remote server>
thanks,
"remote server" is another instance of sqlserver that the local sqlserver
connects to and queries data on behalf of the user. "linked server" is very
much the same thing, except it allows you to connect to any oledb data
source.
-oj
"mecn" <mecn2002@.yahoo.com> wrote in message
news:OyW3DV4TGHA.5500@.TK2MSFTNGP12.phx.gbl...
> hi,
> Could any one tell me what is the diff between remote server and linked
> server?
> I know linked server is for current sql server to access tables......
> what about remote server>
> thanks,
>
|||oj wrote:
> "remote server" is another instance of sqlserver that the local sqlserver
> connects to and queries data on behalf of the user. "linked server" is very
> much the same thing, except it allows you to connect to any oledb data
> source.
>
I'm not quite sure about that definition - A remote server could just
as well be on another server.
AFAIK Remote server is just in there for backward compatibility and you
should use linked server.
Regards
Steen
|||indeed, remote server is there for backward (sql6x) compatibility.
"Configuring Remote Servers
A remote server configuration allows a client connected to one server
running Microsoft SQL ServerT to execute a stored procedure on another
server running SQL Server without establishing another connection. The
server to which the client is connected accepts the client request and sends
the request to the remote server on the client's behalf. The remote server
processes the request and returns any results to the original server, which
in turn passes those results to the client.
Remote server configurations have been superseded by linked server
configurations in SQL Server version 7.0. Both stored procedures and
distributed queries are allowed against linked servers; however, only stored
procedures are allowed against remote servers. Support for remote servers is
provided for backward compatibility only. If you are interested in setting
up a server configuration to execute stored procedures on another server,
and do not have existing remote server configurations, use linked servers
instead of remote servers.
Remote Server Details
Remote servers are set up in pairs. To set up a pair of remote servers,
configure both servers to recognize each other as remote servers. Then,
verify that configuration options are set properly for both servers, so that
each server running SQL Server allows remote users to execute procedure
calls. Check the configuration options in the Server Properties dialog box
on both the local and the remote servers.
In most cases, you should not need to set configuration options for remote
servers; the defaults set on both local and remote computers by SQL Server
Setup allow for remote server connections.
For remote server access to work, the remote access configuration option,
which controls logins from remote servers, must be set to 1 (the default
setting) on both the local and remote computers. If the setting for either
server's remote access option has been changed, you must reset the option
(for one or both servers) back to 1 to allow remote access. This can be
accomplished through either SQL Server Enterprise Manager or the
Transact-SQL sp_configure statement.
From the local server, you can disable a remote server configuration to
prevent user access to that server. "
-oj
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:eShq9KkUGHA.6048@.TK2MSFTNGP11.phx.gbl...
> oj wrote:
> I'm not quite sure about that definition - A remote server could just as
> well be on another server.
> AFAIK Remote server is just in there for backward compatibility and you
> should use linked server.
> Regards
> Steen
Remote Server Not Visible
Hi All,
I am trying to set up log shipping between SQL servers on two different
networks (diff forests) with a two way trust relationship.
Problem is that I can't see the remote SQL server in the destination
server drop down list (I can see local SQL servers).
The SQL agents on both machines are running under different accounts.
I have tried to add the account running the remote SQL agent to my local
SQL servers administrators group but this has no effect.
I can ping the server by name and it resolves OK.
I have registered the server with Enterprise manager, and even tried to
add it as a linked server to no effect.
Any ideas to resolve this would be much appreciated.
Ranj.
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
Ranj,
I have no way of emulating your situation here, but one thing I'd try is
using the client network utility to create an alias to the other server
based on IP address, register the alias in EM and then see if that appears
in the Log-shipping wizard.
HTH,
Paul Ibison
|||Hi Paul,
Thanks for the response.
I tried adding the server through the client network utility with tcp/IP
and then named pipes, but neither worked.
Is it possible to script transaction log shipping through stored
procedures ?
Ranj.
On Wed, 14 Jul 2004 17:09:24 +0100, Paul Ibison
<Paul.Ibison@.Pygmalion.Com> wrote:
> Ranj,
> I have no way of emulating your situation here, but one thing I'd try is
> using the client network utility to create an alias to the other server
> based on IP address, register the alias in EM and then see if that
> appears
> in the Log-shipping wizard.
> HTH,
> Paul Ibison
>
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
|||Ranejet,
there is a list of SPs for log shipping (and other sections) in BOL :
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\tsq
lref.chm::/ts_sp_00_519s.htm
It is possible to script it, but not possible to script it out from an
existing one, so this could take some time.
Please can you post back to let me know what OSs you are using?
Regards,
Paul Ibison
|||Hi Paul,
thanks for the info - I am using Windows 2000 Server edition on local and
remote - both have SQL Enterprise installed.
Both networks have their own forests and are connected with a two way
trust.
There is a checkpoint firewall between them used to esatblish a VPN.
Ranj.
|||Ranj,
you can setup logshipping using the resource kit utilities. I use the ones
that was for sql7 on sql2000 with no problems at all, it is eay to setup as
well.
let me know if you need the scripts and documentation from resource kit from
sql7.
regards
m
"ranejet" <not-tellint> wrote in message
news:opsa55bmjgcakp78@.idt.toare.co.uk...
> Hi Paul,
> Thanks for the response.
> I tried adding the server through the client network utility with tcp/IP
> and then named pipes, but neither worked.
> Is it possible to script transaction log shipping through stored
> procedures ?
> Ranj.
> On Wed, 14 Jul 2004 17:09:24 +0100, Paul Ibison
> <Paul.Ibison@.Pygmalion.Com> wrote:
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
|||Ranejet,
pinging the server doesn't mean port 1433 is open in the firewall. I'd check
that.
Also, use dnslookup to verify the ip address after you have successfully
pinged the server - it may be another server in a different domain.
HTH,
Paul Ibison
|||try an odbcping to verify 1433 is open.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eeD$nBoaEHA.3596@.tk2msftngp13.phx.gbl...
> Ranejet,
> pinging the server doesn't mean port 1433 is open in the firewall. I'd
check
> that.
> Also, use dnslookup to verify the ip address after you have successfully
> pinged the server - it may be another server in a different domain.
> HTH,
> Paul Ibison
>
|||If You can ping the Server, that probably means You have full IP connectivity, since ICMP is the first thing to block in a firewall.
What You might lack, however, is NetBIOS resolution, which Is possibly what the Enterprise Manager is looking for. Do You see the remote Server in the "network" in Windows Explorer ?
If not, activating NetBIOS over TCP/IP might work, alternatively, You need a common WINS server between the two servers to establish a browse list.
I am trying to set up log shipping between SQL servers on two different
networks (diff forests) with a two way trust relationship.
Problem is that I can't see the remote SQL server in the destination
server drop down list (I can see local SQL servers).
The SQL agents on both machines are running under different accounts.
I have tried to add the account running the remote SQL agent to my local
SQL servers administrators group but this has no effect.
I can ping the server by name and it resolves OK.
I have registered the server with Enterprise manager, and even tried to
add it as a linked server to no effect.
Any ideas to resolve this would be much appreciated.
Ranj.
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
Ranj,
I have no way of emulating your situation here, but one thing I'd try is
using the client network utility to create an alias to the other server
based on IP address, register the alias in EM and then see if that appears
in the Log-shipping wizard.
HTH,
Paul Ibison
|||Hi Paul,
Thanks for the response.
I tried adding the server through the client network utility with tcp/IP
and then named pipes, but neither worked.
Is it possible to script transaction log shipping through stored
procedures ?
Ranj.
On Wed, 14 Jul 2004 17:09:24 +0100, Paul Ibison
<Paul.Ibison@.Pygmalion.Com> wrote:
> Ranj,
> I have no way of emulating your situation here, but one thing I'd try is
> using the client network utility to create an alias to the other server
> based on IP address, register the alias in EM and then see if that
> appears
> in the Log-shipping wizard.
> HTH,
> Paul Ibison
>
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
|||Ranejet,
there is a list of SPs for log shipping (and other sections) in BOL :
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%2 0Server\80\Tools\Books\tsq
lref.chm::/ts_sp_00_519s.htm
It is possible to script it, but not possible to script it out from an
existing one, so this could take some time.
Please can you post back to let me know what OSs you are using?
Regards,
Paul Ibison
|||Hi Paul,
thanks for the info - I am using Windows 2000 Server edition on local and
remote - both have SQL Enterprise installed.
Both networks have their own forests and are connected with a two way
trust.
There is a checkpoint firewall between them used to esatblish a VPN.
Ranj.
|||Ranj,
you can setup logshipping using the resource kit utilities. I use the ones
that was for sql7 on sql2000 with no problems at all, it is eay to setup as
well.
let me know if you need the scripts and documentation from resource kit from
sql7.
regards
m
"ranejet" <not-tellint> wrote in message
news:opsa55bmjgcakp78@.idt.toare.co.uk...
> Hi Paul,
> Thanks for the response.
> I tried adding the server through the client network utility with tcp/IP
> and then named pipes, but neither worked.
> Is it possible to script transaction log shipping through stored
> procedures ?
> Ranj.
> On Wed, 14 Jul 2004 17:09:24 +0100, Paul Ibison
> <Paul.Ibison@.Pygmalion.Com> wrote:
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
|||Ranejet,
pinging the server doesn't mean port 1433 is open in the firewall. I'd check
that.
Also, use dnslookup to verify the ip address after you have successfully
pinged the server - it may be another server in a different domain.
HTH,
Paul Ibison
|||try an odbcping to verify 1433 is open.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eeD$nBoaEHA.3596@.tk2msftngp13.phx.gbl...
> Ranejet,
> pinging the server doesn't mean port 1433 is open in the firewall. I'd
check
> that.
> Also, use dnslookup to verify the ip address after you have successfully
> pinged the server - it may be another server in a different domain.
> HTH,
> Paul Ibison
>
|||If You can ping the Server, that probably means You have full IP connectivity, since ICMP is the first thing to block in a firewall.
What You might lack, however, is NetBIOS resolution, which Is possibly what the Enterprise Manager is looking for. Do You see the remote Server in the "network" in Windows Explorer ?
If not, activating NetBIOS over TCP/IP might work, alternatively, You need a common WINS server between the two servers to establish a browse list.
Subscribe to:
Posts (Atom)