I use "SQL Server 2000 Driver for JDBC SP3" to connect SQLServer2000 under
Tomcat App server.
I wish to control the number of physical connections made to the database to
50. Can somebody guide me about this.
At the moment even with as low as 30 concurrent hits we see a very high
number of phyiscal connection to the database as high as 200.
I am using the following settings in SERVER.XML
<Resource name="jdbc/ECTDB" auth="Container"
type="com.microsoft.jdbcx.sqlserver.SQLServerDataS ource"/>
<ResourceParams name="jdbc/ECTDB">
<parameter><name>maxActive</name><value>30</value></parameter>
<parameter><name>maxIdle</name><value>20</value></parameter>
<parameter><name>maxWait</name><value>10000</value></parameter>
<parameter><name>factory</name><value>com.microsoft.jdbcx.sqlserver.SQLServe rDataSourceFactory</value></parameter>
<parameter><name>driverClassName</name><value>com.microsoft.jdbcx.sqlserver.SQLServe rDataSource</value></parameter>
<parameter><name>user</name><value>..</value></parameter>
<parameter><name>password</name><value>..</value></parameter>
<parameter><name>driverName</name><value>SQLServer</value></parameter>
<parameter><name>serverName</name><value>127.0.0.1</value></parameter>
<parameter><name>portNumber</name><value>1433</value></parameter>
<parameter><name>databaseName</name><value>..</value></parameter>
<parameter><name>selectMethod</name><value>cursor</value></parameter>
<parameter><name>loginTimeout</name><value>60</value></parameter>
</ResourceParams>
Thanks a lot
| Thread-Topic: connection pool problem using in Tomcat
| thread-index: AcSMuy5kABS/93PSRZ6MtRi1273r1w==
| X-WBNR-Posting-Host: 202.134.106.86
| From: "=?Utf-8?B?a2FpY2FsbA==?=" <kaicall@.discussions.microsoft.com>
| Subject: connection pool problem using in Tomcat
| Date: Fri, 27 Aug 2004 21:55:03 -0700
| Lines: 30
| Message-ID: <22AD57F5-91A6-48C5-81BF-F9B84365D03F@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6282
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I use "SQL Server 2000 Driver for JDBC SP3" to connect SQLServer2000
under
| Tomcat App server.
|
| I wish to control the number of physical connections made to the database
to
| 50. Can somebody guide me about this.
|
| At the moment even with as low as 30 concurrent hits we see a very high
| number of phyiscal connection to the database as high as 200.
| I am using the following settings in SERVER.XML
| <Resource name="jdbc/ECTDB" auth="Container"
| type="com.microsoft.jdbcx.sqlserver.SQLServerDataS ource"/>
| <ResourceParams name="jdbc/ECTDB">
| <parameter><name>maxActive</name><value>30</value></parameter>
| <parameter><name>maxIdle</name><value>20</value></parameter>
| <parameter><name>maxWait</name><value>10000</value></parameter>
<parameter><name>factory</name><value>com.microsoft.jdbcx.sqlserver.SQLServe
rDataSourceFactory</value></parameter>
<parameter><name>driverClassName</name><value>com.microsoft.jdbcx.sqlserver.
SQLServerDataSource</value></parameter>
| <parameter><name>user</name><value>..</value></parameter>
| <parameter><name>password</name><value>..</value></parameter>
| <parameter><name>driverName</name><value>SQLServer</value></parameter>
| <parameter><name>serverName</name><value>127.0.0.1</value></parameter>
| <parameter><name>portNumber</name><value>1433</value></parameter>
| <parameter><name>databaseName</name><value>..</value></parameter>
| <parameter><name>selectMethod</name><value>cursor</value></parameter>
| <parameter><name>loginTimeout</name><value>60</value></parameter>
| </ResourceParams>
|
|
| Thanks a lot
|
|
If you are using SelectMethod=direct, then it is possible that you are
seeing an increase in connections due to the creation of cloned
connections. These additional connections are necessary because each
statement requires its own connection. Your Tomcat settings have no
bearing on this particular behavior, as it is inherent in the JDBC driver
itself.
Are you using transactions in your code? Can you provide code that
reproduces the problem behavior?
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
|||Carb Simien ,
Yes, I use connection in my code and use a following function for getting
conncection.
public static Connection getConnection() throws Exception {
Connection dbConnection = null;
InitialContext ctx = new InitialContext();
Context envCtx = (Context) ctx.lookup("java:comp/env");
ConnectionPoolDataSource ds =
(ConnectionPoolDataSource) envCtx.lookup("jdbc/ECTDB");
Connection conn = ds.getPooledConnection().getConnection();
conn.setAutoCommit(false);
return conn;
}
Is this funciton cause the problem?
Thanks a lot.
kaicall
""Carb Simien [MSFT]"" wrote:
> --
> | Thread-Topic: connection pool problem using in Tomcat
> | thread-index: AcSMuy5kABS/93PSRZ6MtRi1273r1w==
> | X-WBNR-Posting-Host: 202.134.106.86
> | From: "=?Utf-8?B?a2FpY2FsbA==?=" <kaicall@.discussions.microsoft.com>
> | Subject: connection pool problem using in Tomcat
> | Date: Fri, 27 Aug 2004 21:55:03 -0700
> | Lines: 30
> | Message-ID: <22AD57F5-91A6-48C5-81BF-F9B84365D03F@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.jdbcdriver
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> | Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6282
> | X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
> |
> | I use "SQL Server 2000 Driver for JDBC SP3" to connect SQLServer2000
> under
> | Tomcat App server.
> |
> | I wish to control the number of physical connections made to the database
> to
> | 50. Can somebody guide me about this.
> |
> | At the moment even with as low as 30 concurrent hits we see a very high
> | number of phyiscal connection to the database as high as 200.
> | I am using the following settings in SERVER.XML
> | <Resource name="jdbc/ECTDB" auth="Container"
> | type="com.microsoft.jdbcx.sqlserver.SQLServerDataS ource"/>
> | <ResourceParams name="jdbc/ECTDB">
> | <parameter><name>maxActive</name><value>30</value></parameter>
> | <parameter><name>maxIdle</name><value>20</value></parameter>
> | <parameter><name>maxWait</name><value>10000</value></parameter>
> <parameter><name>factory</name><value>com.microsoft.jdbcx.sqlserver.SQLServe
> rDataSourceFactory</value></parameter>
> <parameter><name>driverClassName</name><value>com.microsoft.jdbcx.sqlserver.
> SQLServerDataSource</value></parameter>
> | <parameter><name>user</name><value>..</value></parameter>
> | <parameter><name>password</name><value>..</value></parameter>
> | <parameter><name>driverName</name><value>SQLServer</value></parameter>
> | <parameter><name>serverName</name><value>127.0.0.1</value></parameter>
> | <parameter><name>portNumber</name><value>1433</value></parameter>
> | <parameter><name>databaseName</name><value>..</value></parameter>
> | <parameter><name>selectMethod</name><value>cursor</value></parameter>
> | <parameter><name>loginTimeout</name><value>60</value></parameter>
> | </ResourceParams>
> |
> |
> | Thanks a lot
> |
> |
> If you are using SelectMethod=direct, then it is possible that you are
> seeing an increase in connections due to the creation of cloned
> connections. These additional connections are necessary because each
> statement requires its own connection. Your Tomcat settings have no
> bearing on this particular behavior, as it is inherent in the JDBC driver
> itself.
> Are you using transactions in your code? Can you provide code that
> reproduces the problem behavior?
> Carb Simien, MCSE MCDBA MCAD
> Microsoft Developer Support - Web Data
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
>
|||CarbinoS@.online.microsoft.com ("Carb Simien [MSFT]") wrote in message news:<zzuzMF7jEHA.2516@.cpmsftngxa10.phx.gbl>...
> If you are using SelectMethod=direct, then it is possible that you are
> seeing an increase in connections due to the creation of cloned
> connections. These additional connections are necessary because each
> statement requires its own connection. Your Tomcat settings have no
> bearing on this particular behavior, as it is inherent in the JDBC driver
> itself.
> Are you using transactions in your code? Can you provide code that
> reproduces the problem behavior?
> Carb Simien, MCSE MCDBA MCAD
> Microsoft Developer Support - Web Data
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
This is a little scary isn't it? If I have a J2EE app that starts out
pre-preparing (for subsequent re-use) N prepared statements per
connection and I have M concurrent clients using the app then we'll
require N*M physical database connections. Is that correct? That
number could be pretty huge for even a mid size app..
Is there any plans to address this in any future driver?
Grant M
|||grantmitchell7@.yahoo.com wrote:
> CarbinoS@.online.microsoft.com ("Carb Simien [MSFT]") wrote in message news:<zzuzMF7jEHA.2516@.cpmsftngxa10.phx.gbl>...
>
> This is a little scary isn't it? If I have a J2EE app that starts out
> pre-preparing (for subsequent re-use) N prepared statements per
> connection and I have M concurrent clients using the app then we'll
> require N*M physical database connections. Is that correct? That
> number could be pretty huge for even a mid size app..
Not to mention if you plan to do anything transactionally, or use temp tables,
which would be limited to one real connection, and not involve all the
under-the-covers connections involved in one logical connection.
I am confident that an upcoming version of the free MS driver will
address this. In the mean time you have the option of using commercial
drivers, or ensuring you run with selectMethod=cursor. As I recall, the
original poster actually already showed he was running with selectMethod=cursor...
Joe Weinstein at BEA
> Is there any plans to address this in any future driver?
> Grant M
|||Joe Weinstein <joeNOSPAM@.bea.com> wrote in message news:<4136035E.9000108@.bea.com>...[vbcol=seagreen]
> grantmitchell7@.yahoo.com wrote:
>
> Not to mention if you plan to do anything transactionally, or use temp tables,
> which would be limited to one real connection, and not involve all the
> under-the-covers connections involved in one logical connection.
> I am confident that an upcoming version of the free MS driver will
> address this. In the mean time you have the option of using commercial
> drivers, or ensuring you run with selectMethod=cursor. As I recall, the
> original poster actually already showed he was running with selectMethod=cursor...
> Joe Weinstein at BEA
Yes the transactional problem is alarming.. Does the driver transact
all the cloned connections for statement when the original connection
is transacted? Who knows but I suppose a test would be relativly
quick.
In regards to selectMethod=cursor - our tests show that result sets
generated with server side cursors can be up to 8 times more expensive
on the database (and slower) than forward only, 'client side' result
sets (depending on the characteristics of the cursor). So instead of
having N*M connections we might end up with N*M server side cursors.
I'm not sure which is worse..
Therefore I would argue that server cursor based result sets are a
major obstacle to scalability and should be avoided at all costs
(except possibly for singleton processes that need a table snapshot
like a report for example).
I hope you are right that an upcoming release resolves this although I
remain skeptical since my guesss is that changing this behavior would
mean a major structural change in the driver's architecture.
On this newsgroup there has been recent reference by Microsoft to a
"new" JDBC driver for SQL 2005. However when I tried to get more
details on this driver there was no response. Perhaps someone from
Microsoft could comment on the "new" driver, and specifically comment
on whether it resolve this serious issue..
Grant
Showing posts with label driver. Show all posts
Showing posts with label driver. Show all posts
Thursday, March 22, 2012
Connection Pool and MSSql driver
Hi all,
I'm trying to build an application using MSSQL Server and Connection pool.
At my server.xml file I have:
<Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
<Resource name="jdbc/StrutsDemoDS" auth="Container"
type="javax.sql.DataSource" scope="Shareable"/>
<ResourceParams name="jdbc/StrutsDemoDS">
<parameter>
<name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
<parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
<parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value>passwd</value></parameter>
<parameter><name>maxActive</name><value>20</value></parameter>
<parameter><name>maxIdle</name><value>10</value></parameter>
<parameter><name>maxWait</name><value>100</value></parameter>
</ResourceParams>
</Context>
In my class, I have:
protected static DataSource dataSource;
protected Connection getConnection() throws SQLException {
InitialContext ic = new InitialContext();
dataSource = (DataSource)
ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
Connection conn = null;
try {
conn = dataSource.getConnection(); // The error happens at this
line
}
catch (SQLException e) {
throw e;
}
return conn;
}
I can't get successful my connection. Can anyone tell me why?
Thanks.
Lorena
Lorena,
What is the error you're getting? Are you sure the lookup is successful?
If you write a simple class that doesn't use jndi but instead uses
DriverManager, Connection, and the normal db access stuff, with the
connectstring you're passing, can you connect?
Marc
"Lorena" <Lorena@.discussions.microsoft.com> wrote in message
news:E2508C07-F91E-40C2-BF64-34B7E8C23F58@.microsoft.com...
> Hi all,
> I'm trying to build an application using MSSQL Server and Connection pool.
> At my server.xml file I have:
> <Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
> <Resource name="jdbc/StrutsDemoDS" auth="Container"
> type="javax.sql.DataSource" scope="Shareable"/>
> <ResourceParams name="jdbc/StrutsDemoDS">
> <parameter>
> <name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
> <parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
> <parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
> <parameter><name>username</name><value>sa</value></parameter>
> <parameter><name>password</name><value>passwd</value></parameter>
> <parameter><name>maxActive</name><value>20</value></parameter>
> <parameter><name>maxIdle</name><value>10</value></parameter>
> <parameter><name>maxWait</name><value>100</value></parameter>
> </ResourceParams>
> </Context>
> In my class, I have:
> protected static DataSource dataSource;
> protected Connection getConnection() throws SQLException {
> InitialContext ic = new InitialContext();
> dataSource = (DataSource)
> ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
> Connection conn = null;
> try {
> conn = dataSource.getConnection(); // The error happens at
> this
> line
> }
> catch (SQLException e) {
> throw e;
> }
> return conn;
> }
> I can't get successful my connection. Can anyone tell me why?
> Thanks.
> Lorena
I'm trying to build an application using MSSQL Server and Connection pool.
At my server.xml file I have:
<Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
<Resource name="jdbc/StrutsDemoDS" auth="Container"
type="javax.sql.DataSource" scope="Shareable"/>
<ResourceParams name="jdbc/StrutsDemoDS">
<parameter>
<name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
<parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
<parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
<parameter><name>username</name><value>sa</value></parameter>
<parameter><name>password</name><value>passwd</value></parameter>
<parameter><name>maxActive</name><value>20</value></parameter>
<parameter><name>maxIdle</name><value>10</value></parameter>
<parameter><name>maxWait</name><value>100</value></parameter>
</ResourceParams>
</Context>
In my class, I have:
protected static DataSource dataSource;
protected Connection getConnection() throws SQLException {
InitialContext ic = new InitialContext();
dataSource = (DataSource)
ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
Connection conn = null;
try {
conn = dataSource.getConnection(); // The error happens at this
line
}
catch (SQLException e) {
throw e;
}
return conn;
}
I can't get successful my connection. Can anyone tell me why?
Thanks.
Lorena
Lorena,
What is the error you're getting? Are you sure the lookup is successful?
If you write a simple class that doesn't use jndi but instead uses
DriverManager, Connection, and the normal db access stuff, with the
connectstring you're passing, can you connect?
Marc
"Lorena" <Lorena@.discussions.microsoft.com> wrote in message
news:E2508C07-F91E-40C2-BF64-34B7E8C23F58@.microsoft.com...
> Hi all,
> I'm trying to build an application using MSSQL Server and Connection pool.
> At my server.xml file I have:
> <Context path="/sample" docBase="C:/myprojects/sample" reloadable="true" >
> <Resource name="jdbc/StrutsDemoDS" auth="Container"
> type="javax.sql.DataSource" scope="Shareable"/>
> <ResourceParams name="jdbc/StrutsDemoDS">
> <parameter>
> <name>factory</name><value>org.apache.commons.dbcp.BasicDataSourc eFactory</value></parameter>
> <parameter><name>driverClassName</name><value>com.microsoft.jdbc.sqlserver.SQLServer Driver</value></parameter>
> <parameter><name>url</name><value>jdbc:microsoft:sqlserver://myserver:1433</value></parameter>
> <parameter><name>username</name><value>sa</value></parameter>
> <parameter><name>password</name><value>passwd</value></parameter>
> <parameter><name>maxActive</name><value>20</value></parameter>
> <parameter><name>maxIdle</name><value>10</value></parameter>
> <parameter><name>maxWait</name><value>100</value></parameter>
> </ResourceParams>
> </Context>
> In my class, I have:
> protected static DataSource dataSource;
> protected Connection getConnection() throws SQLException {
> InitialContext ic = new InitialContext();
> dataSource = (DataSource)
> ic.lookup("java:comp/env/jdbc/StrutsDemoDS");
> Connection conn = null;
> try {
> conn = dataSource.getConnection(); // The error happens at
> this
> line
> }
> catch (SQLException e) {
> throw e;
> }
> return conn;
> }
> I can't get successful my connection. Can anyone tell me why?
> Thanks.
> Lorena
Sunday, March 11, 2012
Connection is busy with results for another hstmt
HI guys,
I'm using ODBC driver from WinXP SP2 with SQL Server 2005 Express (on my machine for test) and SQL Server 2005 Standard (on the production machine).
With SQL Server 2005 Express I've no problem, but with SQL Server 2005 Standard, in some query, I get "Connection is busy with results for another hstmt".
I'm working with VisualStudio 2003 with standard CDatabase and CRecordSet MFC classes.
I looked for an advice in the Microsoft KB but I found only Service Pack for SQL Server 2000 !
Everything could be useful !
Thanks a lot!
Bye, Domenico
You can avoid this error message by switching to the SQL Server 2005 ODBC driver, 'SQL Native Client' and enabling the MARS (Multiple Active Result Sets feature). There is more information in Books Online and also here http://blogs.msdn.com/dataaccess/archive/2005/08/02/446894.aspx
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Connection is busy with results for another command
We are migrating our databases from MS Access to SQL Server 2005 and using the SQL Native Client ODBC driver.
We also use a reporting tool called Actuate. Some of our Actuate reports use multiple datastreams to build the report.
When I run an Actuate report having multiple datastreams I get the following error message from SQL Server:
Error generated by the connected data source. Connection is busy with results for another command.
Is there a configuration setting in SQL Server to enable processing of multiple result sets?
Thanks.
sqlserver can handle thousands of connections. The error reported sounds like your application error/limitation. I suggest you take a look at the application configuration (i.e. connection or command method).
|||Thanks, oj.I think what's happening is that Actuate is attempting to execute multiple queries simultaneously against the same db connection. The error I'm getting looks to be an ODBC error generated from SQL Server.|||
It's typically the data access provider (odbc, .net, etc.) that the application uses that throws the error. For example, you cannot execute another sqlcommand on the same connection that is being used/processed by a sqldatareader.
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqldatareader.aspx
|||SQL Server introduced MARS which allows multiactive resultssets. have a look in the BOL and see have you can enabled it within your conenctionstring at www.connectionstrings.com
Jens K Suessmeyer
http://www.sqlserver2005.de
Connection from SQL 2005 to Informix 2000
Hi All,
I'm trying to set up a SSIS package to pull data from a data sourse on an Informix 2000 server. I'm currently using an OpenLink driver to access the data through ODBC, however when I try to query it through BIDS or using the SQL management Studio's import feature it says that the objects don't exist for what I'm querying.. I can view the tables in the query builder, just not query them?
Has anyone any suggestions as to how I might be able to resolve this? The Informix server is not one that I can modify, so anything that I do will have to be done from the SQL server (running 2005 ent edition)
I'm able to query the tables and fields from another program, however can't output the results from this easily for SQL to use.
If you have any suggestions I'd greatly appreciate them. Let me know if you need any more information
Regards,
Steve
PS, I'm using SQL 2005 Ent Ed, OpenLink Multi Tier ODBC Version 4.2, Informix 2000 connected via TCP/IP, and have a username and password to connect (not a trusted connection)
Hallo,
I have the same Problem.
I think the problem is the sql-syntax.
SQL2005 generate this query: select * from [tablename]
informix need this: select * from tablename
bye
hardy
|||Hey Steve,
I have the exact same error. Has anyone found the answer?
Mrlace2
Connection from SQL 2005 to Informix 2000
Hi All,
I'm trying to set up a SSIS package to pull data from a data sourse on an Informix 2000 server. I'm currently using an OpenLink driver to access the data through ODBC, however when I try to query it through BIDS or using the SQL management Studio's import feature it says that the objects don't exist for what I'm querying.. I can view the tables in the query builder, just not query them?
Has anyone any suggestions as to how I might be able to resolve this? The Informix server is not one that I can modify, so anything that I do will have to be done from the SQL server (running 2005 ent edition)
I'm able to query the tables and fields from another program, however can't output the results from this easily for SQL to use.
If you have any suggestions I'd greatly appreciate them. Let me know if you need any more information
Regards,
Steve
PS, I'm using SQL 2005 Ent Ed, OpenLink Multi Tier ODBC Version 4.2, Informix 2000 connected via TCP/IP, and have a username and password to connect (not a trusted connection)
Hallo,
I have the same Problem.
I think the problem is the sql-syntax.
SQL2005 generate this query: select * from [tablename]
informix need this: select * from tablename
bye
hardy
|||Hey Steve,
I have the exact same error. Has anyone found the answer?
Mrlace2
Connection for the ADO RecordSet
Hi! All,
I have an old ado application like following:
pCadoCon = new CADOConnection;
pCadoCon->Open (_T"driver={...A OEM driver...}; UID=..;PWD=....", _T (""), _T (""));
//some OEM driver unlocking code
pCadors = new CADORs;
pCadors->Open (_T"select foo from bar", pCadoCon->m_lpDispatch, eCursor); //SQL: a select statement here
The CADOConnection and CADORs are ADO connection, RecordSet wrapper classes created with ClassWizard.
I successfully open an ADO connection using the OEM driver by this DSN less way, and then passed it to ADO Recordset. From ODBC trace, I found that under the cover of the ADO, this connection is used to execute the select statement, but after that it automatically opens an other connection. I do not know why and is it possible to disable this?
I suspect it's opening another connection to provide a back channel to post updates to a scrollable, updatable rowset. Can it be disabled? Ah, sure. Open a ROFO Recordset.
Wednesday, March 7, 2012
Connection Error using SQL Server ODBC
Hi, I'm trying to connect to an SQL Server using an ODBC driver, typed in the
Machine name, but it won't let me connect.
Where the wizard asks me what the server name is that I want to connect to,
the drop down is empty. I thought it should show me a list of servers to
choose from?
Also, if I try to type in the machine name, and connect, it gives me an
error that it either could not connect or I am unauthorized even though I
know I'm using the administrators login and password.
I'm sooooooo confused. Am I even using the right ODBC driver? It's [SQL
Server], and they tell me the database is SQL Servcer v.8...
Any ideas?
THANKS!!
In the ODBC set up there are several ways to connect...
When setting it up you need to make sure that you click on client
configuraiton and choose a connection that your SQL Server allows. TCP/IP is
pretty typical on port 1433. Then you must make sure that your SQL server
allows connections using TCP/IP using your client configuration tools.
You also want to check simple things like making sure you can ping the
server (if your firewall allows it) to make sure that you can resolve your
server using DNS...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"KRISTEN" <KRISTEN@.discussions.microsoft.com> wrote in message
news:B76386D1-75FB-4673-AC9B-FF501DB58D87@.microsoft.com...
> Hi, I'm trying to connect to an SQL Server using an ODBC driver, typed in
> the
> Machine name, but it won't let me connect.
> Where the wizard asks me what the server name is that I want to connect
> to,
> the drop down is empty. I thought it should show me a list of servers to
> choose from?
> Also, if I try to type in the machine name, and connect, it gives me an
> error that it either could not connect or I am unauthorized even though I
> know I'm using the administrators login and password.
> I'm sooooooo confused. Am I even using the right ODBC driver? It's [SQL
> Server], and they tell me the database is SQL Servcer v.8...
> Any ideas?
> THANKS!!
Machine name, but it won't let me connect.
Where the wizard asks me what the server name is that I want to connect to,
the drop down is empty. I thought it should show me a list of servers to
choose from?
Also, if I try to type in the machine name, and connect, it gives me an
error that it either could not connect or I am unauthorized even though I
know I'm using the administrators login and password.
I'm sooooooo confused. Am I even using the right ODBC driver? It's [SQL
Server], and they tell me the database is SQL Servcer v.8...
Any ideas?
THANKS!!
In the ODBC set up there are several ways to connect...
When setting it up you need to make sure that you click on client
configuraiton and choose a connection that your SQL Server allows. TCP/IP is
pretty typical on port 1433. Then you must make sure that your SQL server
allows connections using TCP/IP using your client configuration tools.
You also want to check simple things like making sure you can ping the
server (if your firewall allows it) to make sure that you can resolve your
server using DNS...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"KRISTEN" <KRISTEN@.discussions.microsoft.com> wrote in message
news:B76386D1-75FB-4673-AC9B-FF501DB58D87@.microsoft.com...
> Hi, I'm trying to connect to an SQL Server using an ODBC driver, typed in
> the
> Machine name, but it won't let me connect.
> Where the wizard asks me what the server name is that I want to connect
> to,
> the drop down is empty. I thought it should show me a list of servers to
> choose from?
> Also, if I try to type in the machine name, and connect, it gives me an
> error that it either could not connect or I am unauthorized even though I
> know I'm using the administrators login and password.
> I'm sooooooo confused. Am I even using the right ODBC driver? It's [SQL
> Server], and they tell me the database is SQL Servcer v.8...
> Any ideas?
> THANKS!!
Connection Error using SQL Server ODBC
Hi, I'm trying to connect to an SQL Server using an ODBC driver, typed in th
e
Machine name, but it won't let me connect.
Where the wizard asks me what the server name is that I want to connect to,
the drop down is empty. I thought it should show me a list of servers to
choose from?
Also, if I try to type in the machine name, and connect, it gives me an
error that it either could not connect or I am unauthorized even though I
know I'm using the administrators login and password.
I'm sooooooo confused. Am I even using the right ODBC driver? It's [SQ
L
Server], and they tell me the database is SQL Servcer v.8...
Any ideas?
THANKS!!In the ODBC set up there are several ways to connect...
When setting it up you need to make sure that you click on client
configuraiton and choose a connection that your SQL Server allows. TCP/IP is
pretty typical on port 1433. Then you must make sure that your SQL server
allows connections using TCP/IP using your client configuration tools.
You also want to check simple things like making sure you can ping the
server (if your firewall allows it) to make sure that you can resolve your
server using DNS...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"KRISTEN" <KRISTEN@.discussions.microsoft.com> wrote in message
news:B76386D1-75FB-4673-AC9B-FF501DB58D87@.microsoft.com...
> Hi, I'm trying to connect to an SQL Server using an ODBC driver, typed in
> the
> Machine name, but it won't let me connect.
> Where the wizard asks me what the server name is that I want to connect
> to,
> the drop down is empty. I thought it should show me a list of servers to
> choose from?
> Also, if I try to type in the machine name, and connect, it gives me an
> error that it either could not connect or I am unauthorized even though I
> know I'm using the administrators login and password.
> I'm sooooooo confused. Am I even using the right ODBC driver? It's [
SQL
> Server], and they tell me the database is SQL Servcer v.8...
> Any ideas?
> THANKS!!
e
Machine name, but it won't let me connect.
Where the wizard asks me what the server name is that I want to connect to,
the drop down is empty. I thought it should show me a list of servers to
choose from?
Also, if I try to type in the machine name, and connect, it gives me an
error that it either could not connect or I am unauthorized even though I
know I'm using the administrators login and password.
I'm sooooooo confused. Am I even using the right ODBC driver? It's [SQ
L
Server], and they tell me the database is SQL Servcer v.8...
Any ideas?
THANKS!!In the ODBC set up there are several ways to connect...
When setting it up you need to make sure that you click on client
configuraiton and choose a connection that your SQL Server allows. TCP/IP is
pretty typical on port 1433. Then you must make sure that your SQL server
allows connections using TCP/IP using your client configuration tools.
You also want to check simple things like making sure you can ping the
server (if your firewall allows it) to make sure that you can resolve your
server using DNS...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"KRISTEN" <KRISTEN@.discussions.microsoft.com> wrote in message
news:B76386D1-75FB-4673-AC9B-FF501DB58D87@.microsoft.com...
> Hi, I'm trying to connect to an SQL Server using an ODBC driver, typed in
> the
> Machine name, but it won't let me connect.
> Where the wizard asks me what the server name is that I want to connect
> to,
> the drop down is empty. I thought it should show me a list of servers to
> choose from?
> Also, if I try to type in the machine name, and connect, it gives me an
> error that it either could not connect or I am unauthorized even though I
> know I'm using the administrators login and password.
> I'm sooooooo confused. Am I even using the right ODBC driver? It's [
SQL
> Server], and they tell me the database is SQL Servcer v.8...
> Any ideas?
> THANKS!!
Friday, February 24, 2012
connection driver NATURAL
does anybody know where could i find a driver which would be able to connect database with BCK extension (as i know this is database written in natural language) from SQL Server 2000I believe in general .BCK extension will be given to a backup file and check whether this is a backup file or so. If not call originator for further details or try to open in NOTEPAD and see for further information on this file.
As of I know there is no driver in SQL for .BCK extension file to import.
As of I know there is no driver in SQL for .BCK extension file to import.
Sunday, February 19, 2012
Connection between SQL Server 2000 SP3a and ODBC Driver
Database: SQL Server 2000 Developer Edition SP3a
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.
Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.
Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>
Connection between SQL Server 2000 SP3a and ODBC Driver
Database: SQL Server 2000 Developer Edition SP3a
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>
Subscribe to:
Posts (Atom)