다음을 통해 공유

SQL Server Native Client survey

  • 아티클

Dear SQL Server developers and users:

Our sister team, the SQL Server Native Client (SNAC), has a survey open to ask for your feedback as they take a step back to review the priorities and goals for the long term and identify areas that will benefit from investments.

As a whole, 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. The feedback you provide is very valuable and be rest assured that each and every response will be read and will provide the background for some of the key decisions that we will make that will benefit our SQL Server database application developer community.

This survey will be open for your submissions until January 31, 2010 and can be found here.

 

SQL Server Protocols Team.

Comments

  • Anonymous
    January 18, 2010
    win xp micro soft sqlserver2005 cannt connect to data base (DBNETLIB connectionopen

  • Anonymous
    January 27, 2010
    I am using Window Server 2003 and Services Pack . I am trying to connect to SQL Server 2005. I am runing Crystal Report template. I set up ODBC connection which worked. I am also using ASPX.Net. But when I ran the application throught the web url I get the error below: Logon failed. Details: 01000:[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (PreLoginHandshake()).Query Engine Error: '08001:[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.'Logon failed.Error in File C:WINDOWSTEMPCouncilDistrict {869B8D1E-1FF4-49D6-8F82-853B0C214AD1}.rpt: Unable to connect: incorrect log on parameters.

  • Anonymous
    February 03, 2010
    The comment has been removed

  • Anonymous
    February 17, 2010
    Hi, I want to connect to Crystal Reports either by Integration Security or by SQL server authentication with SQLServer Native Client. My question is what are the prerequisites in the client computer to be able to connect through Native Client?

  • Anonymous
    February 17, 2010
    The comment has been removed

  • Anonymous
    March 10, 2010
    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

  • Anonymous
    March 15, 2010
    Using windows 7 and cannot use the event log.  It is unavailable because the WMI data provider does not recognize instance name.  Please help.