Post reply

ODBC Data source administration

  • June 17, 2007 at 8:50 pm

    #174686

    Hi,

    i have installed sql server2005 in my home pc. trying to do the ODBC settings but it is giving me a error

     

    connection failed

    SQLState:010000

    sql server error2

    [microsoft] [ODBC SQL SERVER DRIVER] [Shared memory] connection open (connect())

    connection failed

    sqlstate:08001

    sql server error: 17

    [microsoft][ODBC SQL Server Driver][Shared memory] sql server does not exist

    or access denied.

    what should i do to solve this problem : pls suggest

    i have tried using sql server auth and windows authe but still cannot work.

     

    thanks

  • June 18, 2007 at 12:42 am

    #713495

    http://support.microsoft.com/default.aspx?kbid=328306

     

  • June 18, 2007 at 1:43 am

    #713501

    Enable shared memory through SQL Configuration Area Manager. Then you should be able to connect to the SQL Server using ODBC.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • June 18, 2007 at 4:54 am

    #713522

    mr sugesh,

    i have checked the configuration but the shared memory is already enabled.

    anyother solution pls

     

    thanks

  • June 18, 2007 at 5:33 am

    #713526

    Microsoft SQL Server ODBC Driver Version 03.85.1022

    Data Source Name: SQLS

    Data Source Description:

    Server: ROMI

    Database: (Default)

    Language: (Default)

    Translate Character Data: Yes

    Log Long Running Queries: No

    Log Driver Statistics: No

    Use Integrated Security: Yes

    Use Regional Settings: No

    Prepared Statements Option: Do not create temporary procedures

    Use Failover Server: No

    Use ANSI Quoted Identifiers: Yes

    Use ANSI Null, Paddings and Warnings: Yes

    Data Encryption: No

     

    this is the test datascript  . is anything wrong. still i cannot find the solution

  • June 18, 2007 at 5:48 am

    #713529

    Use client network utility to specify that you always go with TCP connections. Then try connecting to the database using the TCP connection instead of shared memory. Check if error reoccurs.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • June 18, 2007 at 6:55 pm

    #713696

    yes i can connect now. just want to confirm few things.

    i can see two data source in the odbc data source administration

    when should i choose SQL NATIVE CLIENT and when should i choose

    SQL Server and what is the difference and purpose of them.

    thankyou very much

  • June 18, 2007 at 10:21 pm

    #713714

    SQL NATIVE CLIENT comes out with support from SQL 2005 and has better performance than the OLEDB provider for SQL Server.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • June 19, 2007 at 2:20 am

    #713749

    thanks

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply