Showing posts with label via. Show all posts
Showing posts with label via. Show all posts

Sunday, March 25, 2012

Connection pooling in MSSQL via VB

Hi folks,
Is there a way to implement connection pooling in MSSQL 7 or 2k when accessing it from VB?
Thanks.Yes, if you implement the VB data consuming object as a MTS COM object (COM DLL). MTS is already integrated in COM+ with w2k.

Originally posted by lokem
Hi folks,

Is there a way to implement connection pooling in MSSQL 7 or 2k when accessing it from VB?

Thanks.|||If you use ADO via ODBC, and you:

1. enable connection pooling in ODBC control panel
2. make sure you Close() your connection and set it to nothing when you've finished using it

...then you've got connection pooling. I think the closed connection objects hang around for a default of 60 seconds.|||Originally posted by dbadelphes
Yes, if you implement the VB data consuming object as a MTS COM object (COM DLL). MTS is already integrated in COM+ with w2k.

So I just have to get it registered to Component Services for a computer and I'm set? Do I need to do anything special when defining the connection string?

mwilkes: Thanks for the tip. Will be trying that out!|||To make Coonection Pooling work you also need to make sure that you use the same connection string all the time. In the past developers used the same UID, PWD, DATABASE and SERVER in the connection string but would change ApplicationName by setting it to a UserID so they could distinguish connections via IIS. This would end up creating a seperate connection.

connection pooling for access jet connected ODBC tables?

Is 'connection pooling' available when using an access front end connecting
to sql server 2000 tables via jet connected ODBC (not an access
project/ado)?
If yes, is there any configurable options? if yes where? On client side or
server side or both?
any help is appreciated. Thanks.
You can configure ODBC connection properties in an Access mdb in
several places -- database options, query options, and in an ODBC
connection string (or DSN). However, I'm not sure about
resource/connection pooling. Access handles a lot of that under the
covers, spawning additonal connections when needed, say for opening a
complex form. What exactly are you trying to dos?
--Mary
On Mon, 24 May 2004 16:37:11 -0400, "djc" <noone@.nowhere.com> wrote:

>Is 'connection pooling' available when using an access front end connecting
>to sql server 2000 tables via jet connected ODBC (not an access
>project/ado)?
>If yes, is there any configurable options? if yes where? On client side or
>server side or both?
>any help is appreciated. Thanks.
>
sqlsql

connection pooling for access jet connected ODBC tables?

Is 'connection pooling' available when using an access front end connecting
to sql server 2000 tables via jet connected ODBC (not an access
project/ado)?
If yes, is there any configurable options? if yes where? On client side or
server side or both?
any help is appreciated. Thanks.You can configure ODBC connection properties in an Access mdb in
several places -- database options, query options, and in an ODBC
connection string (or DSN). However, I'm not sure about
resource/connection pooling. Access handles a lot of that under the
covers, spawning additonal connections when needed, say for opening a
complex form. What exactly are you trying to dos?
--Mary
On Mon, 24 May 2004 16:37:11 -0400, "djc" <noone@.nowhere.com> wrote:

>Is 'connection pooling' available when using an access front end connecting
>to sql server 2000 tables via jet connected ODBC (not an access
>project/ado)?
>If yes, is there any configurable options? if yes where? On client side or
>server side or both?
>any help is appreciated. Thanks.
>

Thursday, March 22, 2012

connection pooling

is connection pooling something that can be used after moving tables from
mdb file to sql server 2000 and just relinking the tables via ODBC in the
front end file? Or is this something that must be setup in code?Connection pooling is on by default. It's typically used if you make and
break connections with the same connection string parameters. A web server
is a primary candidate for it's use.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sqlsql

connection pooling

is connection pooling something that can be used after moving tables from
mdb file to sql server 2000 and just relinking the tables via ODBC in the
front end file? Or is this something that must be setup in code?
Connection pooling is on by default. It's typically used if you make and
break connections with the same connection string parameters. A web server
is a primary candidate for it's use.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Tuesday, March 20, 2012

connection or user limitation

Customers connect to my server via ISAP DLL. The dll makes a connection to sql server. I may have 20 or 30 or 40 customers connecting to my server via the ISAPI dll. I am trying to understand whether MSDE is enough for my application or do I need the ente
rprise SQL server. I want to understand the limitation on MSDE, it is 5 concurrent users or 5 concurrent connections and there is a difference because the ISAPI dll uses the same user login. Actually, the is one user connecting to SQL server via DLL, but
multiple copies of the dll can be loaded and each copy makes its own database connection.
> it is 5 concurrent users or 5 concurrent connections
Neither, it is 5 concurrent workloads.
You can have 40 or 100 connections and not trigger the governor, until so
much work is attempted by so many users *at the same time.* Remember that a
lot of the time that a connection stays open, it is idle, so it not pushing
the workload limit.
Please read:
http://msdn.microsoft.com/library/en...r_sa2_0ciq.asp
http://www.aspfaq.com/
(Reverse address to reply.)

connection of sql server via vba

Help !!

I have a sql server database that is as follows

SERVER: AFG
Database Name : APF
Authentication: Windows authentication

how do I create the connectionstring via vba to access this database?sydney (mr.vinay.gupta@.gmail.com) writes:

Quote:

Originally Posted by

I have a sql server database that is as follows
>
SERVER: AFG
Database Name : APF
Authentication: Windows authentication
>
how do I create the connectionstring via vba to access this database?


"Provider=SQLOLEDB;Server=AFG;Inital Catalog=APF;Trusted_connection=yes"

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||sydney wrote:

Quote:

Originally Posted by

Help !!
>
I have a sql server database that is as follows
>
SERVER: AFG
Database Name : APF
Authentication: Windows authentication
>
how do I create the connectionstring via vba to access this database?


www.connectionstrings.com

Sunday, March 11, 2012

connection history to SQL server?

Is there any way to see in Enterprise Manager a history of
connections (also via Enterprise Manager) to a db? I'm
trying to track down connections to our db that were done
by a consultant remotely through Enterprise Manager via
the Internet. The consultant had direct access and didn't
need to log onto our domain.
Thanks.Not unless you had SQL login auditing set to All or are auditing security
events on the server, in which case you should be able to see logons in the
NT Security event log
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Brian" <anonymous@.discussions.microsoft.com> wrote in message
news:09f301c3b372$868347a0$a001280a@.phx.gbl...
Is there any way to see in Enterprise Manager a history of
connections (also via Enterprise Manager) to a db? I'm
trying to track down connections to our db that were done
by a consultant remotely through Enterprise Manager via
the Internet. The consultant had direct access and didn't
need to log onto our domain.
Thanks.|||OK, so if I have SQL login auditing set to All where would
I see the events? In the server event log or somewhere in
Enterprise Manager?
>--Original Message--
>Not unless you had SQL login auditing set to All or are
auditing security
>events on the server, in which case you should be able to
see logons in the
>NT Security event log
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>Is there any way to see in Enterprise Manager a history of
>connections (also via Enterprise Manager) to a db? I'm
>trying to track down connections to our db that were done
>by a consultant remotely through Enterprise Manager via
>the Internet. The consultant had direct access and didn't
>need to log onto our domain.
>Thanks.
>
>.
>|||In the SQL Error log (In Enterprise Manager this will be in the Management
subfolder for a server)
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Brian" <anonymous@.discussions.microsoft.com> wrote in message
news:660601c3b377$eb660e00$a601280a@.phx.gbl...
OK, so if I have SQL login auditing set to All where would
I see the events? In the server event log or somewhere in
Enterprise Manager?
>--Original Message--
>Not unless you had SQL login auditing set to All or are
auditing security
>events on the server, in which case you should be able to
see logons in the
>NT Security event log
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>Is there any way to see in Enterprise Manager a history of
>connections (also via Enterprise Manager) to a db? I'm
>trying to track down connections to our db that were done
>by a consultant remotely through Enterprise Manager via
>the Internet. The consultant had direct access and didn't
>need to log onto our domain.
>Thanks.
>
>.
>|||Jasper,
Thanks for your responses. It didn't help me out, but I
had SQL login auditing set to Success (not All). When I
changed it to Success, I get this in the error
log "Configuration option 'show advanced options' changed
from 1 to 1. Run the RECONFIGURE statement to install..",
so I'm thinking something else is going on I have to
resolve.
I still need to catch our consultant connecting to the
server without first checking with us (which they are
supposed to do).
Brian
>--Original Message--
>In the SQL Error log (In Enterprise Manager this will be
in the Management
>subfolder for a server)
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:660601c3b377$eb660e00$a601280a@.phx.gbl...
>OK, so if I have SQL login auditing set to All where would
>I see the events? In the server event log or somewhere in
>Enterprise Manager?
>>--Original Message--
>>Not unless you had SQL login auditing set to All or are
>auditing security
>>events on the server, in which case you should be able to
>see logons in the
>>NT Security event log
>>--
>>HTH
>>Jasper Smith (SQL Server MVP)
>>I support PASS - the definitive, global
>>community for SQL Server professionals -
>>http://www.sqlpass.org
>>"Brian" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>>Is there any way to see in Enterprise Manager a history
of
>>connections (also via Enterprise Manager) to a db? I'm
>>trying to track down connections to our db that were done
>>by a consultant remotely through Enterprise Manager via
>>the Internet. The consultant had direct access and
didn't
>>need to log onto our domain.
>>Thanks.
>>
>>.
>
>.
>|||Yes, I should have mentioned, it's one of the options that requires a SQL
Service restart (don't know how practical that is for you). Another option
would be to use a server side trace capturing the audit login and logout
events. If they have a specific login, you can filter on that also.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:122401c3b37a$6ed460a0$a501280a@.phx.gbl...
Jasper,
Thanks for your responses. It didn't help me out, but I
had SQL login auditing set to Success (not All). When I
changed it to Success, I get this in the error
log "Configuration option 'show advanced options' changed
from 1 to 1. Run the RECONFIGURE statement to install..",
so I'm thinking something else is going on I have to
resolve.
I still need to catch our consultant connecting to the
server without first checking with us (which they are
supposed to do).
Brian
>--Original Message--
>In the SQL Error log (In Enterprise Manager this will be
in the Management
>subfolder for a server)
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"Brian" <anonymous@.discussions.microsoft.com> wrote in
message
>news:660601c3b377$eb660e00$a601280a@.phx.gbl...
>OK, so if I have SQL login auditing set to All where would
>I see the events? In the server event log or somewhere in
>Enterprise Manager?
>>--Original Message--
>>Not unless you had SQL login auditing set to All or are
>auditing security
>>events on the server, in which case you should be able to
>see logons in the
>>NT Security event log
>>--
>>HTH
>>Jasper Smith (SQL Server MVP)
>>I support PASS - the definitive, global
>>community for SQL Server professionals -
>>http://www.sqlpass.org
>>"Brian" <anonymous@.discussions.microsoft.com> wrote in
>message
>>news:09f301c3b372$868347a0$a001280a@.phx.gbl...
>>Is there any way to see in Enterprise Manager a history
of
>>connections (also via Enterprise Manager) to a db? I'm
>>trying to track down connections to our db that were done
>>by a consultant remotely through Enterprise Manager via
>>the Internet. The consultant had direct access and
didn't
>>need to log onto our domain.
>>Thanks.
>>
>>.
>
>.
>

Thursday, March 8, 2012

Connection failure with VIA/GigaNet Protocol

I'm trying to determine if this error
(http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
rather difficult to scroll through the dozens of numbers looking for one
specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
searchable?Hi Ron
I think this was fixed in build 990 which is included in SP4
http://support.microsoft.com/kb/890200/EN-US/
John
"Ron Hinds" wrote:
> I'm trying to determine if this error
> (http://support.microsoft.com/kb/811274/en-us) has been fixed in SQL2000 SP4
> or the SP4 cumulative hotfix. I can't find it listed on MSDN, but it's
> rather difficult to scroll through the dozens of numbers looking for one
> specific fix. Note to Microsoft: Why don't you make the fixed KB numbers
> searchable?
>
>

connection failed from client application

Hi ,
the client application used is ms access via odbc to sql server 2000 std
edition sp3a
sometimes the user just get the following error :
1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
generate SSPI context
2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
generate SSPI context
does anyone knows wat's the cause and how to resolve
if need to reinstall the odbc , how can i do that ?
tks & rdgs
Hi
You may want to check out
http://support.microsoft.com/kb/811889/
http://support.microsoft.com/default...b;en-us;267588
http://support.microsoft.com/default...b;en-us;814401
John
"maxzsim" wrote:

> Hi ,
> the client application used is ms access via odbc to sql server 2000 std
> edition sp3a
> sometimes the user just get the following error :
> 1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
> generate SSPI context
> 2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
> generate SSPI context
> does anyone knows wat's the cause and how to resolve
> if need to reinstall the odbc , how can i do that ?
> tks & rdgs
>

connection failed from client application

Hi ,
the client application used is ms access via odbc to sql server 2000 std
edition sp3a
sometimes the user just get the following error :
1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
generate SSPI context
2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
generate SSPI context
does anyone knows wat's the cause and how to resolve
if need to reinstall the odbc , how can i do that ?
tks & rdgsHi
You may want to check out
http://support.microsoft.com/kb/811889/
http://support.microsoft.com/defaul...kb;en-us;267588
http://support.microsoft.com/defaul...kb;en-us;814401
John
"maxzsim" wrote:

> Hi ,
> the client application used is ms access via odbc to sql server 2000 std
> edition sp3a
> sometimes the user just get the following error :
> 1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
> generate SSPI context
> 2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
> generate SSPI context
> does anyone knows wat's the cause and how to resolve
> if need to reinstall the odbc , how can i do that ?
> tks & rdgs
>

connection failed from client application

Hi ,
the client application used is ms access via odbc to sql server 2000 std
edition sp3a
sometimes the user just get the following error :
1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
generate SSPI context
2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
generate SSPI context
does anyone knows wat's the cause and how to resolve
if need to reinstall the odbc , how can i do that ?
tks & rdgsHi
You may want to check out
http://support.microsoft.com/kb/811889/
http://support.microsoft.com/default.aspx?scid=kb;en-us;267588
http://support.microsoft.com/default.aspx?scid=kb;en-us;814401
John
"maxzsim" wrote:
> Hi ,
> the client application used is ms access via odbc to sql server 2000 std
> edition sp3a
> sometimes the user just get the following error :
> 1 - Connection failed , SQL state : S1000 , SQL Server Error : 0 Cannot
> generate SSPI context
> 2 - Connection failed , SQL state : HY000 , SQL Server Error : 0 Cannot
> generate SSPI context
> does anyone knows wat's the cause and how to resolve
> if need to reinstall the odbc , how can i do that ?
> tks & rdgs
>

Friday, February 24, 2012

Connection broken

We have added a new firewall to our network and now I keep getting my
connection dropped when running from home. Port 1433 is open.
I am connecting via a VPN and it was working fine. Nothing has changed in
this respect. If I disconnect my Firewall at home and go to the internet
directly, I have no problems (but this firewall worked fine before and does
now sporadically).
Now, however, I can connect fine but my queries give me the following
message after about 30 seconds:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
This says I was connected, but now the Connection is broken.
If I were to give it an invalid command such as "who_is", I do get the
following results:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'who_is'.
This comes directly from Sql Server, so I know the my machine at home can
talk to the Server fine.
Why am I not able to query without losing connection?
Thanks,
Tom
I found out what is happening, but not why.
Apparently, Sql Server using UDP service 17 port 1434 for something.
I looked at my firewall settings and it is dropping my packets because they
are fragmented. It was confusing at first, because it worked fine without
the firewall. But what must be happening is that the data is being passed
on 1433 (which I would expect) and since there is no firewall to strip bad
packets it lets the fragmented packet through. For some reason, because of
this packet the connection is dropped (not sure what constitutes a dropped
connection) so I assume the actual response hasn't been sent yet and now it
can't send it because the connection is now gone (I think).
Anyone know why this is happening or what this port (1434) is used for? I
knew about 1433, but this is the first I had heard about 1434.
Thanks,
Tom
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
> We have added a new firewall to our network and now I keep getting my
> connection dropped when running from home. Port 1433 is open.
> I am connecting via a VPN and it was working fine. Nothing has changed in
> this respect. If I disconnect my Firewall at home and go to the internet
> directly, I have no problems (but this firewall worked fine before and
> does now sporadically).
> Now, however, I can connect fine but my queries give me the following
> message after about 30 seconds:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> This says I was connected, but now the Connection is broken.
> If I were to give it an invalid command such as "who_is", I do get the
> following results:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'who_is'.
> This comes directly from Sql Server, so I know the my machine at home can
> talk to the Server fine.
> Why am I not able to query without losing connection?
> Thanks,
> Tom
>
|||UDP 1434 is the SQL Server Resolution Service used to find
what port number a named instance is listening on.
You can find more information in the following articles:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
How to use static and dynamic port allocation in SQL Server
2000
http://support.microsoft.com/?id=823938
-Sue
On Fri, 10 Mar 2006 08:41:32 -0800, "tshad"
<tscheiderich@.ftsolutions.com> wrote:

>I found out what is happening, but not why.
>Apparently, Sql Server using UDP service 17 port 1434 for something.
>I looked at my firewall settings and it is dropping my packets because they
>are fragmented. It was confusing at first, because it worked fine without
>the firewall. But what must be happening is that the data is being passed
>on 1433 (which I would expect) and since there is no firewall to strip bad
>packets it lets the fragmented packet through. For some reason, because of
>this packet the connection is dropped (not sure what constitutes a dropped
>connection) so I assume the actual response hasn't been sent yet and now it
>can't send it because the connection is now gone (I think).
>Anyone know why this is happening or what this port (1434) is used for? I
>knew about 1433, but this is the first I had heard about 1434.
>Thanks,
>Tom
>"tshad" <tscheiderich@.ftsolutions.com> wrote in message
>news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
>

Connection broken

We have added a new firewall to our network and now I keep getting my
connection dropped when running from home. Port 1433 is open.
I am connecting via a VPN and it was working fine. Nothing has changed in
this respect. If I disconnect my Firewall at home and go to the internet
directly, I have no problems (but this firewall worked fine before and does
now sporadically).
Now, however, I can connect fine but my queries give me the following
message after about 30 seconds:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForD
ata
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
This says I was connected, but now the Connection is broken.
If I were to give it an invalid command such as "who_is", I do get the
following results:
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'who_is'.
This comes directly from Sql Server, so I know the my machine at home can
talk to the Server fine.
Why am I not able to query without losing connection?
Thanks,
TomI found out what is happening, but not why.
Apparently, Sql Server using UDP service 17 port 1434 for something.
I looked at my firewall settings and it is dropping my packets because they
are fragmented. It was confusing at first, because it worked fine without
the firewall. But what must be happening is that the data is being passed
on 1433 (which I would expect) and since there is no firewall to strip bad
packets it lets the fragmented packet through. For some reason, because of
this packet the connection is dropped (not sure what constitutes a dropped
connection) so I assume the actual response hasn't been sent yet and now it
can't send it because the connection is now gone (I think).
Anyone know why this is happening or what this port (1434) is used for? I
knew about 1433, but this is the first I had heard about 1434.
Thanks,
Tom
"tshad" <tscheiderich@.ftsolutions.com> wrote in message
news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
> We have added a new firewall to our network and now I keep getting my
> connection dropped when running from home. Port 1433 is open.
> I am connecting via a VPN and it was working fine. Nothing has changed in
> this respect. If I disconnect my Firewall at home and go to the internet
> directly, I have no problems (but this firewall worked fine before and
> does now sporadically).
> Now, however, I can connect fine but my queries give me the following
> message after about 30 seconds:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckFo
rData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> This says I was connected, but now the Connection is broken.
> If I were to give it an invalid command such as "who_is", I do get the
> following results:
> Server: Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'who_is'.
> This comes directly from Sql Server, so I know the my machine at home can
> talk to the Server fine.
> Why am I not able to query without losing connection?
> Thanks,
> Tom
>|||UDP 1434 is the SQL Server Resolution Service used to find
what port number a named instance is listening on.
You can find more information in the following articles:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
How to use static and dynamic port allocation in SQL Server
2000
http://support.microsoft.com/?id=823938
-Sue
On Fri, 10 Mar 2006 08:41:32 -0800, "tshad"
<tscheiderich@.ftsolutions.com> wrote:

>I found out what is happening, but not why.
>Apparently, Sql Server using UDP service 17 port 1434 for something.
>I looked at my firewall settings and it is dropping my packets because they
>are fragmented. It was confusing at first, because it worked fine without
>the firewall. But what must be happening is that the data is being passed
>on 1433 (which I would expect) and since there is no firewall to strip bad
>packets it lets the fragmented packet through. For some reason, because of
>this packet the connection is dropped (not sure what constitutes a dropped
>connection) so I assume the actual response hasn't been sent yet and now it
>can't send it because the connection is now gone (I think).
>Anyone know why this is happening or what this port (1434) is used for? I
>knew about 1433, but this is the first I had heard about 1434.
>Thanks,
>Tom
>"tshad" <tscheiderich@.ftsolutions.com> wrote in message
>news:ewYccw6QGHA.5808@.TK2MSFTNGP12.phx.gbl...
>

Sunday, February 19, 2012

connection between VB.net and SQL

I would like to use VB2005.Net (Express) connect to MSSQL2005 (Express), how can I do it?

I can complete the development via local database (with "attach" method in connection string). I try the remote connection via client machine with string ("Data Source=w2000-vm1\SQLEXPRESS;Initial Catalog=ABC;Integrated Security=SSPI;Connect Timeout=30;User Instance=True") and it was still pop up error shown below (using web deployment for the client machine). But I can do the same with Excel VBA sucessful.

Error Message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Data.SqlClient.SqlException: User do not have right。
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at TestDeploy.DatabaseTestDataSetTableAdapters.PhoneBookTableAdapter.Fill(PhoneBookDataTable dataTable)
at TestDeploy.Form1.Form1_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
------------
TestDeploy
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/ronald/Local%20Settings/Apps/2.0/M3JA8MR1.OCE/AGDRJ61O.XTD/test..tion_84bdc91a3f310404_0001.0000_f95a0c6d7be6e97f/TestDeploy.exe
------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
------------
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINNT/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Thanks for your kind helpConfused


ronaldp:

System.Data.SqlClient.SqlException: User do not have right。

That looks to me like it is a permissions issue.

In your connection string you are using Integrated Authentication which means you will be connecting to the database under the user account that IIS assigns to the worker process.

You can check this account in IIS, the directory security tab of your virtual directory.

You need to make sure this user account is a valid login for your sql database.

Friday, February 17, 2012

Connecting via VPN

Your machine and the customer's are not in the same domain so Windows
authentication won't work because there's no way to authenticate the user on
your machine. SQL Auth should work unless there's something else blocking
the TCP/IP connection. It might help to know what error you're getting and
if there is an error in the server error log. Running EM remotely is
actually the best solution in this case.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Middletree" <middletree@.hottttttttmail.com> wrote in message
news:OitGvBWlGHA.4772@.TK2MSFTNGP04.phx.gbl...
> One my company's customers has allowed me to connect to their network via
> VPN. Overall, it seems to work fine. I can remote in, or map drives, etc.
> However, I have been unable to use my SQL2000 Enterprise manager to
> connect to their database. I can remote into the machine where that
> database resides and open up EM there, but I can't do it from EM on my
> machine. That is, I'm getting a 'logon failed' error, regardless of
> whether or not I am using Windows or SQL authentication.
> I did some digging, and found that ports 1433 and 1434 need to be open for
> this to happen. However, the customer has stated that he isn't blocking
> off these ports.
> Anyone know of any issues with doing this over VPN?
>One my company's customers has allowed me to connect to their network via
VPN. Overall, it seems to work fine. I can remote in, or map drives, etc.
However, I have been unable to use my SQL2000 Enterprise manager to connect
to their database. I can remote into the machine where that database resides
and open up EM there, but I can't do it from EM on my machine. That is, I'm
getting a 'logon failed' error, regardless of whether or not I am using
Windows or SQL authentication.
I did some digging, and found that ports 1433 and 1434 need to be open for
this to happen. However, the customer has stated that he isn't blocking off
these ports.
Anyone know of any issues with doing this over VPN?|||Your machine and the customer's are not in the same domain so Windows
authentication won't work because there's no way to authenticate the user on
your machine. SQL Auth should work unless there's something else blocking
the TCP/IP connection. It might help to know what error you're getting and
if there is an error in the server error log. Running EM remotely is
actually the best solution in this case.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Middletree" <middletree@.hottttttttmail.com> wrote in message
news:OitGvBWlGHA.4772@.TK2MSFTNGP04.phx.gbl...
> One my company's customers has allowed me to connect to their network via
> VPN. Overall, it seems to work fine. I can remote in, or map drives, etc.
> However, I have been unable to use my SQL2000 Enterprise manager to
> connect to their database. I can remote into the machine where that
> database resides and open up EM there, but I can't do it from EM on my
> machine. That is, I'm getting a 'logon failed' error, regardless of
> whether or not I am using Windows or SQL authentication.
> I did some digging, and found that ports 1433 and 1434 need to be open for
> this to happen. However, the customer has stated that he isn't blocking
> off these ports.
> Anyone know of any issues with doing this over VPN?
>|||[vbcol=seagreen]
And your local firewall (if any)?
Try to connect with telnet on port 1433 and/or osql or sqlcmd with the
"tcp:"-prefix.
More infor here
http://blogs.msdn.com/sql_protocols.../22/483684.aspx
And the remote connection is not always the best solution - perhaps the
local machine is a development-station for test and debugging - porting
changes is a whole lot easier with local access...
/ola|||[vbcol=seagreen]
And your local firewall (if any)?
Try to connect with telnet on port 1433 and/or osql or sqlcmd with the
"tcp:"-prefix.
More infor here
http://blogs.msdn.com/sql_protocols.../22/483684.aspx
And the remote connection is not always the best solution - perhaps the
local machine is a development-station for test and debugging - porting
changes is a whole lot easier with local access...
/ola

Connecting via Radio Link

Could somebody tell me as to what configuration changes has to be made in the SQL Server 2000, if I want to connect to a table in the database using Internet options, i.e., I have the SQL Server running on a machine which uses a real IP address, and I want to connect to it (SQL Server)using DSN from another location. In the 2nd location, I use internet using dialup/DSL/Cable Broadband.

--
The following error is shown, when I try to connect to the SQL Server using SQL Server authentication using login ID and password:

Connection failed:
SQL State:'01000'
SQL Server Error: 10060
[Microsoft][OBDC SQL Server Driver][TCP/IP Sockets]ConnectionOpen[Connect()]
Connection failed:
SQL State:'08001'
SQL Server Error: 17
[Microsoft][OBDC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
-----

Thanxs in advance to anyone who can help me solve the problem.You can use the Client Network Utility.

Go To Client Network Utility. Go to Alias Tab.
Click on ADD. Provide a Alias Name, and the Server IP address or the URL as Server Name under the Connection Parameters Section. (Netowrk Libraries can be Named Pipes)

Thats it. When you go to Enterprise Manager, you can register that server by its Alias name.

Connecting via ODBC to SQLServer 2005 June CTP using MARS

Hello newsgroup,
after searching around the web, some reading and testing I'm still having
problems using MARS via ODBC with the SQLServer2005 June CTP.
I'm trying to enable MARS by connection string, after some looking about
"MARS_Connection=yes" should be the setting. That right?
I found different settings for OLEDB and ADO.NET I don't know why three
different strings are needed instead of one for all.
Anyway, it's not working and I'm getting the "connection is already full
with data from another result" message. I'm using the old odbc client for
SQLServer 2000, is that the problem?
I'd really like to use SQLServer in future, but I need MARS because else the
application would need some restructuring and that's too expensive. Currently
I'm working with two other DBMS and they work fine when it come to this
feature.
Thanks for help,
florian
Hi Florian,
Inorder for MARS to work you will need to use the new SQL Native Client; The
ODBC client for SQLServer 2000 does not support MARS.
ADO.NET, OLEDB and ODBC have different connection strings for MARS inorder
to preserve the naming conventions for connectino attributes bettween the
different providers.
Prior versions will get the 'connection busy' errors if you try to use
implicit multiple connections in and ODBC application.
Chris Lee has written an excellent blog about this here: It describes
migrating from MDAC to the SQL Native Client (very easy) and also about
using MARS
http://blogs.msdn.com/dataaccess/arc...gory/9952.aspx
There's a great technet article here as well
http://www.microsoft.com/technet/pro...marssql05.mspx
Brad Sarsfield [MSFT] bradsa(at)microsoft.com
This posting is provided "AS IS", with no warranties, and confers no rights.
"Florian B." <Florian B.@.discussions.microsoft.com> wrote in message
news:E4A95505-E345-45FF-A9AC-FFAD3E9E6ACF@.microsoft.com...
> Hello newsgroup,
> after searching around the web, some reading and testing I'm still having
> problems using MARS via ODBC with the SQLServer2005 June CTP.
> I'm trying to enable MARS by connection string, after some looking about
> "MARS_Connection=yes" should be the setting. That right?
> I found different settings for OLEDB and ADO.NET I don't know why three
> different strings are needed instead of one for all.
> Anyway, it's not working and I'm getting the "connection is already full
> with data from another result" message. I'm using the old odbc client for
> SQLServer 2000, is that the problem?
> I'd really like to use SQLServer in future, but I need MARS because else
> the
> application would need some restructuring and that's too expensive.
> Currently
> I'm working with two other DBMS and they work fine when it come to this
> feature.
> Thanks for help,
> florian

Connecting via ODBC to SQLServer 2005 June CTP using MARS

Hello newsgroup,
after searching around the web, some reading and testing I'm still having
problems using MARS via ODBC with the SQLServer2005 June CTP.
I'm trying to enable MARS by connection string, after some looking about
"MARS_Connection=yes" should be the setting. That right?
I found different settings for OLEDB and ADO.NET I don't know why three
different strings are needed instead of one for all.
Anyway, it's not working and I'm getting the "connection is already full
with data from another result" message. I'm using the old odbc client for
SQLServer 2000, is that the problem?
I'd really like to use SQLServer in future, but I need MARS because else the
application would need some restructuring and that's too expensive. Currentl
y
I'm working with two other DBMS and they work fine when it come to this
feature.
Thanks for help,
florianHi Florian,
Inorder for MARS to work you will need to use the new SQL Native Client; The
ODBC client for SQLServer 2000 does not support MARS.
ADO.NET, OLEDB and ODBC have different connection strings for MARS inorder
to preserve the naming conventions for connectino attributes bettween the
different providers.
Prior versions will get the 'connection busy' errors if you try to use
implicit multiple connections in and ODBC application.
Chris Lee has written an excellent blog about this here: It describes
migrating from MDAC to the SQL Native Client (very easy) and also about
using MARS
http://blogs.msdn.com/dataaccess/ar...egory/9952.aspx
There's a great technet article here as well
http://www.microsoft.com/technet/pr.../marssql05.mspx
Brad Sarsfield [MSFT] bradsa(at)microsoft.com
This posting is provided "AS IS", with no warranties, and confers no rights.
"Florian B." <Florian B.@.discussions.microsoft.com> wrote in message
news:E4A95505-E345-45FF-A9AC-FFAD3E9E6ACF@.microsoft.com...
> Hello newsgroup,
> after searching around the web, some reading and testing I'm still having
> problems using MARS via ODBC with the SQLServer2005 June CTP.
> I'm trying to enable MARS by connection string, after some looking about
> "MARS_Connection=yes" should be the setting. That right?
> I found different settings for OLEDB and ADO.NET I don't know why three
> different strings are needed instead of one for all.
> Anyway, it's not working and I'm getting the "connection is already full
> with data from another result" message. I'm using the old odbc client for
> SQLServer 2000, is that the problem?
> I'd really like to use SQLServer in future, but I need MARS because else
> the
> application would need some restructuring and that's too expensive.
> Currently
> I'm working with two other DBMS and they work fine when it come to this
> feature.
> Thanks for help,
> florian

Connecting via ODBC

Hi all,
Hope you can help, I am trying to link to some data tables into Access via
the ODBC connection. It worked for me before but i have had issues with my PC
and now i get this message:
[INTERSOLV][ODBC SQL Server driver]Communication link failure.[INTERSOLV]
[ODBC SQL Server driver][SQL Server]ct_connect(): directory service layer:
internal directory control layer error: Requested server name not found.
I suspect this will be a hard question to answer but I'd appreciate any input.
Cheers
Dave
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
This is a pretty general error. It could be caused by your network, or by
SQL Server settings. You didn't say how long ago it worked. Yesterday, or
last year? If yesterday you may have changed something. If last year, it
could be lots of things.
You didn't say what version you are using. If SQL Server 2005, check out the
connectivity tutorial which was designed to help users with just this
problem. http://msdn2.microsoft.com/en-us/library/ms345318.aspx
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Suttd via droptable.com" <u25367@.uwe> wrote in message
news:7e0eab8790a4c@.uwe...
> Hi all,
> Hope you can help, I am trying to link to some data tables into Access via
> the ODBC connection. It worked for me before but i have had issues with my
> PC
> and now i get this message:
> [INTERSOLV][ODBC SQL Server driver]Communication link failure.[INTERSOLV]
> [ODBC SQL Server driver][SQL Server]ct_connect(): directory service layer:
> internal directory control layer error: Requested server name not found.
> I suspect this will be a hard question to answer but I'd appreciate any
> input.
>
> Cheers
> Dave
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
>
|||Hi,
Thanks for your reply, I was using it last week, my PC burnt out and I
replaced it and used my old hard drive as a slave so I could have all my old
applications etc. I am using "Sybase System10" as my Driver? My knowledge
is quite limited in this area sorry if I am missing something silly here.
Regards
Dave
Rick Byham, (MSFT) wrote:[vbcol=seagreen]
>This is a pretty general error. It could be caused by your network, or by
>SQL Server settings. You didn't say how long ago it worked. Yesterday, or
>last year? If yesterday you may have changed something. If last year, it
>could be lots of things.
>You didn't say what version you are using. If SQL Server 2005, check out the
>connectivity tutorial which was designed to help users with just this
>problem. http://msdn2.microsoft.com/en-us/library/ms345318.aspx
>[quoted text clipped - 13 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
|||What version of SQL Server are trying to connect to?
Is SQL Server on the same computer or a different computer?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Suttd via droptable.com" <u25367@.uwe> wrote in message
news:7e34deec0e23c@.uwe...

> Hi,
> Thanks for your reply, I was using it last week, my PC burnt out and I
> replaced it and used my old hard drive as a slave so I could have all my
> old
> applications etc. I am using "Sybase System10" as my Driver? My
> knowledge
> is quite limited in this area sorry if I am missing something silly here.
> Regards
> Dave
>
> Rick Byham, (MSFT) wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
>