Hi
I have an application that uses an ADOConnection named CONNECTION1 and an AD
ODataset.The dataset fetches a record for editing it.This dataset has no Con
nectionString and its connection is the CONNECTION1.After opening the datase
t and editing record (befor
posting it) I execute a Stord Procedure to update another record in another
table with CONNECTION1.EXECUTE.
After opening the dataset I see a row in Management -> Current Activity -> P
rocess Info in EnterPrise Manager.And After CONNECTION.EXECUTE statement I s
ee 2 rows in Enterprise Manager.
I do all data modification by one ADOConnection in Delphi5 but SQL SERVER 20
00 do these modification by separate SPIDs (sessions).
How can I prevent this?
Dose ADOConnection or ADODataset have any property to prevent that? Or shoul
d I do anything in SQL SERVER?
ThanksYou may not be able to prevent it. ADO and ODBC, for that matter, will
spawn connections as they see fit. In most cases it does this because the
first SPID is in the middle of some process that has not completed, so the
second SPID is necesary to perform any other task. Normally this does not
cause any problems.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Showing posts with label sessions. Show all posts
Showing posts with label sessions. Show all posts
Wednesday, March 7, 2012
multiple sessions when using ADO
Hi
I have an application that uses an ADOConnection named CONNECTION1 and an ADODataset.The dataset fetches a record for editing it.This dataset has no ConnectionString and its connection is the CONNECTION1.After opening the dataset and editing record (befor
posting it) I execute a Stord Procedure to update another record in another table with CONNECTION1.EXECUTE.
After opening the dataset I see a row in Management -> Current Activity -> Process Info in EnterPrise Manager.And After CONNECTION.EXECUTE statement I see 2 rows in Enterprise Manager.
I do all data modification by one ADOConnection in Delphi5 but SQL SERVER 2000 do these modification by separate SPIDs (sessions).
How can I prevent this?
Dose ADOConnection or ADODataset have any property to prevent that? Or should I do anything in SQL SERVER?
Thanks
You may not be able to prevent it. ADO and ODBC, for that matter, will
spawn connections as they see fit. In most cases it does this because the
first SPID is in the middle of some process that has not completed, so the
second SPID is necesary to perform any other task. Normally this does not
cause any problems.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have an application that uses an ADOConnection named CONNECTION1 and an ADODataset.The dataset fetches a record for editing it.This dataset has no ConnectionString and its connection is the CONNECTION1.After opening the dataset and editing record (befor
posting it) I execute a Stord Procedure to update another record in another table with CONNECTION1.EXECUTE.
After opening the dataset I see a row in Management -> Current Activity -> Process Info in EnterPrise Manager.And After CONNECTION.EXECUTE statement I see 2 rows in Enterprise Manager.
I do all data modification by one ADOConnection in Delphi5 but SQL SERVER 2000 do these modification by separate SPIDs (sessions).
How can I prevent this?
Dose ADOConnection or ADODataset have any property to prevent that? Or should I do anything in SQL SERVER?
Thanks
You may not be able to prevent it. ADO and ODBC, for that matter, will
spawn connections as they see fit. In most cases it does this because the
first SPID is in the middle of some process that has not completed, so the
second SPID is necesary to perform any other task. Normally this does not
cause any problems.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Monday, February 20, 2012
Multiple SA Sessions
As a DBA, I was just handed a SQL Server to support where the client has
install an application and all user connections are logged in as 'sa'. Does
anybody know what priority 'sa' has, would this be a huge contention problem
and would this be one of my major sources for blocking processes? There are
about 20,000 updates per day and active queries being run simultaniously.
This is SQL Server 2000 Standard Ed on windows 2000.
I am looking for any documents or whitepapers to convince client this has to
change - comments and suggestions are welcome.The login doesn't influence priorities regarding resource usage, blocking et
c. There are many
reasons why you shouldn't be using sa, but blocking problems is not one of t
hem.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBAJimbo" <DBAJimbo@.discussions.microsoft.com> wrote in message
news:8540E787-D825-4931-B2F1-CAF449744D96@.microsoft.com...
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Do
es
> anybody know what priority 'sa' has, would this be a huge contention probl
em
> and would this be one of my major sources for blocking processes? There a
re
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has
to
> change - comments and suggestions are welcome.|||As the sa account can do anything on the server, this setup raises all sorts
of security issues. Another account should be created and used, which has
only the access it needs.
Alternatively, if your users can all authenticate using their windows domain
accounts, you can create windows domain groups that you can give certain
rights to, and add users to the appropriate groups. This gives much better
control over who can do/access what on the server.
Regards
Adam
"DBAJimbo" wrote:
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Do
es
> anybody know what priority 'sa' has, would this be a huge contention probl
em
> and would this be one of my major sources for blocking processes? There a
re
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has
to
> change - comments and suggestions are welcome.
install an application and all user connections are logged in as 'sa'. Does
anybody know what priority 'sa' has, would this be a huge contention problem
and would this be one of my major sources for blocking processes? There are
about 20,000 updates per day and active queries being run simultaniously.
This is SQL Server 2000 Standard Ed on windows 2000.
I am looking for any documents or whitepapers to convince client this has to
change - comments and suggestions are welcome.The login doesn't influence priorities regarding resource usage, blocking et
c. There are many
reasons why you shouldn't be using sa, but blocking problems is not one of t
hem.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBAJimbo" <DBAJimbo@.discussions.microsoft.com> wrote in message
news:8540E787-D825-4931-B2F1-CAF449744D96@.microsoft.com...
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Do
es
> anybody know what priority 'sa' has, would this be a huge contention probl
em
> and would this be one of my major sources for blocking processes? There a
re
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has
to
> change - comments and suggestions are welcome.|||As the sa account can do anything on the server, this setup raises all sorts
of security issues. Another account should be created and used, which has
only the access it needs.
Alternatively, if your users can all authenticate using their windows domain
accounts, you can create windows domain groups that you can give certain
rights to, and add users to the appropriate groups. This gives much better
control over who can do/access what on the server.
Regards
Adam
"DBAJimbo" wrote:
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Do
es
> anybody know what priority 'sa' has, would this be a huge contention probl
em
> and would this be one of my major sources for blocking processes? There a
re
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has
to
> change - comments and suggestions are welcome.
Multiple SA Sessions
As a DBA, I was just handed a SQL Server to support where the client has
install an application and all user connections are logged in as 'sa'. Does
anybody know what priority 'sa' has, would this be a huge contention problem
and would this be one of my major sources for blocking processes? There are
about 20,000 updates per day and active queries being run simultaniously.
This is SQL Server 2000 Standard Ed on windows 2000.
I am looking for any documents or whitepapers to convince client this has to
change - comments and suggestions are welcome.The login doesn't influence priorities regarding resource usage, blocking etc. There are many
reasons why you shouldn't be using sa, but blocking problems is not one of them.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBAJimbo" <DBAJimbo@.discussions.microsoft.com> wrote in message
news:8540E787-D825-4931-B2F1-CAF449744D96@.microsoft.com...
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.|||As the sa account can do anything on the server, this setup raises all sorts
of security issues. Another account should be created and used, which has
only the access it needs.
Alternatively, if your users can all authenticate using their windows domain
accounts, you can create windows domain groups that you can give certain
rights to, and add users to the appropriate groups. This gives much better
control over who can do/access what on the server.
Regards
Adam
"DBAJimbo" wrote:
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.
install an application and all user connections are logged in as 'sa'. Does
anybody know what priority 'sa' has, would this be a huge contention problem
and would this be one of my major sources for blocking processes? There are
about 20,000 updates per day and active queries being run simultaniously.
This is SQL Server 2000 Standard Ed on windows 2000.
I am looking for any documents or whitepapers to convince client this has to
change - comments and suggestions are welcome.The login doesn't influence priorities regarding resource usage, blocking etc. There are many
reasons why you shouldn't be using sa, but blocking problems is not one of them.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBAJimbo" <DBAJimbo@.discussions.microsoft.com> wrote in message
news:8540E787-D825-4931-B2F1-CAF449744D96@.microsoft.com...
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.|||As the sa account can do anything on the server, this setup raises all sorts
of security issues. Another account should be created and used, which has
only the access it needs.
Alternatively, if your users can all authenticate using their windows domain
accounts, you can create windows domain groups that you can give certain
rights to, and add users to the appropriate groups. This gives much better
control over who can do/access what on the server.
Regards
Adam
"DBAJimbo" wrote:
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.
Multiple SA Sessions
As a DBA, I was just handed a SQL Server to support where the client has
install an application and all user connections are logged in as 'sa'. Does
anybody know what priority 'sa' has, would this be a huge contention problem
and would this be one of my major sources for blocking processes? There are
about 20,000 updates per day and active queries being run simultaniously.
This is SQL Server 2000 Standard Ed on windows 2000.
I am looking for any documents or whitepapers to convince client this has to
change - comments and suggestions are welcome.
The login doesn't influence priorities regarding resource usage, blocking etc. There are many
reasons why you shouldn't be using sa, but blocking problems is not one of them.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBAJimbo" <DBAJimbo@.discussions.microsoft.com> wrote in message
news:8540E787-D825-4931-B2F1-CAF449744D96@.microsoft.com...
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.
|||As the sa account can do anything on the server, this setup raises all sorts
of security issues. Another account should be created and used, which has
only the access it needs.
Alternatively, if your users can all authenticate using their windows domain
accounts, you can create windows domain groups that you can give certain
rights to, and add users to the appropriate groups. This gives much better
control over who can do/access what on the server.
Regards
Adam
"DBAJimbo" wrote:
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.
install an application and all user connections are logged in as 'sa'. Does
anybody know what priority 'sa' has, would this be a huge contention problem
and would this be one of my major sources for blocking processes? There are
about 20,000 updates per day and active queries being run simultaniously.
This is SQL Server 2000 Standard Ed on windows 2000.
I am looking for any documents or whitepapers to convince client this has to
change - comments and suggestions are welcome.
The login doesn't influence priorities regarding resource usage, blocking etc. There are many
reasons why you shouldn't be using sa, but blocking problems is not one of them.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"DBAJimbo" <DBAJimbo@.discussions.microsoft.com> wrote in message
news:8540E787-D825-4931-B2F1-CAF449744D96@.microsoft.com...
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.
|||As the sa account can do anything on the server, this setup raises all sorts
of security issues. Another account should be created and used, which has
only the access it needs.
Alternatively, if your users can all authenticate using their windows domain
accounts, you can create windows domain groups that you can give certain
rights to, and add users to the appropriate groups. This gives much better
control over who can do/access what on the server.
Regards
Adam
"DBAJimbo" wrote:
> As a DBA, I was just handed a SQL Server to support where the client has
> install an application and all user connections are logged in as 'sa'. Does
> anybody know what priority 'sa' has, would this be a huge contention problem
> and would this be one of my major sources for blocking processes? There are
> about 20,000 updates per day and active queries being run simultaniously.
> This is SQL Server 2000 Standard Ed on windows 2000.
> I am looking for any documents or whitepapers to convince client this has to
> change - comments and suggestions are welcome.
Subscribe to:
Posts (Atom)