I'm a SQL DBA but have only dealt with databases less than 1 TB in
size. Some of my programmers are asking how well SQL 2000 will handle
a 5 TB database. We're wondering if SQL is sufficient of if we need
to go to Oracle. I know the SQL 2000 specs say it can handle it but
I'm looking for real world experiences.SQL Server can handle much more data than that and does every day if done
properly. I can bring a server to it's knees with a 10MB database with a
poor schema and a poor app etc. With a proper design and planning size
really shouldn't matter.
Andrew J. Kelly SQL MVP
"Charles Crosby" <crosbyct@.yahoo.com> wrote in message
news:8433ccee.0403101124.280f58a8@.posting.google.com...
> I'm a SQL DBA but have only dealt with databases less than 1 TB in
> size. Some of my programmers are asking how well SQL 2000 will handle
> a 5 TB database. We're wondering if SQL is sufficient of if we need
> to go to Oracle. I know the SQL 2000 specs say it can handle it but
> I'm looking for real world experiences.
Showing posts with label dba. Show all posts
Showing posts with label dba. Show all posts
Monday, March 12, 2012
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)