Showing posts with label point. Show all posts
Showing posts with label point. Show all posts

Monday, March 19, 2012

Connection limits to database by operating system

Can someone point me to documentation related to the number of connections a
database can have before there is a degradation in the connection?
I was told that if you have a database on a computer with a Windows 2000
operating system you can only have 5 connections to the database or the
connections will be slow or delayed to the point that the application using
the connection will not work. Because of this, the database should be on
Windows 2000 Server. This operating system allows more connections.
I am using SQL Server 2000. The database is on a system that makes
electrical measurements and stores the analysis. There are separate
applications on network computers using TCP/IP connections that access this
analysis data.
Is there a distinction between connecting to a database via a TCP/IP
connection and connecting to the database that is on the computer that the
database is on?
Thanks in advance!
Gloria
The degradation in performance you are describing looks more
like and MSDE vs. SQL Server issue. MSDE is throttled for an
average resource usage of 5 concurrent batches. You can find
more information on this in SQL Server books online under
DBCC CONCURRENCYVIOLATION
-Sue
On Tue, 11 Jan 2005 06:33:07 -0800, Gloria
<Gloria@.discussions.microsoft.com> wrote:

>Can someone point me to documentation related to the number of connections a
>database can have before there is a degradation in the connection?
>I was told that if you have a database on a computer with a Windows 2000
>operating system you can only have 5 connections to the database or the
>connections will be slow or delayed to the point that the application using
>the connection will not work. Because of this, the database should be on
>Windows 2000 Server. This operating system allows more connections.

Connection limits to database by operating system

Can someone point me to documentation related to the number of connections a
database can have before there is a degradation in the connection?
I was told that if you have a database on a computer with a Windows 2000
operating system you can only have 5 connections to the database or the
connections will be slow or delayed to the point that the application using
the connection will not work. Because of this, the database should be on
Windows 2000 Server. This operating system allows more connections.
I am using SQL Server 2000. The database is on a system that makes
electrical measurements and stores the analysis. There are separate
applications on network computers using TCP/IP connections that access this
analysis data.
Is there a distinction between connecting to a database via a TCP/IP
connection and connecting to the database that is on the computer that the
database is on?
Thanks in advance!
GloriaThe degradation in performance you are describing looks more
like and MSDE vs. SQL Server issue. MSDE is throttled for an
average resource usage of 5 concurrent batches. You can find
more information on this in SQL Server books online under
DBCC CONCURRENCYVIOLATION
-Sue
On Tue, 11 Jan 2005 06:33:07 -0800, Gloria
<Gloria@.discussions.microsoft.com> wrote:

>Can someone point me to documentation related to the number of connections
a
>database can have before there is a degradation in the connection?
>I was told that if you have a database on a computer with a Windows 2000
>operating system you can only have 5 connections to the database or the
>connections will be slow or delayed to the point that the application using
>the connection will not work. Because of this, the database should be on
>Windows 2000 Server. This operating system allows more connections.

Thursday, March 8, 2012

Connection fails SQL 2000

One of our customers has SQl server 2000 installed
This has been working perfectly untill last Friday.
At this point various databases began to return errors
when querries were run on the data.
There appeasr to be no pattern to which databases still
work as I have two backup copies of the main databse they
use. The main one and one of the backups produce errors
yet the other backup, taken on the same day does not.
Looking at the error log (attached) there seems to be a
lot of "corrupt" entires.
Any suggestions
Date Source Message
---
--
---
--...
004 DC771 Module(sqlservr+000DC771) (ExecuteSql
(class CParamExchange *,class CXVariant *,
004 A9DE2 Module(sqlservr+000A9DE2)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A9E93 Module(sqlservr+000A9E93)
(CXteHashMatch::ExecCompile(class CExecCompContext *)
004 A70B6 Module(sqlservr+000A70B6)
(CXteHashMatch::IntermediateCompile(class IMemObj *,c
004 A8B35 Module(sqlservr+000A8B35)
(CXteHashMatch::CreateBailoutPlan(class CRemapContext
0041 F796 Module(sqlservr+0001F796)
(CSQLObject::FTransform(class CParamExchange *)+00000
0041 FDDD Module(sqlservr+0001FDDD)
(CSQLObject::FTransform2(class CSQLComment *,class CP
00415080 Module(sqlservr+00015080)
(CSQLSource::FTransform(class CParamExchange *)
+0000037C)
0041534 F Module(sqlservr+0001534F)
(CSQLSource::Execute(class CParamExchange *)+00000176
00415410 Module(sqlservr+00015410)
(CSQLSource::Execute(class CParamExchange *)
+00000343)
00415765 Module(sqlservr+00015765)
(CMsqlExecContext::Execute(class CCompPlan *,class
CParamExchange *)+000001C7)
004160 DB Module(sqlservr+000160DB)
(CMsqlExecContext::ExecuteStmts(class ExecutionContex
0041767 E Module(sqlservr+0001767E) (process_commands
(struct srv_proc *)+000001E7)
0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
(struct srv_proc *)+00000019)
00447078 Module(sqlservr+00047078)
(CCompPlan::FCompileStep(class CAlgStmt *,class
CStatement * *)+00000AE7)
004510 FE Module(sqlservr+000510FE)
(CProchdr::FCompile(class CCompPlan *,class CParamExc
0049 CB9F Module(sqlservr+0009CB9F)
(CStmtExec::XretExecute(class CMsqlExecContext *)cons
0049 CD0A Module(sqlservr+0009CD0A)
(CStmtExec::XretLocalExec(class CMsqlExecContext *,un
0049 C6F4 Module(sqlservr+0009C6F4)
(CSQLObject::FGetFromDisk(class CParamExchange *)+000
0049 DA48 Module(sqlservr+0009DA48)
(CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
00563 F78 Module(sqlservr+00163F78)
(CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
00564019 Module(sqlservr+00164019)
(BuildQueryFromTree(class TREE *,class IMemObj
*,class IMemObj *,class IQueryOb
005642 CD Module(sqlservr+001642CD)
(CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
0056701 F Module(sqlservr+0016701F)
(CBndOutputs::RemapValrefs(class CRemapContext *,int)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
00567536 Module(sqlservr+00167536)
(CXte::ExecCompile(class CExecCompContext *)
+000000B7)
005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
(void)+00000116)
0061 DDB6 Module(sqlservr+0021DDB6)
(CSpecProc::Execute(class CParamExchange *)+00000092)
0061 DA3E Module(sqlservr+0021DA3E)
(CSpecProc::ExecuteSpecial(class CParamExchange *,uns
0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
srv_proc *)+000004A8)
00703 A1C Module(sqlservr+00303A1C)
(CXteHashMatch::CreateInputScan(class IMemObj *,class
2003-11-05 12:36:10.29 server Microsoft SQL Server
2000 - 8.00.194 (Intel X86) ...
2003-11-05 12:36:10.54 server Logging SQL Server
messages in file 'd:\Program Files\Microsoft SQL
Server\MSSQ
2003-11-05 12:36:10.54 server Server Process ID is 1700.
2003-11-05 12:36:10.54 server All rights reserved.
2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
Microsoft Corporation.
2003-11-05 12:36:10.99 server SQL Server is starting at
priority class 'normal'(4 CPUs detected).
2003-11-05 12:36:13.00 server SQL Server configured for
thread mode processing.
2003-11-05 12:36:13.23 server Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-11-05 12:36:13.62 server Attempting to initialize
Distributed Transaction Coordinator.
2003-11-05 12:36:19.92 spid2 Starting up
database 'master'.
2003-11-05 12:36:27.70 spid5 Starting up
database 'model'.
2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
version '8.0.194'.
2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
2003-11-05 12:36:27.79 spid12 Starting up
database 'powerway'.
2003-11-05 12:36:27.79 spid11 Starting up
database 'dbWheelset_Live'.
2003-11-05 12:36:27.79 spid10 Starting up
database 'Northwind'.
2003-11-05 12:36:27.79 spid9 Starting up
database 'pubs'.
2003-11-05 12:36:27.79 spid8 Starting up
database 'msdb'.
2003-11-05 12:36:27.81 spid14 Starting up
database 'dbWheelSets_LIVE'.
2003-11-05 12:36:27.81 spid13 Starting up
database 'dbWheelSets_TEST'.
2003-11-05 12:36:27.89 spid16 Starting up
database 'dbWheelsets_ARCH_TEST'.
2003-11-05 12:36:27.89 spid15 Starting up
database 'dbWheelsets_BACKUP'.
2003-11-05 12:36:27.98 spid17 Starting up
database 'dbWheelsets_DATA_TEST'.
2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
2003-11-05 12:36:28.51 spid11 Analysis of
database 'dbWheelset_Live' (7) is 100% complete
(approximately 0 mo
2003-11-05 12:36:28.65 spid12 Analysis of
database 'powerway' (8) is 100% complete (approximately 0
more seco
2003-11-05 12:36:28.87 server SQL Server is ready for
client connections
2003-11-05 12:36:28.87 server SQL server listening on
172.20.120.23:1433, 127.0.0.1:1433.
2003-11-05 12:36:28.87 server SQL server listening on
TCP, Shared Memory, Named Pipes.
2003-11-05 12:36:29.76 spid13 Analysis of
database 'dbWheelSets_TEST' (9) is 100% complete
(approximately 0 m
2003-11-05 12:36:38.67 spid5 Starting up
database 'tempdb'.
2003-11-05 12:36:41.85 spid2 Recovery complete.
2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
version '2000.80.194' to execute extended stored procedure
2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
version '2000.80.194' to execute extended stored
procedure '
2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
version '4.0.5'...
2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
Process 55 generated fatal exception c0000005 EXCEPTIO
2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
State: 0
410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
(class UmsWorkQueue *)+00000264)
4107382 C Module(UMS+0000382C) (ThreadStartRoutine
(void *)+000000BC)
7 C57B382 Module(KERNEL32+0000B382)
(lstrcmpiW+000000B7)
78008454 Module(MSVCRT+00008454)
(_endthread+000000C1)Have you tried running DBCC CHECKDB
--
HTH
Ryan Waight, MCDBA, MCSE
"john kinghorn" <anonymous@.discussions.microsoft.com> wrote in message
news:076a01c3a787$7e28ea20$a401280a@.phx.gbl...
> One of our customers has SQl server 2000 installed
> This has been working perfectly untill last Friday.
> At this point various databases began to return errors
> when querries were run on the data.
> There appeasr to be no pattern to which databases still
> work as I have two backup copies of the main databse they
> use. The main one and one of the backups produce errors
> yet the other backup, taken on the same day does not.
> Looking at the error log (attached) there seems to be a
> lot of "corrupt" entires.
> Any suggestions
>
> Date Source Message
> ---
> --
> ---
> --...
> 004 DC771 Module(sqlservr+000DC771) (ExecuteSql
> (class CParamExchange *,class CXVariant *,
> 004 A9DE2 Module(sqlservr+000A9DE2)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A9E93 Module(sqlservr+000A9E93)
> (CXteHashMatch::ExecCompile(class CExecCompContext *)
> 004 A70B6 Module(sqlservr+000A70B6)
> (CXteHashMatch::IntermediateCompile(class IMemObj *,c
> 004 A8B35 Module(sqlservr+000A8B35)
> (CXteHashMatch::CreateBailoutPlan(class CRemapContext
> 0041 F796 Module(sqlservr+0001F796)
> (CSQLObject::FTransform(class CParamExchange *)+00000
> 0041 FDDD Module(sqlservr+0001FDDD)
> (CSQLObject::FTransform2(class CSQLComment *,class CP
> 00415080 Module(sqlservr+00015080)
> (CSQLSource::FTransform(class CParamExchange *)
> +0000037C)
> 0041534 F Module(sqlservr+0001534F)
> (CSQLSource::Execute(class CParamExchange *)+00000176
> 00415410 Module(sqlservr+00015410)
> (CSQLSource::Execute(class CParamExchange *)
> +00000343)
> 00415765 Module(sqlservr+00015765)
> (CMsqlExecContext::Execute(class CCompPlan *,class
> CParamExchange *)+000001C7)
> 004160 DB Module(sqlservr+000160DB)
> (CMsqlExecContext::ExecuteStmts(class ExecutionContex
> 0041767 E Module(sqlservr+0001767E) (process_commands
> (struct srv_proc *)+000001E7)
> 0043 B7EF Module(sqlservr+0003B7EF) (execute_rpc
> (struct srv_proc *)+00000019)
> 00447078 Module(sqlservr+00047078)
> (CCompPlan::FCompileStep(class CAlgStmt *,class
> CStatement * *)+00000AE7)
> 004510 FE Module(sqlservr+000510FE)
> (CProchdr::FCompile(class CCompPlan *,class CParamExc
> 0049 CB9F Module(sqlservr+0009CB9F)
> (CStmtExec::XretExecute(class CMsqlExecContext *)cons
> 0049 CD0A Module(sqlservr+0009CD0A)
> (CStmtExec::XretLocalExec(class CMsqlExecContext *,un
> 0049 C6F4 Module(sqlservr+0009C6F4)
> (CSQLObject::FGetFromDisk(class CParamExchange *)+000
> 0049 DA48 Module(sqlservr+0009DA48)
> (CStmtSelect::Init(class CAlgStmt *,class CCompPlan *
> 00563 F78 Module(sqlservr+00163F78)
> (CStmtQuery::InitQuery(class CAlgStmt *,class CCompPl
> 00564019 Module(sqlservr+00164019)
> (BuildQueryFromTree(class TREE *,class IMemObj
> *,class IMemObj *,class IQueryOb
> 005642 CD Module(sqlservr+001642CD)
> (CCvtTree::PqryFromTree(class TREE *,class IMemObj *,
> 0056701 F Module(sqlservr+0016701F)
> (CBndOutputs::RemapValrefs(class CRemapContext *,int)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 00567536 Module(sqlservr+00167536)
> (CXte::ExecCompile(class CExecCompContext *)
> +000000B7)
> 005688 A4 Module(sqlservr+001688A4) (CQuery::Prepare
> (void)+00000116)
> 0061 DDB6 Module(sqlservr+0021DDB6)
> (CSpecProc::Execute(class CParamExchange *)+00000092)
> 0061 DA3E Module(sqlservr+0021DA3E)
> (CSpecProc::ExecuteSpecial(class CParamExchange *,uns
> 0063 C71D Module(sqlservr+0023C71D) (execrpc(struct
> srv_proc *)+000004A8)
> 00703 A1C Module(sqlservr+00303A1C)
> (CXteHashMatch::CreateInputScan(class IMemObj *,class
> 2003-11-05 12:36:10.29 server Microsoft SQL Server
> 2000 - 8.00.194 (Intel X86) ...
> 2003-11-05 12:36:10.54 server Logging SQL Server
> messages in file 'd:\Program Files\Microsoft SQL
> Server\MSSQ
> 2003-11-05 12:36:10.54 server Server Process ID is 1700.
> 2003-11-05 12:36:10.54 server All rights reserved.
> 2003-11-05 12:36:10.54 server Copyright (C) 1988-2000
> Microsoft Corporation.
> 2003-11-05 12:36:10.99 server SQL Server is starting at
> priority class 'normal'(4 CPUs detected).
> 2003-11-05 12:36:13.00 server SQL Server configured for
> thread mode processing.
> 2003-11-05 12:36:13.23 server Using dynamic lock
> allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
> 2003-11-05 12:36:13.62 server Attempting to initialize
> Distributed Transaction Coordinator.
> 2003-11-05 12:36:19.92 spid2 Starting up
> database 'master'.
> 2003-11-05 12:36:27.70 spid5 Starting up
> database 'model'.
> 2003-11-05 12:36:27.70 server Using 'SSNETLIB.DLL'
> version '8.0.194'.
> 2003-11-05 12:36:27.73 spid2 Server name is 'WRLW2S002'.
> 2003-11-05 12:36:27.79 spid12 Starting up
> database 'powerway'.
> 2003-11-05 12:36:27.79 spid11 Starting up
> database 'dbWheelset_Live'.
> 2003-11-05 12:36:27.79 spid10 Starting up
> database 'Northwind'.
> 2003-11-05 12:36:27.79 spid9 Starting up
> database 'pubs'.
> 2003-11-05 12:36:27.79 spid8 Starting up
> database 'msdb'.
> 2003-11-05 12:36:27.81 spid14 Starting up
> database 'dbWheelSets_LIVE'.
> 2003-11-05 12:36:27.81 spid13 Starting up
> database 'dbWheelSets_TEST'.
> 2003-11-05 12:36:27.89 spid16 Starting up
> database 'dbWheelsets_ARCH_TEST'.
> 2003-11-05 12:36:27.89 spid15 Starting up
> database 'dbWheelsets_BACKUP'.
> 2003-11-05 12:36:27.98 spid17 Starting up
> database 'dbWheelsets_DATA_TEST'.
> 2003-11-05 12:36:28.43 spid5 Clearing tempdb database.
> 2003-11-05 12:36:28.51 spid11 Analysis of
> database 'dbWheelset_Live' (7) is 100% complete
> (approximately 0 mo
> 2003-11-05 12:36:28.65 spid12 Analysis of
> database 'powerway' (8) is 100% complete (approximately 0
> more seco
> 2003-11-05 12:36:28.87 server SQL Server is ready for
> client connections
> 2003-11-05 12:36:28.87 server SQL server listening on
> 172.20.120.23:1433, 127.0.0.1:1433.
> 2003-11-05 12:36:28.87 server SQL server listening on
> TCP, Shared Memory, Named Pipes.
> 2003-11-05 12:36:29.76 spid13 Analysis of
> database 'dbWheelSets_TEST' (9) is 100% complete
> (approximately 0 m
> 2003-11-05 12:36:38.67 spid5 Starting up
> database 'tempdb'.
> 2003-11-05 12:36:41.85 spid2 Recovery complete.
> 2003-11-05 12:36:49.51 spid51 Using 'xpsqlbot.dll'
> version '2000.80.194' to execute extended stored procedure
> 2003-11-05 12:36:51.96 spid51 Using 'xpstar.dll'
> version '2000.80.194' to execute extended stored
> procedure '
> 2003-11-05 13:15:27.45 spid55 Using 'sqlimage.dll'
> version '4.0.5'...
> 2003-11-05 13:15:27.46 spid55 SqlDumpExceptionHandler:
> Process 55 generated fatal exception c0000005 EXCEPTIO
> 2003-11-05 13:15:27.46 spid55 Error: 0, Severity: 19,
> State: 0
> 410735 D0 Module(UMS+000035D0) (ProcessWorkRequests
> (class UmsWorkQueue *)+00000264)
> 4107382 C Module(UMS+0000382C) (ThreadStartRoutine
> (void *)+000000BC)
> 7 C57B382 Module(KERNEL32+0000B382)
> (lstrcmpiW+000000B7)
> 78008454 Module(MSVCRT+00008454)
> (_endthread+000000C1)
>

Tuesday, February 14, 2012

Connecting to SQLExpress from classic ASP.

Migrating a site to a new server. Moved data to SQLExpress. Changed connection string to point to SQLExpress and now I am getting this error.

Microsoft OLE DB Provider for SQL Servererror '80004005'

Cannot open database "PHCSQL" requested by the login. The login failed.

/func/inc_DatabaseFunctions.inc, line 5
Do I need to do permissions differently than MSDE?
Did connection strings change?
Help?

Hi,
Download the full eval version and install it as a named instance and register the Express. How install the full version management studio which is a separate install and right click at the top to register the Express. Then create permissions for Asp in the security section of management studio. Another option is to just restore the backup .bak file of the MSDE with the backup and restore wizard and choose the restore from a device option. Try the links below to download the eval verion and connection strings including old style connection strings. Hope this helps.

http://www.microsoft.com/sql/downloads/trial-software.mspx

http://www.carlprothman.net/Default.aspx?tabid=81