By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,200 Members | 1,755 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,200 IT Pros & Developers. It's quick & easy.

Protocol or message pattern of SQL Server client and database syst

P: n/a
Now we have some trouble to directly access to SQL Server database.

I would like to know if there is a special protocol in the communication
between SQL SERVER client and databse system. What is the messaging pattern?

Thank you for any help.

David
May 16 '07 #1
Share this Question
Share on Google+
8 Replies


P: n/a
There are really only two areas here:
1) getting the connection string right.
2) Ensuring that the SQL Server is enabled for remote access, the correct
transports (e.g. TCP, Named Pipes) are enabled, and that mixed mode
authentication is enabled.

Once you can connect to your database you won't need to worry about
"messaging patterns" or protocols.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"david" wrote:
Now we have some trouble to directly access to SQL Server database.

I would like to know if there is a special protocol in the communication
between SQL SERVER client and databse system. What is the messaging pattern?

Thank you for any help.

David
May 16 '07 #2

P: n/a

To followup:

Correct Transports:
Sometimes you can switch out which one it is using to experiment with better
performance.
I remember a client that was a dog with named pipes, and tcp/ip fixed it.

Sql Server defaults to port 1433. So that port has to be open. (Or
whichever one it was setup for).

The things I mention are subpar to what Peter mentioned.
(Aka, don't go chasing these until you get the other stuff resolved first)

Get the connection working, and you don't worry about the other stuff.
To make sure you got a good connection string, you can try this object.
SqlConnectionStringBuilder

http://www.google.com/search?hl=en&q...r+&btnG=Search

"Peter Bromberg [C# MVP]" <pb*******@yahoo.yabbadabbadoo.comwrote in
message news:03**********************************@microsof t.com...
There are really only two areas here:
1) getting the connection string right.
2) Ensuring that the SQL Server is enabled for remote access, the correct
transports (e.g. TCP, Named Pipes) are enabled, and that mixed mode
authentication is enabled.

Once you can connect to your database you won't need to worry about
"messaging patterns" or protocols.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"david" wrote:
Now we have some trouble to directly access to SQL Server database.

I would like to know if there is a special protocol in the communication
between SQL SERVER client and databse system. What is the messaging
pattern?

Thank you for any help.

David

May 16 '07 #3

P: n/a
"sloan" <sl***@ipass.netwrote in message
news:ea**************@TK2MSFTNGP02.phx.gbl...
To make sure you got a good connection string, you can try this object.
SqlConnectionStringBuilder

http://www.google.com/search?hl=en&q...r+&btnG=Search
I've never needed to look any further than here:
http://www.connectionstrings.com/
--
http://www.markrae.net

May 16 '07 #4

P: n/a

Neither have I.

But the object gives you all the "options" with intellisense for a newbie I
guess.
http://msdn2.microsoft.com/en-us/lib...r_members.aspx

Heck, there are a few listed there I didn't know existed.

"Mark Rae" <ma**@markNOSPAMrae.netwrote in message
news:uQ**************@TK2MSFTNGP04.phx.gbl...
"sloan" <sl***@ipass.netwrote in message
news:ea**************@TK2MSFTNGP02.phx.gbl...
To make sure you got a good connection string, you can try this object.
SqlConnectionStringBuilder
http://www.google.com/search?hl=en&q...r+&btnG=Search
>
I've never needed to look any further than here:
http://www.connectionstrings.com/
--
http://www.markrae.net

May 16 '07 #5

P: n/a
One more qustion is if the network administrator can block the direct access
message to database for security reason.

Thank for all of you.

I will try and read what you suggested to.

David

"sloan" wrote:
>
Neither have I.

But the object gives you all the "options" with intellisense for a newbie I
guess.
http://msdn2.microsoft.com/en-us/lib...r_members.aspx

Heck, there are a few listed there I didn't know existed.

"Mark Rae" <ma**@markNOSPAMrae.netwrote in message
news:uQ**************@TK2MSFTNGP04.phx.gbl...
"sloan" <sl***@ipass.netwrote in message
news:ea**************@TK2MSFTNGP02.phx.gbl...
To make sure you got a good connection string, you can try this object.
>
>
SqlConnectionStringBuilder
>
>
http://www.google.com/search?hl=en&q...r+&btnG=Search

I've never needed to look any further than here:
http://www.connectionstrings.com/
--
http://www.markrae.net


May 17 '07 #6

P: n/a
"david" <da***@discussions.microsoft.comwrote in message
news:7B**********************************@microsof t.com...
One more qustion is if the network administrator can block the direct
access
message to database for security reason.
Direct access *message*...???

A network administrator can certainly restrict what can and cannot connect
to SQL Server and/or the machine that it's running on...

--
http://www.markrae.net

May 17 '07 #7

P: n/a
Hi, Peter:

I have checked the the setting for SQL Server Properties. Where to find
"enable remote access" and what you described in the Enterprise Manager? But
we found the following:

1. Remote server connections: two options (seems for server to server)
1.1. Allow other SQL Servers to connect remotely to this SQL server using
RPC (Checked)
1.2. Enforce distributed transactions (MTS) (unchecked)

2. Security Authentication:
2.1. SQL Server and Windows (not selected): means using both SQL Server ID
and Windows ID
2.2. Windows only (selected): means using windows ID and password

David
"Peter Bromberg [C# MVP]" wrote:
There are really only two areas here:
1) getting the connection string right.
2) Ensuring that the SQL Server is enabled for remote access, the correct
transports (e.g. TCP, Named Pipes) are enabled, and that mixed mode
authentication is enabled.

Once you can connect to your database you won't need to worry about
"messaging patterns" or protocols.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"david" wrote:
Now we have some trouble to directly access to SQL Server database.

I would like to know if there is a special protocol in the communication
between SQL SERVER client and databse system. What is the messaging pattern?

Thank you for any help.

David
May 17 '07 #8

P: n/a

2. Security Authentication:
2.1. SQL Server and Windows (not selected): means using both SQL Server ID
and Windows ID
2.2. Windows only (selected): means using windows ID and password
This means you're using Window/NT authentication. Aka, permissions need to
be set up for

mycompany/jsmith (nt login) in order to connect.

I always setup using both. (which 2.1 is unchecked for you)

uid=jimmy;pwd=jimmypassword

If you see these in your connect string AND 2.1 is unchecked, it won't work.

Either select 2.1 or give
mycompany/jsmith the privs.

Also remember, if you're using Asp.Net, you won't "be" mycompany/jsmith
you'll be mymachine/AspNet (user account on the machine hosting IIS).

If you're doing a windows service, you'll probably be mymachine/SYSTEM


"david" <da***@discussions.microsoft.comwrote in message
news:B0**********************************@microsof t.com...
Hi, Peter:

I have checked the the setting for SQL Server Properties. Where to find
"enable remote access" and what you described in the Enterprise Manager?
But
we found the following:

1. Remote server connections: two options (seems for server to server)
1.1. Allow other SQL Servers to connect remotely to this SQL server using
RPC (Checked)
1.2. Enforce distributed transactions (MTS) (unchecked)

2. Security Authentication:
2.1. SQL Server and Windows (not selected): means using both SQL Server ID
and Windows ID
2.2. Windows only (selected): means using windows ID and password

David
"Peter Bromberg [C# MVP]" wrote:
There are really only two areas here:
1) getting the connection string right.
2) Ensuring that the SQL Server is enabled for remote access, the
correct
transports (e.g. TCP, Named Pipes) are enabled, and that mixed mode
authentication is enabled.

Once you can connect to your database you won't need to worry about
"messaging patterns" or protocols.
Peter

--
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net


"david" wrote:
Now we have some trouble to directly access to SQL Server database.
>
I would like to know if there is a special protocol in the
communication
between SQL SERVER client and databse system. What is the messaging
pattern?
>
Thank you for any help.
>
David

May 17 '07 #9

This discussion thread is closed

Replies have been disabled for this discussion.