Let's say there are two databases, DB#1 and DB#2, and a user JOE. DB#1 and
DB#2 have stored procedures identically named (.e.g. "uspGetOrders") with
the same signature. Is it possible when running a trace that filters on
user like JOE, to determine which database the procedure belongs to which
JOE happens to be executing? How can I tell which it is? When I double
click on the trace line to view the details, the sp name is displayed
without a db or owner prefix. And if I filter on database name, I see this:
exec uspGetOrders @.p1 no matter which database I happen to choose. The
trace doesn't seem to tell me where the procedure "originates" so to speak.
I'm trying to figure out why the procedure is returning no data when it is
moved to DB#2 and points back to tables in DB1. The procedure worked fine
when it was in DB#1. The stored procedure refers to the table as
DB1.dbo.Orders and JOE has been granted execute privileges (via a role) on
DB2.dbo.uspGetOrders. JOE had no problem working with the procedure when
it was in the same database as the table. JOE belongs to a role that has
select privileges on Orders.
The only other thing that has changed is the Initial Catalog when JOE
connects. Now it is DB2.
Thanks!
TimoIf a user is in DB#1 and what you see executed is
uspGetOrders, it's executing the stored procedure in DB#1.
It would have to be qualified by the database name to
execute the stored procedure in DB#2.
If you are on SQL Server 2000 and if you are on SP3, then
the issue with the stored procedure could be due to not
having cross database ownership chaining enabled. If you are
running under this configuration and have updated your books
online, you can find more information in books online under
the topic:
Cross DB Ownership Chaining
-Sue
On Mon, 12 Apr 2004 12:25:28 -0400, "Timo"
<timo@.anonymous.com> wrote:
>Let's say there are two databases, DB#1 and DB#2, and a user JOE. DB#1 and
>DB#2 have stored procedures identically named (.e.g. "uspGetOrders") with
>the same signature. Is it possible when running a trace that filters on
>user like JOE, to determine which database the procedure belongs to which
>JOE happens to be executing? How can I tell which it is? When I double
>click on the trace line to view the details, the sp name is displayed
>without a db or owner prefix. And if I filter on database name, I see this
:
>exec uspGetOrders @.p1 no matter which database I happen to choose. The
>trace doesn't seem to tell me where the procedure "originates" so to speak.
>I'm trying to figure out why the procedure is returning no data when it is
>moved to DB#2 and points back to tables in DB1. The procedure worked fine
>when it was in DB#1. The stored procedure refers to the table as
>DB1.dbo.Orders and JOE has been granted execute privileges (via a role) on
>DB2.dbo.uspGetOrders. JOE had no problem working with the procedure when
>it was in the same database as the table. JOE belongs to a role that has
>select privileges on Orders.
>The only other thing that has changed is the Initial Catalog when JOE
>connects. Now it is DB2.
>Thanks!
>Timo
>
>
>|||Sue,
Thanks for the reply. It doesn't appear to be Cross DB Ownership chaining;
same issue after this:
EXEC sp_configure 'Cross DB Ownership Chaining', '0'; RECONFIGURE
EXEC sp_dboption 'DB1', 'db chaining', 'ON'
EXEC sp_dboption 'DB2', 'db chaining', 'ON'
Trace shows the procedure being invoked; the IN parameter is there, but all
the OUT parameters are null. When I've encountered similar symptoms in Trace
before, it was because the user lacked execute privileges on the procedure.
But JOE has these privileges by virtue of membership in a db role.
Any other way to troubleshoot this scenario using Trace?
Thanks again.
Timo
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:vcil70hj0j37239l9ds5tevbtfotc6n506@.
4ax.com...
> If a user is in DB#1 and what you see executed is
> uspGetOrders, it's executing the stored procedure in DB#1.
> It would have to be qualified by the database name to
> execute the stored procedure in DB#2.
> If you are on SQL Server 2000 and if you are on SP3, then
> the issue with the stored procedure could be due to not
> having cross database ownership chaining enabled. If you are
> running under this configuration and have updated your books
> online, you can find more information in books online under
> the topic:
> Cross DB Ownership Chaining
> -Sue
> On Mon, 12 Apr 2004 12:25:28 -0400, "Timo"
> <timo@.anonymous.com> wrote:
>
and
which
this:
speak.
is
on
when
>|||In Profiler, you'd want to select exceptions from the Errors
and Warnings event class. That will give you any errors
being raised. You should also make sure you are capturing
the completion of the stored procedure, not just the
starting event.
Did you check the owners of the objects (the stored
procedure and the underlying tables) and databases involved?
The databases need to be owned by the same login. The
objects need to have the same object owner.
-Sue
On Mon, 12 Apr 2004 13:40:39 -0400, "Timo"
<timo@.anonymous.com> wrote:
>Sue,
>Thanks for the reply. It doesn't appear to be Cross DB Ownership chaining;
>same issue after this:
>EXEC sp_configure 'Cross DB Ownership Chaining', '0'; RECONFIGURE
>EXEC sp_dboption 'DB1', 'db chaining', 'ON'
>EXEC sp_dboption 'DB2', 'db chaining', 'ON'
>Trace shows the procedure being invoked; the IN parameter is there, but all
>the OUT parameters are null. When I've encountered similar symptoms in Trac
e
>before, it was because the user lacked execute privileges on the procedure.
>But JOE has these privileges by virtue of membership in a db role.
>Any other way to troubleshoot this scenario using Trace?
>Thanks again.
>Timo
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:vcil70hj0j37239l9ds5tevbtfotc6n506@.
4ax.com...
>and
>which
>this:
>speak.
>is
>on
>when
>|||To add to Sue's response, if your objects are owned by 'dbo', the database
owners need to be the same in order to maintain an unbroken ownership chain
for dbo-owned objects. If needed, you can use sp_changedbowner to ensure
the databases are owned by the same login:
USE DB1
EXEC sp_changedbowner 'MyOwnerLogin'
USE DB2
EXEC sp_changedbowner 'MyOwnerLogin'
Users will need access to both databases but permissions on indirectly
referenced objects are not needed.
Hope this helps.
Dan Guzman
SQL Server MVP
"Timo" <timo@.anonymous.com> wrote in message
news:%23t2AiVLIEHA.580@.TK2MSFTNGP12.phx.gbl...
> Sue,
> Thanks for the reply. It doesn't appear to be Cross DB Ownership
chaining;
> same issue after this:
> EXEC sp_configure 'Cross DB Ownership Chaining', '0'; RECONFIGURE
> EXEC sp_dboption 'DB1', 'db chaining', 'ON'
> EXEC sp_dboption 'DB2', 'db chaining', 'ON'
> Trace shows the procedure being invoked; the IN parameter is there, but
all
> the OUT parameters are null. When I've encountered similar symptoms in
Trace
> before, it was because the user lacked execute privileges on the
procedure.
> But JOE has these privileges by virtue of membership in a db role.
> Any other way to troubleshoot this scenario using Trace?
> Thanks again.
> Timo
>
> "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:vcil70hj0j37239l9ds5tevbtfotc6n506@.
4ax.com...
> and
with
on
> which
> this:
The
> speak.
> is
fine
> on
> when
has
>|||Thank you Dan for the dbchangeowner tip, and Sue for the Errors and Warnings
event class tip. I will use them to advantage. In Trace, I was not seeing
the completion of the sp, only the starting event, and so was unable to
determine what database the client was pointing at. After having the
developer re-check the connection string in the client-side code, we found
that the wrong database was being specified as the initial catalog.
Timo
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:ukvyQdVIEHA.2972@.TK2MSFTNGP12.phx.gbl...
> To add to Sue's response, if your objects are owned by 'dbo', the database
> owners need to be the same in order to maintain an unbroken ownership
chain
> for dbo-owned objects. If needed, you can use sp_changedbowner to ensure
> the databases are owned by the same login:
> USE DB1
> EXEC sp_changedbowner 'MyOwnerLogin'
> USE DB2
> EXEC sp_changedbowner 'MyOwnerLogin'
> Users will need access to both databases but permissions on indirectly
> referenced objects are not needed.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Timo" <timo@.anonymous.com> wrote in message
> news:%23t2AiVLIEHA.580@.TK2MSFTNGP12.phx.gbl...
> chaining;
> all
> Trace
> procedure.
DB#1
> with
> on
double
see
> The
it
> fine
role)
> has
>
Showing posts with label named. Show all posts
Showing posts with label named. Show all posts
Wednesday, March 28, 2012
Saturday, February 25, 2012
process could not connect to Distributor
Sql Server SP4 on the publisher/distributer.
MSDE SP4 on the subscriber
Merge Replication
Anonymous Pull Subscriptions
TCP/IP only - removed Named Pipes
Windows Authent only - removed SQL Server
Setup an alias on the subscriber to the publisher.
Running on same network but different workgroups. Can not use Windows
Authentication as moving to Internet model.
Followed
http://support.microsoft.com/default...&Product=sql2k
So I setup the publisher to use an SA user and gave that SA user ownership
and admin rights to the publisher database.
I keep getting this error from the ActiveX component in VB.NET on the
subscriber: The process could not connect to Distributor 'W2KSERVER'.
SQL Server does not exist or access denied.
I had these guys working when it was SP3a, still had named pipes, and using
Windows Authentication passthrough.
Thanks,
Buzz
configure distributornetwork for tcpip, use the fqdn for the
distributoraddress (ie sqlserver.mydomainname.com).
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Buzz" <buzz@.online.nospam> wrote in message
news:EC950BD0-5245-47EB-8320-06D6633633BA@.microsoft.com...
> Sql Server SP4 on the publisher/distributer.
> MSDE SP4 on the subscriber
> Merge Replication
> Anonymous Pull Subscriptions
> TCP/IP only - removed Named Pipes
> Windows Authent only - removed SQL Server
> Setup an alias on the subscriber to the publisher.
> Running on same network but different workgroups. Can not use Windows
> Authentication as moving to Internet model.
> Followed
>
http://support.microsoft.com/default...&Product=sql2k
> So I setup the publisher to use an SA user and gave that SA user ownership
> and admin rights to the publisher database.
> I keep getting this error from the ActiveX component in VB.NET on the
> subscriber: The process could not connect to Distributor 'W2KSERVER'.
> SQL Server does not exist or access denied.
> I had these guys working when it was SP3a, still had named pipes, and
using
> Windows Authentication passthrough.
> Thanks,
> Buzz
>
>
|||Hello,
Name resolution must be working between all machines involved in
replication. Otherwise, you may receive the error message.
I suggest that you perform the following steps to narrow down the issue:
* Drop the subcription and then drop the publication.
* Setup name resolution both ways between the machines. There are several
options for achieving name resolution. You can use CNU aliases
(cliconfg.exe), hosts files, WINS, and/or DNS.
* On the publisher reregister in publisher and subscriber in Enterprise
Manager by netbios name instead of by IP address.
* On the remote server, register the publisher and the subscriber in
Enterprise Manager by netbios name (@.@.servername).
* Recreate the publication and then recreate the subscription.
* Run the Merge agent. Check the issue.
The following information is for your reference:
Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/?id=328306
324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
2000)
http://support.microsoft.com/?id=324992
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||All that and it turns out it was a software firewall issue with XP on the
subscriber laptop.
However, now I am stuck with the next issue. Part of replicating over
untrusted domains or the internet means I need to use FTP. On the subscribers
I use the ActiveX merge module.
I specify the FTP address:
_merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
End If
Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
_merge.FTPAddress = Me.txtFtpAddress.Text
But it keeps erroring out saying it cannot find the FTP location specified
at the value I have for _merge.Publisher?
The value for the Ftp is ftp://192.168.1.2/repldata.
The value for the Publisher is server909.
I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
But I'm not going to be doing LMHOSTS management on 500+ production laptops
and we plan on using different FTP servers that are different than the SQL
Server.
"Sophie Guo [MSFT]" wrote:
> Hello,
> Name resolution must be working between all machines involved in
> replication. Otherwise, you may receive the error message.
> I suggest that you perform the following steps to narrow down the issue:
> * Drop the subcription and then drop the publication.
> * Setup name resolution both ways between the machines. There are several
> options for achieving name resolution. You can use CNU aliases
> (cliconfg.exe), hosts files, WINS, and/or DNS.
> * On the publisher reregister in publisher and subscriber in Enterprise
> Manager by netbios name instead of by IP address.
> * On the remote server, register the publisher and the subscriber in
> Enterprise Manager by netbios name (@.@.servername).
> * Recreate the publication and then recreate the subscription.
> * Run the Merge agent. Check the issue.
> The following information is for your reference:
> Potential causes of the "SQL Server does not exist or access denied" error
> message
> http://support.microsoft.com/?id=328306
> 324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
> 2000)
> http://support.microsoft.com/?id=324992
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Not sure if the following will help, but let me try to clarify a few things:
1) Ftp support in SQL replication applies only to transfer of snapshot
files, movement of SQL changes would require a regular connection to SQL
server (Publisher and Distributor).
2) The Ftp* properties on the Merge\Distribution ActiveX control have
actually been deprecated in SQL2000, configuration of FTP snapshot support is
done at the publication level (right-click publication for properties). Once
that is confiigured, you will need to regenerate a new snapshot for the
settings to take effect. And when you start the merge control, all you need
to do is to specify a FileTransferType of FTP. In hind-sight, it was probably
a mistake not to take out the FTP* properties completely.
3) There is still the all important task of getting the merge activeX
control to establish a regular connection to SQL Server from an untrusted
domain in the first place. This typically means that either 1) to expose
whatever port that the distributor and publisher are listening on (default
SQL Server port is 1433) to the outside world (or accessible from the
laptops) and then use the Distributor|PublisherNetwork|Address properties to
point to the exposed IP address\port configuration, or 2) (recommended) to
configure VPN between the laptops and the Publisher\Distributor machines so
regular SQL Server connections can be established. If you decide to use the
VPN approach, there really is no need to configure FTP for the snapshot files
as regular UNC shares should be accessible by the laptops.
HTH
-Raymond
"Buzz" wrote:
[vbcol=seagreen]
> All that and it turns out it was a software firewall issue with XP on the
> subscriber laptop.
> However, now I am stuck with the next issue. Part of replicating over
> untrusted domains or the internet means I need to use FTP. On the subscribers
> I use the ActiveX merge module.
> I specify the FTP address:
> _merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
> If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
> Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
> End If
> Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
> _merge.FTPAddress = Me.txtFtpAddress.Text
> But it keeps erroring out saying it cannot find the FTP location specified
> at the value I have for _merge.Publisher?
> The value for the Ftp is ftp://192.168.1.2/repldata.
> The value for the Publisher is server909.
> I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
> But I'm not going to be doing LMHOSTS management on 500+ production laptops
> and we plan on using different FTP servers that are different than the SQL
> Server.
> "Sophie Guo [MSFT]" wrote:
MSDE SP4 on the subscriber
Merge Replication
Anonymous Pull Subscriptions
TCP/IP only - removed Named Pipes
Windows Authent only - removed SQL Server
Setup an alias on the subscriber to the publisher.
Running on same network but different workgroups. Can not use Windows
Authentication as moving to Internet model.
Followed
http://support.microsoft.com/default...&Product=sql2k
So I setup the publisher to use an SA user and gave that SA user ownership
and admin rights to the publisher database.
I keep getting this error from the ActiveX component in VB.NET on the
subscriber: The process could not connect to Distributor 'W2KSERVER'.
SQL Server does not exist or access denied.
I had these guys working when it was SP3a, still had named pipes, and using
Windows Authentication passthrough.
Thanks,
Buzz
configure distributornetwork for tcpip, use the fqdn for the
distributoraddress (ie sqlserver.mydomainname.com).
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Buzz" <buzz@.online.nospam> wrote in message
news:EC950BD0-5245-47EB-8320-06D6633633BA@.microsoft.com...
> Sql Server SP4 on the publisher/distributer.
> MSDE SP4 on the subscriber
> Merge Replication
> Anonymous Pull Subscriptions
> TCP/IP only - removed Named Pipes
> Windows Authent only - removed SQL Server
> Setup an alias on the subscriber to the publisher.
> Running on same network but different workgroups. Can not use Windows
> Authentication as moving to Internet model.
> Followed
>
http://support.microsoft.com/default...&Product=sql2k
> So I setup the publisher to use an SA user and gave that SA user ownership
> and admin rights to the publisher database.
> I keep getting this error from the ActiveX component in VB.NET on the
> subscriber: The process could not connect to Distributor 'W2KSERVER'.
> SQL Server does not exist or access denied.
> I had these guys working when it was SP3a, still had named pipes, and
using
> Windows Authentication passthrough.
> Thanks,
> Buzz
>
>
|||Hello,
Name resolution must be working between all machines involved in
replication. Otherwise, you may receive the error message.
I suggest that you perform the following steps to narrow down the issue:
* Drop the subcription and then drop the publication.
* Setup name resolution both ways between the machines. There are several
options for achieving name resolution. You can use CNU aliases
(cliconfg.exe), hosts files, WINS, and/or DNS.
* On the publisher reregister in publisher and subscriber in Enterprise
Manager by netbios name instead of by IP address.
* On the remote server, register the publisher and the subscriber in
Enterprise Manager by netbios name (@.@.servername).
* Recreate the publication and then recreate the subscription.
* Run the Merge agent. Check the issue.
The following information is for your reference:
Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/?id=328306
324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
2000)
http://support.microsoft.com/?id=324992
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||All that and it turns out it was a software firewall issue with XP on the
subscriber laptop.
However, now I am stuck with the next issue. Part of replicating over
untrusted domains or the internet means I need to use FTP. On the subscribers
I use the ActiveX merge module.
I specify the FTP address:
_merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
End If
Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
_merge.FTPAddress = Me.txtFtpAddress.Text
But it keeps erroring out saying it cannot find the FTP location specified
at the value I have for _merge.Publisher?
The value for the Ftp is ftp://192.168.1.2/repldata.
The value for the Publisher is server909.
I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
But I'm not going to be doing LMHOSTS management on 500+ production laptops
and we plan on using different FTP servers that are different than the SQL
Server.
"Sophie Guo [MSFT]" wrote:
> Hello,
> Name resolution must be working between all machines involved in
> replication. Otherwise, you may receive the error message.
> I suggest that you perform the following steps to narrow down the issue:
> * Drop the subcription and then drop the publication.
> * Setup name resolution both ways between the machines. There are several
> options for achieving name resolution. You can use CNU aliases
> (cliconfg.exe), hosts files, WINS, and/or DNS.
> * On the publisher reregister in publisher and subscriber in Enterprise
> Manager by netbios name instead of by IP address.
> * On the remote server, register the publisher and the subscriber in
> Enterprise Manager by netbios name (@.@.servername).
> * Recreate the publication and then recreate the subscription.
> * Run the Merge agent. Check the issue.
> The following information is for your reference:
> Potential causes of the "SQL Server does not exist or access denied" error
> message
> http://support.microsoft.com/?id=328306
> 324992 How to use replication with SQL Server 2000 Desktop Engine (MSDE
> 2000)
> http://support.microsoft.com/?id=324992
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Not sure if the following will help, but let me try to clarify a few things:
1) Ftp support in SQL replication applies only to transfer of snapshot
files, movement of SQL changes would require a regular connection to SQL
server (Publisher and Distributor).
2) The Ftp* properties on the Merge\Distribution ActiveX control have
actually been deprecated in SQL2000, configuration of FTP snapshot support is
done at the publication level (right-click publication for properties). Once
that is confiigured, you will need to regenerate a new snapshot for the
settings to take effect. And when you start the merge control, all you need
to do is to specify a FileTransferType of FTP. In hind-sight, it was probably
a mistake not to take out the FTP* properties completely.
3) There is still the all important task of getting the merge activeX
control to establish a regular connection to SQL Server from an untrusted
domain in the first place. This typically means that either 1) to expose
whatever port that the distributor and publisher are listening on (default
SQL Server port is 1433) to the outside world (or accessible from the
laptops) and then use the Distributor|PublisherNetwork|Address properties to
point to the exposed IP address\port configuration, or 2) (recommended) to
configure VPN between the laptops and the Publisher\Distributor machines so
regular SQL Server connections can be established. If you decide to use the
VPN approach, there really is no need to configure FTP for the snapshot files
as regular UNC shares should be accessible by the laptops.
HTH
-Raymond
"Buzz" wrote:
[vbcol=seagreen]
> All that and it turns out it was a software firewall issue with XP on the
> subscriber laptop.
> However, now I am stuck with the next issue. Part of replicating over
> untrusted domains or the internet means I need to use FTP. On the subscribers
> I use the ActiveX merge module.
> I specify the FTP address:
> _merge.FileTransferType = FILE_TRANSFER_TYPE.FILETRANSFERFTP
> If Me.txtFtpAddress.Text.StartsWith("ftp://") = False Then
> Me.txtFtpAddress.Text = "ftp://" & Me.txtFtpAddress.Text
> End If
> Me.txtFtpAddress.Text = Me.txtFtpAddress.Text.Replace("\", "/")
> _merge.FTPAddress = Me.txtFtpAddress.Text
> But it keeps erroring out saying it cannot find the FTP location specified
> at the value I have for _merge.Publisher?
> The value for the Ftp is ftp://192.168.1.2/repldata.
> The value for the Publisher is server909.
> I put an LMHOSTS entry to route the 192.168.1.2 to server909 it works.
> But I'm not going to be doing LMHOSTS management on 500+ production laptops
> and we plan on using different FTP servers that are different than the SQL
> Server.
> "Sophie Guo [MSFT]" wrote:
Labels:
connect,
database,
distributer,
distributor,
microsoft,
msde,
mysql,
named,
oracle,
process,
publisher,
pull,
replicationanonymous,
server,
sp4,
sql,
subscribermerge,
subscriptionstcp
Subscribe to:
Posts (Atom)