however a cost justification can be made.
Check
http://www.tpc.org/tpcw/results/tpc...erf_results.asp
J
quote:
>--Original Message--
>Hello all,
>At the moment accounting wants to know how much it costs
>to maintenance a SQL-database. They have approached me to
>tell them how much the maintenance of a database costs.
>They want to have a little list in which they can see the
>maintenance-cost against the database-size. Something
like
quote:
>..
>0.1 GByte: 1 hour a month
>1 GByte: 2 hour a month
>100 GByte: 3 hour a month
>The only maintenance I do is:
>-1- Activate and scheduling of the "Database Maintenance
>Plan";
>-2- A weekly recovery test of 1 randomly chosen database.
>So for me, size does not matter. I don't notice if a
>backup takes longer. The only thing that costs a little
>more time is a recovery test of a big database. CPU, Mem
>and disk-space are the responsibility of another
>department.
>Accounting does not believe that the maintenance-cost of
a
quote:One variable cost related to size is
>database is independent of the database-size. Am I
>overlooking something? What are you're maintenance
>experiences? What do you charge for maintenance?
>Hope someone can shed some light on the subject,
>tanks in advance,
>Annick van den Broek
>.
>
Disk, and tape for backup. Downtime for restore of larger DB. Cost of your
time ( if you wait) for other maint tasks like checkdb, drop/create
indexes...
But as you say, you should do all of these tasks regardless of size..so (in
my opinion.) the fixed costs are MOST of the total cost, and variable costs
based on size of DB are limited..
"Annick van den Broek" <anonymous@.discussions.microsoft.com> wrote in
message news:970a01c3eb24$90714c00$a301280a@.phx.gbl...
quote:|||Accounting should understand the concept of fixed vs. variable costs. There
> Hello all,
> At the moment accounting wants to know how much it costs
> to maintenance a SQL-database. They have approached me to
> tell them how much the maintenance of a database costs.
> They want to have a little list in which they can see the
> maintenance-cost against the database-size. Something like
> .
> 0.1 GByte: 1 hour a month
> 1 GByte: 2 hour a month
> 100 GByte: 3 hour a month
> The only maintenance I do is:
> -1- Activate and scheduling of the "Database Maintenance
> Plan";
> -2- A weekly recovery test of 1 randomly chosen database.
> So for me, size does not matter. I don't notice if a
> backup takes longer. The only thing that costs a little
> more time is a recovery test of a big database. CPU, Mem
> and disk-space are the responsibility of another
> department.
> Accounting does not believe that the maintenance-cost of a
> database is independent of the database-size. Am I
> overlooking something? What are you're maintenance
> experiences? What do you charge for maintenance?
> Hope someone can shed some light on the subject,
> tanks in advance,
> Annick van den Broek
>
is a fixed cost per database and a variable cost per database. The variable
cost can be grouped by size ranges (<1GB, 1-10GB, 10GB-100GB, 100GB+) or any
ranges that you feel comfortable with. The big issues are time and space.
Can you backup and restore the system within the allowable time windows and
do you have the space to handle a decent backup rotation? Also, throughput
is an issue on FULL recovery model. You have to have space for transaction
log backups for whatever period you determine.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Annick van den Broek" <anonymous@.discussions.microsoft.com> wrote in
message news:970a01c3eb24$90714c00$a301280a@.phx.gbl...
quote:
> Hello all,
> At the moment accounting wants to know how much it costs
> to maintenance a SQL-database. They have approached me to
> tell them how much the maintenance of a database costs.
> They want to have a little list in which they can see the
> maintenance-cost against the database-size. Something like
> .
> 0.1 GByte: 1 hour a month
> 1 GByte: 2 hour a month
> 100 GByte: 3 hour a month
> The only maintenance I do is:
> -1- Activate and scheduling of the "Database Maintenance
> Plan";
> -2- A weekly recovery test of 1 randomly chosen database.
> So for me, size does not matter. I don't notice if a
> backup takes longer. The only thing that costs a little
> more time is a recovery test of a big database. CPU, Mem
> and disk-space are the responsibility of another
> department.
> Accounting does not believe that the maintenance-cost of a
> database is independent of the database-size. Am I
> overlooking something? What are you're maintenance
> experiences? What do you charge for maintenance?
> Hope someone can shed some light on the subject,
> tanks in advance,
> Annick van den Broek
>
No comments:
Post a Comment