Cost of ownership: MV vs. SQL Server
- From: "dawn" <dawnwolthuis@xxxxxxxxx>
- Date: 8 Sep 2005 12:53:00 -0700
I'm interested in hearing from people who are running (or have run)
transaction processing systems on both an MV system and SQL Server.
Question: What are the differences in cost of ownership that you see
between these two environments?
I'm interested in your intuition as to whether the total cost of
ownership for each environment is roughly the same or whether one is
less expensive than the other. I'm also interested in any more
specific information or impressions you might have.
Some categories might be:
1) Ease in learning & training
2) Actual hard costs in the budget for the software
3) How much hardware is required for each: cpu, memory, disk
4) User access (e.g. 24/7)
5) Reliability, risk of downtime, risk of data loss
6) Number or fraction of professionals required to support a production
environment in each (and/or lists of what tasks are required on an
on-going or periodic basis)
7) Cost of optional and 3rd party add-ins
8) End-User Satisfaction
9) IT User Satisfaction
10) Ease, speed, & quality of new software development & maintenance of
existing in-house software
11) Vendor support
12) Ease of getting the data back out, is there a need to make data
marts for reporting more often in one environment than the other?
13) Cost of establishing or maintaining security / access
14) Cost of backups
15) Performance
Other categories?
Thanks in advance for any help you can give. --dawn
.
- Follow-Ups:
- Re: Cost of ownership: MV vs. SQL Server
- From: qbits killed the cat
- Re: Cost of ownership: MV vs. SQL Server
- From: Kevin Powick
- Re: Cost of ownership: MV vs. SQL Server
- From: Dave Weaver
- Re: Cost of ownership: MV vs. SQL Server
- Prev by Date: Re: D3 on Debian Linux?
- Next by Date: printing tools
- Previous by thread: Zombied telnet ports on D3/Linux
- Next by thread: Re: Cost of ownership: MV vs. SQL Server
- Index(es):
Relevant Pages
|