Site: http://blogs.msdn.com/b/sql_protocols/ Link: http://blogs.msdn.com/sql_protocols/rss.xml
by dpblogs via SQL Protocols on 10/13/2011 5:50:00 PM
Greetings Developer community: We heard yesterday and today at the PASS conference about the exciting new areas that we are investing in bringing the power of SQL Server to our customers. Many of our developers who rely on native connectivity to SQL Server primarily use ODBC for their connectivity needs. We have been supporting ODBC as a part of the SQL Native Access Client (SNAC) libraries. In our continued commitment to interoperability, today we also announced that we will be releasing the M ...
[ read more ]
by SQL Server Connectivity via SQL Protocols on 10/29/2010 5:36:45 PM
Hello reader, We have extended our SQL Connectivity Customer Survey until November 2, 2010 5:00PM PST. If you have not done so please take a moment to fill our our easy 10 question survey listed below at the link to help shape the future of SQL Server. Thanks, SQL Connectivity Team Greetings to the SQL Server community : Last year in October 2009, we introduced the process of interacting on a regular basis with the developers and users in the form of surveys. During ...
by SQL Server Connectivity via SQL Protocols on 10/12/2010 4:38:07 PM
Greetings to the SQL Server community: Last year in October 2009, we introduced the process of interacting on a regular basis with the developers and users in the form of surveys. During the last 12 months, we completed surveys that focused on the broad SQL Connectivity components, including ODBC, ADO.NET, JDBC and PHP. These surveys provide us with an ability to validate some of the requests we have got from developers, users and partners such as you as well as ideas th ...
by SQL Protocols via SQL Protocols on 5/19/2010 6:20:00 AM
Several customers approached us asking what are the possible values for CurCmd in TDS DONE token. The TDS DONE token is defined at http://msdn.microsoft.com/en-us/library/dd340421(PROT.13).aspx. Similar rules apply to DONEPROC and DONEINPROC. In the TDS protocol, we have: CurCmd The token of the current command. The token value is provided and controlled by the application layer, which utilizes TDS. The TDS layer does not evaluate the value. As it says, we don’t put the possible value in ...
by SQL Protocols via SQL Protocols on 5/18/2010 6:40:00 AM
Microsoft SQL Server has a traceflag framework through which users can set specific server characteristics or to switch on/off a particular behavior. For details about how to use traceflags, please refer to http://msdn.microsoft.com/en-us/library/ms188396.aspx In this blog, I will introduce two useful traceflags related to TDS, -T4052/-T4055.-T4052 can be used to print the TDS packet sent to client (i.e. output) to console.-T4055 can be used to print the TDS packet received (i.e. input) to conso ...
by SQL Protocols via SQL Protocols on 4/2/2010 9:06:00 PM
Our colleagues over in the SQL Server Security team have developed an open tool for troubleshooting "Login Failure" errors. If you're having an issue with "Login Failure" errors and can't resolve it from the other SQL Protocols blog articles here, check out their blog post and give their tool a try: http://blogs.msdn.com/sqlsecurity/archive/2010/03/29/sql-server-authentication-troubleshooter.aspx Dan BenediktsonSQL Server Protocols Disclaimer: This posting is provided "AS IS" with no ...
by SQL Protocols via SQL Protocols on 10/19/2009 9:48:00 PM
Secure connection to SQL Server can be enforced by different ways, e.g. forcing encryption by using “ForceEncryption” property under the Network Configuration in the server. But this setting will force all clients to use encryption and any client that is not able to use an encrypted connection will fail. If you need to connect to SQL Server selectively here is how to achieve this: You can take advantage of the two client settings, “Force Protocol Encryption” and “Trust Server Certificate” and tw ...
by SQL Server Connectivity via SQL Protocols on 10/19/2009 9:48:00 PM
by dpblogs via SQL Protocols on 10/2/2009 10:41:00 PM
Dear SQL Server developers and users: It is this time of the year when we, in the SQL Connectivity product team, take a step back, review the priorities and goals for the long term and identify areas that will benefit from investments. We view you and your organization as a key stakeholder in this process and would like to gather your inputs in this survey, which should take no more than 5-10 minutes and a few other surveys that we will conduct in the next few months. The feedback ...
by SQL Protocols via SQL Protocols on 3/9/2009 8:11:00 PM
This error message, which is associated with the Winsock error WSAENOBUFS and actually comes from Windows rather than SQL Server directly, has two well-understood root causes. However, it still stumps people today, probably because there is no single source which explains both root causes and offers solutions for both. Here is a description of the two common situations where you may see this error and quick solutions for each: OS runs out of memory for TCP buffers When a powerful clie ...
by SQL Protocols via SQL Protocols on 11/6/2008 12:26:00 AM
Endpoint configuration seems to be creating some confusion. I hope that this will clarify some of the behavior as it applies to TCP endpoints. With a default configuration of SQL Server, try the following: > select name, port, is_dynamic_port, state from sys.tcp_endpoints> goname port is_dynamic_port state--------------------------- ---- ---------- ...
by SQL Protocols via SQL Protocols on 9/20/2008 1:06:00 AM
Lately we have noticed many misunderstandings surrounding the usage of the Data Source keyword in connection strings, caused by people generalizing from an example demonstrating a connection string for local connectivity and creating their own connection string for a remote connection. Here is one such example connection string for local connectivity as it would be used in VB.Net: Public con As New System.Data.SqlClient.SqlConnection("Integrated Security=SSPI;Initial Catalog=TestDatabase;D ...
by SQL Server Connectivity via SQL Protocols on 9/20/2008 1:06:00 AM
by SQL Server Connectivity via SQL Protocols on 8/29/2008 3:10:00 AM
Sometimes we are asked about the possibility of configuring SQL Server protocols through PowerShell. In SQL Server 2008, the sqlps tool incorporates WMI and SMO into this powerful Windows administrator tool, making it easy to manage SQL Server protocols through PowerShell. To get started, run (elevated, if on W ...
by SQL Protocols via SQL Protocols on 8/29/2008 3:10:00 AM
by SQL Protocols via SQL Protocols on 7/16/2008 12:20:00 AM
Some customers have reported connection failure because of wrong TDS version. The client application gets the following error message: (or similar depends on the protocol used) A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233) When you check the errorlog of your SQL Server, you see the fol ...
by SQL Protocols via SQL Protocols on 6/17/2008 5:49:00 AM
On a Windows Cluster it is possible to install a SQL Server Cluster, which will be a separate entity with disctinct Virtual Server Name, IP address, and pipe name. The nodes of the SQL Cluster must be able to communicate with one another. This communication may fail if the TCP port on which SQL Server is listening is not excepted from firewalls on the machines. This port can be found by using the Configuration Manager utility by viewing the properties of the TCP protocol or b ...
by SQL Protocols via SQL Protocols on 5/21/2008 1:34:00 AM
SQL Server 2008 contains a new feature designed to help troubleshoot particularly tricky connectivity problems. This new feature, the Connectivity Ring Buffer, captures a record for each server-initiated connection closure, including each kill of a session or Login Failed event. To facilitate efficient troubleshooting, the ring buffer attempts to provide information to correlate between the client failure and the server’s closing action. Up to 1k records in the ring buffer are persiste ...
by SQL Protocols via SQL Protocols on 5/3/2008 3:28:00 AM
Understanding the error message: “Login failed for user ''. The user is not associated with a trusted SQL Server connection.” This exact Login Failed error, with the empty string for the user name, has two unrelated classes of causes, one of which has already been blogged about here: http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx. In addition to an extra space in the connection string, the other class of causes for this error message is an inability to resolve the Windo ...
by SQL Protocols via SQL Protocols on 4/30/2008 9:53:00 AM
We have been seeing and trying to resolve SQL connectivity issue all the time. I guess it would be helpful if we can put some guidance on how to resolve connectivity issues. Here comes a proposal based on my experience. Basically, when you failed to connect to your SQL Server, the issue could be: 1) Network issue, 2) SQL Server configuration issue. 3) Firewall issue, 4) Client driver issue, 5) Application configuration issue. 6) Authentication and logon issue. Usually, custo ...
by SQL Protocols via SQL Protocols on 4/21/2008 12:46:00 AM
We see a couple of cases where customer could not connect to named instance on X64. They all have the following symptons. 1) Customer has no problem to connect X86 instance on the same server machine even if it's a named instance. Customer can even connect to some of the X64 named instance, but always see problem when connect to some specific named X64 instance. 2) SQL Server is confirmed up and running. The server is listening on TCP and/or NP protocols. 3) SQL Browser is confirmed in runn ...
by SQL Protocols via SQL Protocols on 4/8/2008 9:09:00 PM
Sporadic “Connection forcibly closed by remote host” errors with SQL Server connections can be very difficult to troubleshoot and resolve. This blog post is targeted at diagnosing TOE/Chimney issues that may lead to this client error message. Chimney is a feature introduced in the Windows Server 2003 Scalable Networking Pack, which was included in Windows Server 2003 SP2. Chimney increases network performance when using a network card which implements TOE, TCP/IP Offload Engine, which is a ...
by SQL Server Connectivity via SQL Protocols on 4/8/2008 9:09:00 PM
by SQL Protocols via SQL Protocols on 4/7/2008 8:16:00 AM
After installing SQL Server 2008, some users might notice that sqlbrowser.exe is installed under %ProgramFiles%Microsoft SQL Server\90\Shared, rather than %ProgramFiles%Microsoft SQL Server\100\Shared as some users expect. When setup fails for some reason, some user may think this is the culprit. As matter of fact, this is by design, not a bug. Some backgound here. SQL Server 2005 is also knowns as SQL Server 9 (code name Yukon), and SQL Server 2008 is also known as SQL Server 10 (code name Kat ...
by SQL Protocols via SQL Protocols on 4/3/2008 12:52:00 AM
Did you know that beginning with SQL Server 2008, support for service principal names (SPNs) has been extended to enable mutual authentication across all protocols. Administators can now define their own SPNs. Thus SQL Server 2008 makes secure authentication more manageable and reliable by allowing clients to directly specify the SPN to use. Fore more information, click here: http://msdn2.microsoft.com/en-us/library/cc280459(SQL.100).aspx ----Tres LondonSQL Server ProtocolsDisclaimer: This posti ...
by SQL Protocols via SQL Protocols on 7/19/2007 6:57:00 PM
In this post, I am trying to list out potential cause and general solution to this specific error when you are making connection to SQL Server 2005. First, It is due to TCP connection fail, since you can tell from the title, "TCP Provider: .xx", which indicates that either your connection string explicitly use 'tcp:" prefix, say "Server=tcp:<machinename> ...." or your client protocol setting ask for first try Named Pipe connection, if fails, then fallback to TCP co ...
by SQL Protocols via SQL Protocols on 6/30/2007 7:10:00 PM
This post focus on a typical cause of sql login failure issue described as the title. In real world, a customer log on to the machine as a domain\user or local machine accout, he can connec to SQL Server through SQL Server Management Studio. However, he fails to connect by using SQL Login, namely, in connection string specify User as the NT account, and the password. An example: He did: "Create login [domain\user] from windows", then try - osql -S -U [domain\user] -P xx or osql -S -U[machinea ...
by SQL Protocols via SQL Protocols on 6/30/2007 1:38:00 AM
When enabling channel encryption between the application and SQL Server, users may wonder what encryption algorithm is being used to protect their data. Unfortunately, this isn't an easy question to answer and here's why. SQL Server (both 2005 and 2000) leverages the SChannel layer (the SSL/TLS layer provided by Windows) for facilitating encryption. Furthermore, SQL Server will completely rely upon SChannel to determine the best encryption cipher suite to use. Inciden ...
by SQL Protocols via SQL Protocols on 5/16/2007 9:46:00 AM
This error message is the most frequent error message when connecting to SQL Server. You see this error message when you use SqlClient. In SNAC, the error message is slightly differently as follows: C:\>osql -E -Syourserver[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [xxx].[SQL Native Client]Login timeout expired Basically, this error message just tell you that the client cannot make a connection to the server. It's equvalent to "SQL Server does not exist ...
by SQL Protocols via SQL Protocols on 5/14/2007 1:28:00 AM
Users often see this error message when connection to a SQL Server and don't know where to start to solve the problem. In most forums, people says this is because remote connection is not enabled on the server. This is not exactly correct. Actually, this error message give customers very specific information and the solution is quite simple. First of all, you get this error message only if you are trying to connect to a SQL Server named instance. For default instance, you never see this. Why? B ...
The content of the postings is owned by the respective author. SQL Feeds is not responsible for the contents of the postings. This site is automatically generated and cannot be reviewed for abusive content. If you find abusive content on SQL Feeds, please contact us. Designated trademarks and brands are the property of their respective owners. All rights reserved.
