Re: dbservername/dbserveraliases/nettype
>BTW be careful to not use the same port for shared memory and tcp in
>the sqlhosts on the server >
>Art S. Kagel
Art,
We've been using the same port for shared memory and tcp for a year now in
production.
7.23
ex.
sqlhosts:
prod onipcshm aruba sqlexec
onconfig:
DBSERVERNAME prod
DBSERVERALIASES
NETTYPE ipcshm,1,256,CPU
NETTYPE soctcp,1,256,NET
The engine starts a listener thread on the sqlexec port and also accepts
shared memory connections.
if you only have a NETTYPE of ipcshm then the service entry in the sqlhosts
for the onipcshm seems to accept anything (not needing to be defined in the
services file) The manual says that the services entry is an internal
placeholder when used with ipcshm, whatever that's worth.
The local process seem to connect via shared memory fine while the tcp
connections use the sqlexec socket.
do you know of any drawbacks?
Thanks,
Scott Kolaya