The best practice for THAT would be to ensure all SQL security auditing is
temporarily turned OFF, heh heh.
(Embedded image moved to file: pic25951.gif)Countrywide
Michael Beadles
Client Server Engineer III
MIS-Distributed Systems Suppt
818-597-5509 29851 Agoura Road
Office Agoura Hills, CA 91301
USA
[Email address protected]
"Tad Huck "
<mssqldba-ezmlmsh
ield-x39682617.x1 To
[Email Address Removed] "LazyDBA Discussion"
.com> <[Email address protected]
cc
03/28/2006 01:30
PM Subject
RE: Best Practices
Here is my "un-official" best practice for establishing justification
for another DBA:
1. Create a script that will deadlock the primary table(s) on each of
your production critical databases.
2. When management begins to jump up and down and their eyes bulge out
of their sockets; bring them a budget requisite change form for adding
the additional DBA.
3. Kill the deadlock script and blame your favorite developer group of
writing bad code.
4. If this does not work go to step 1 and retry adding an hour to your
delay period
DBA's can be roughly classified as 'production' or 'development' each
requires a different skill set. Most people assume a 'production' DBA is
lower level and less adept as those doing SQL development work. The fact
is that in a very complex ASP 'on-demand' data center the production
DBA's must have an extremely high degree of detailed knowledge and
understanding of how SQL Server operates , of Operating systems,
configurations, SAN, NAS and various other related infrastructure that
may comprise the entire application environment as well as SQL
architecture itself. The way your company is organized, the number of
developers and the types of software you manage will all be factors to
look at. One way to highlight resource shortages is by establishing
meaningful Service Level Agreements and then tracking the delivery times
or control factors. If you can show you just can't keep up then this
makes a good case for management to respond to.
Tad Huck
{Database Czar - " If you can't learn to do something well, learn to
enjoy doing it poorly. "}
REAL PAGE INC.
4000 International Parkway
Carrollton, Texas 75007-1913
(972) 820-3432.
-----Original Message-----
From: Michael Everett
[mailto:mssqldba-ezmlmshield-x78443700.[Email address protected]
Sent: Tuesday, March 28, 2006 2:00 PM
To: LazyDBA Discussion
Subject: Best Practices
Hello everyone,
Can someone point me in the right direction? I am looking for
documentation that sets "guidelines" for the ratio of SQL DB servers to
DBA. We are trying to justify the need for an additional DBA in our
company.
Thank you all in advance.
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
This message is intended only for the use of the individual(s) or entity to
which it is addressed and may contain information that is privileged,
confidential, and/or proprietary to RealPage and its affiliated companies.
If the reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution, forwarding or copying of
this communication is prohibited without the express permission of the
sender. If you have received this communication in error, please notify the
sender immediately and delete the original message.
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
======================================================================
Confidentiality Notice: The information contained in and transmitted with this communication is strictly confidential, is intended only for the use of the intended recipient, and is the property of Countrywide Financial Corporation or its affiliates and subsidiaries. If you are not the intended recipient, you are hereby notified that any use of the information contained in or transmitted with the communication or dissemination, distribution, or copying of this communication is strictly prohibited by law. If you have received this communication in error, please immediately return this communication to the sender and delete the original message and any copy of it in your possession.
======================================================================
MS Sql Server LazyDBA home page