SQL Server protocol

[mendhak]

Is it TCP/IP? or some propriety extension from M$ on the very same? Or other?

[mendhak]

It's such a simple question!! How could u not know this??

What protocol! Is it TCP/IP?

[cafeenman]

Yes it might or might not be.

[mendhak]

That may have been the single most useful answer I've ever received in VBF. Thanks.

Anyone else got any 'helpful' answers?

[mendhak]

Boss: So have you figured out the problem yet?
Me: Yeah, SQL Server might or might not use TCP/IP. So that might or might not be the problem.
Boss: SO you're saying we might or might not even have a problem?
Me: Maybe.

[cafeenman]

Originally posted by mendhak

Exactly. That's what I said. Which part aren't you getting?

[mendhak]

Originally posted by cafeenman

Which part aren't you getting?

Uhm... the answer.

[cafeenman]

Originally posted by mendhak


Uhm... the answer.

Oh, well, that's the part I don't know, so I can't help you any more than I have already.

[mendhak]

You could clear out your inbox, maybe.

[cafeenman]

Originally posted by mendhak
You could clear out your inbox, maybe.

but my web host doesn't support Front Page extensions.























Chit Chat here we come.

[mendhak]

Originally posted by cafeenman

but my web host doesn't support Front Page extensions.























Chit Chat here we come.

Those camel riding incestuous bastards! Oh, and chit chat has arrived. In the words of the great Flustor,

Yaaaaay!

[mendhak]

574 views!!!!!

OK... ignore this one. I've posted another thread.

[Slaine]

Take your pick froggy:

[cafeenman]

SEE???? I was right!!!

You can have TCP/IP or
Nightwalker Link or
Named Popes or
Barnyard vines.

Isn't that what I told you in my first post???? Pay attention frog boy!!!!!!!

[mendhak]

Originally posted by Slaine
Take your pick froggy:

Where where where where????

You just showed me today's Holy Grail!

[RSINGH]

It should be under your SQL Server menu under 'Client Network Utility'.

[mendhak]

And uhm... how do I redirect you guys to here:

http://www.vbforums.com/showthread.p...hreadid=177886

Uhm... click it.

[mendhak]

Originally posted by RSINGH
It should be under your SQL Server menu under 'Client Network Utility'.

thanks ranj.

and everyone.

and profuse thank yous to cafeenman. (ad infinitium)

[Frans C]

And if you want to use a specific protocol for your connection, you can specify it in the connection string under "Network Library=xxxxxx"

Now the tricky part, the value for xxxxxx is the name of the dll for the network library, without the extension. You can find the dll's to use in the client network utility.

eg
strConn = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Northwind;Data Source=test_sql;Network Library=dbmssocn"

will connect using TCP/IP

Of course both client and server must support the protocol.

[mendhak]

Originally posted by Frans C
And if you want to use a specific protocol for your connection, you can specify it in the connection string under "Network Library=xxxxxx"

Now the tricky part, the value for xxxxxx is the name of the dll for the network library, without the extension. You can find the dll's to use in the client network utility.

eg
strConn = "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Northwind;Data Source=test_sql;Network Library=dbmssocn"

will connect using TCP/IP

Of course both client and server must support the protocol.

Actually, I doubt I'll be doing that. I'm working on a heterogenous network, a sad mixture of Novell and Windows, so I suppose I'll have to configure this at the server itself.

[mendhak]

What the **** is going on here? 990 views? DB FREAKY

[Frans C]

Yep, that would be best.
I only used it in an NT only network, with multiple domains, to ensure TCP/IP was used, and not Named Pipes. This to avoid problems when the server was in a different domain then the user logged on to.