OT: Database Design Samples

Long time ago I saw a site having samples of database design for each type
of biz like accounting, retails, etc. I can't find it any more. If you
still have the link please post. Thanks.This is one link with a variety of data models:
http://www.databaseanswers.org/data_models/index.htm
-Sue
On Wed, 10 May 2006 14:52:14 -0700, "ME" <ME@.mail.com>
wrote:
>Long time ago I saw a site having samples of database design for each type
>of biz like accounting, retails, etc. I can't find it any more. If you
>still have the link please post. Thanks.
>|||Thanks a lot.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:co0562hhlf4i9r81iqhb6u4l6r7obi4v0j@.4ax.com...
> This is one link with a variety of data models:
> http://www.databaseanswers.org/data_models/index.htm
> -Sue
> On Wed, 10 May 2006 14:52:14 -0700, "ME" <ME@.mail.com>
> wrote:
>>Long time ago I saw a site having samples of database design for each type
>>of biz like accounting, retails, etc. I can't find it any more. If you
>>still have the link please post. Thanks.
>

OSQL using named pipes instead of TCP/IP

Hi,
I'm having a small issue with OSQL. When I type "OSQL -S MYSERVER -E" , it
connects through TCP/IP, but on one client (that has DEVELOPER edition
installed), it tries to connect through Named Pipes, which is disabled for
the server that I'm trying to connect to. I checked the Client Config
Protocols and TCP/IP (2) is listed before Named Pipes (3).
I know I can prefix the server name with TCP: to force it to use TCP/IP,
but I don't want to do that. How can I get OSQL to connect through TCP/IP
instead of Named Pipes? Again the client has SQL 2005 Developer and the
Server has SQL 2005 Standard
Thanks!Found out. There was an alias for this server in there that told it to use
NP. Now to find out why there was an alias in there. . . . .
"Nieves" <JuanN@.yahoo.com> wrote in message
news:%238m7S8yPHHA.2312@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I'm having a small issue with OSQL. When I type "OSQL -S MYSERVER -E" ,
> it connects through TCP/IP, but on one client (that has DEVELOPER edition
> installed), it tries to connect through Named Pipes, which is disabled for
> the server that I'm trying to connect to. I checked the Client Config
> Protocols and TCP/IP (2) is listed before Named Pipes (3).
> I know I can prefix the server name with TCP: to force it to use TCP/IP,
> but I don't want to do that. How can I get OSQL to connect through TCP/IP
> instead of Named Pipes? Again the client has SQL 2005 Developer and the
> Server has SQL 2005 Standard
> Thanks!
>

OSQL using named pipes instead of TCP/IP

Hi,
I'm having a small issue with OSQL. When I type "OSQL -S MYSERVER -E" , it
connects through TCP/IP, but on one client (that has DEVELOPER edition
installed), it tries to connect through Named Pipes, which is disabled for
the server that I'm trying to connect to. I checked the Client Config
Protocols and TCP/IP (2) is listed before Named Pipes (3).
I know I can prefix the server name with TCP: to force it to use TCP/IP,
but I don't want to do that. How can I get OSQL to connect through TCP/IP
instead of Named Pipes? Again the client has SQL 2005 Developer and the
Server has SQL 2005 Standard
Thanks!
Found out. There was an alias for this server in there that told it to use
NP. Now to find out why there was an alias in there. . . . .
"Nieves" <JuanN@.yahoo.com> wrote in message
news:%238m7S8yPHHA.2312@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I'm having a small issue with OSQL. When I type "OSQL -S MYSERVER -E" ,
> it connects through TCP/IP, but on one client (that has DEVELOPER edition
> installed), it tries to connect through Named Pipes, which is disabled for
> the server that I'm trying to connect to. I checked the Client Config
> Protocols and TCP/IP (2) is listed before Named Pipes (3).
> I know I can prefix the server name with TCP: to force it to use TCP/IP,
> but I don't want to do that. How can I get OSQL to connect through TCP/IP
> instead of Named Pipes? Again the client has SQL 2005 Developer and the
> Server has SQL 2005 Standard
> Thanks!
>

OSQL using named pipes instead of TCP/IP

Hi,
I'm having a small issue with OSQL. When I type "OSQL -S MYSERVER -E" , it
connects through TCP/IP, but on one client (that has DEVELOPER edition
installed), it tries to connect through Named Pipes, which is disabled for
the server that I'm trying to connect to. I checked the Client Config
Protocols and TCP/IP (2) is listed before Named Pipes (3).
I know I can prefix the server name with TCP: to force it to use TCP/IP,
but I don't want to do that. How can I get OSQL to connect through TCP/IP
instead of Named Pipes? Again the client has SQL 2005 Developer and the
Server has SQL 2005 Standard
Thanks!Found out. There was an alias for this server in there that told it to use
NP. Now to find out why there was an alias in there. . . . .
"Nieves" <JuanN@.yahoo.com> wrote in message
news:%238m7S8yPHHA.2312@.TK2MSFTNGP04.phx.gbl...
> Hi,
> I'm having a small issue with OSQL. When I type "OSQL -S MYSERVER -E" ,
> it connects through TCP/IP, but on one client (that has DEVELOPER edition
> installed), it tries to connect through Named Pipes, which is disabled for
> the server that I'm trying to connect to. I checked the Client Config
> Protocols and TCP/IP (2) is listed before Named Pipes (3).
> I know I can prefix the server name with TCP: to force it to use TCP/IP,
> but I don't want to do that. How can I get OSQL to connect through TCP/IP
> instead of Named Pipes? Again the client has SQL 2005 Developer and the
> Server has SQL 2005 Standard
> Thanks!
>