sql server odbc:
You need to enable Remote Connections using the SQL Server
Surface Area Configuration tool. Open the tool, go to the
Server node in the tool, go to Database Engine and from
there you will see the option for Remote Connections.
-Sue
On Wed, 23 Aug 2006 13:02:59 -0400, "Jan K. van Dalen"
[quoted text, click to view] <vandjATmarkross.com> wrote:
>Hi Everyone,
>
>Ok, I'm pretty new to SQL Server. I installed SQL Server 2005 Express with
>extended option.
>
>I'm able to connect to it using Management Studio Express I was able to
>create a new DB and create a login user "demo" with password "demo". Gave
>full access to the new db.
>
>Now I want to connect to the db using the odbc connector. I have tried both
>the SQL Server and the SQL Native Client with same results.
>
>FYI, TCP/IP is enable for the internal ip address (127.0.0.1). Also, I made
>sure that the Server Default property for remote connection is on. Also, I
>setup for dual authentication.
>
>When I create the ODBC entry, I'm able to select the server and when trying
>to authenticate I have tried both, NT Authentication and entering a
>user/password.
>
>Both are denied. One of the errors says that I don't have Remote connection
>on. Other times (depending on authentication method) just says that SQL
>Server does not exist or access denied.
>
>I have also tried using user "SA" but no luck.
>
>Any ideas?
>
>Thanks in advance !!!
>
Hi Everyone,
Ok, I'm pretty new to SQL Server. I installed SQL Server 2005 Express with
extended option.
I'm able to connect to it using Management Studio Express I was able to
create a new DB and create a login user "demo" with password "demo". Gave
full access to the new db.
Now I want to connect to the db using the odbc connector. I have tried both
the SQL Server and the SQL Native Client with same results.
FYI, TCP/IP is enable for the internal ip address (127.0.0.1). Also, I made
sure that the Server Default property for remote connection is on. Also, I
setup for dual authentication.
When I create the ODBC entry, I'm able to select the server and when trying
to authenticate I have tried both, NT Authentication and entering a
user/password.
Both are denied. One of the errors says that I don't have Remote connection
on. Other times (depending on authentication method) just says that SQL
Server does not exist or access denied.
I have also tried using user "SA" but no luck.
Any ideas?
Thanks in advance !!!
That depends on the app and if it's an upgrade, etc. The
following article in books online outlines when to chose
what:
When to Use SQL Native Client
http://msdn2.microsoft.com/en-us/library/ms130828.aspx -Sue
On Wed, 23 Aug 2006 14:54:34 -0400, "Jan K. van Dalen"
[quoted text, click to view] <vandjATmarkross.com> wrote:
>Sue ... got it working ... thanks.
>
>Now, should I use the SQL Server odbc or the SQL Native Client?
>
>The db will be access by IIS/ASP.Net application.
>
>"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
>news:p65pe2tmg0m63n8m6htinurm7u0hfb51rl@4ax.com...
>> You need to enable Remote Connections using the SQL Server
>> Surface Area Configuration tool. Open the tool, go to the
>> Server node in the tool, go to Database Engine and from
>> there you will see the option for Remote Connections.
>>
>> -Sue
>>
>> On Wed, 23 Aug 2006 13:02:59 -0400, "Jan K. van Dalen"
>> <vandjATmarkross.com> wrote:
>>
>>>Hi Everyone,
>>>
>>>Ok, I'm pretty new to SQL Server. I installed SQL Server 2005 Express
>>>with
>>>extended option.
>>>
>>>I'm able to connect to it using Management Studio Express I was able to
>>>create a new DB and create a login user "demo" with password "demo". Gave
>>>full access to the new db.
>>>
>>>Now I want to connect to the db using the odbc connector. I have tried
>>>both
>>>the SQL Server and the SQL Native Client with same results.
>>>
>>>FYI, TCP/IP is enable for the internal ip address (127.0.0.1). Also, I
>>>made
>>>sure that the Server Default property for remote connection is on. Also,
>>>I
>>>setup for dual authentication.
>>>
>>>When I create the ODBC entry, I'm able to select the server and when
>>>trying
>>>to authenticate I have tried both, NT Authentication and entering a
>>>user/password.
>>>
>>>Both are denied. One of the errors says that I don't have Remote
>>>connection
>>>on. Other times (depending on authentication method) just says that SQL
>>>Server does not exist or access denied.
>>>
>>>I have also tried using user "SA" but no luck.
>>>
>>>Any ideas?
>>>
>>>Thanks in advance !!!
>>>
>>
>
Sue ... got it working ... thanks.
Now, should I use the SQL Server odbc or the SQL Native Client?
The db will be access by IIS/ASP.Net application.
[quoted text, click to view] "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
news:p65pe2tmg0m63n8m6htinurm7u0hfb51rl@4ax.com...
> You need to enable Remote Connections using the SQL Server
> Surface Area Configuration tool. Open the tool, go to the
> Server node in the tool, go to Database Engine and from
> there you will see the option for Remote Connections.
>
> -Sue
>
> On Wed, 23 Aug 2006 13:02:59 -0400, "Jan K. van Dalen"
> <vandjATmarkross.com> wrote:
>
>>Hi Everyone,
>>
>>Ok, I'm pretty new to SQL Server. I installed SQL Server 2005 Express
>>with
>>extended option.
>>
>>I'm able to connect to it using Management Studio Express I was able to
>>create a new DB and create a login user "demo" with password "demo". Gave
>>full access to the new db.
>>
>>Now I want to connect to the db using the odbc connector. I have tried
>>both
>>the SQL Server and the SQL Native Client with same results.
>>
>>FYI, TCP/IP is enable for the internal ip address (127.0.0.1). Also, I
>>made
>>sure that the Server Default property for remote connection is on. Also,
>>I
>>setup for dual authentication.
>>
>>When I create the ODBC entry, I'm able to select the server and when
>>trying
>>to authenticate I have tried both, NT Authentication and entering a
>>user/password.
>>
>>Both are denied. One of the errors says that I don't have Remote
>>connection
>>on. Other times (depending on authentication method) just says that SQL
>>Server does not exist or access denied.
>>
>>I have also tried using user "SA" but no luck.
>>
>>Any ideas?
>>
>>Thanks in advance !!!
>>
>
Don't see what you're looking for? Try a search.
