December 6, 2016 at 4:56 am
I was talking to a colleague of mine who does application development.
He was telling that there are various factors through which they measure and manage the applications and below are some of the ones
Application Size
Interfaces
Release Frequency
Primary Technology / Number of Primary Languages
Mobile Element Incorporated
Total Users
Peak Concurrent Users
User Location
Wondering if we can have a list of factors that measure database complexity?
May be the high availability or DR methods used, OLTP/OLAP etc etc?
December 8, 2016 at 8:32 pm
Can someone help me out on this pls
December 10, 2016 at 6:59 am
How do you measure database complexity?
Ideally a solution will be as simple as possible, but does not necessarily mean it will be simple.
Very rarely will a developer be able to tell you how loaded the application will be when it moves into production, how many users will use it and so on so you as the DBA need to rely on experience and knowledge to build the Environment appropriately from the outset.
When you design a database infrastructure (read installing the environment) consider the following:
1. Availability: Does it Need to be available 24/7 or can downtime for a short period be tolerated? This will help you decide which high availability mechanism will be appropriate.
2. Consider the placement of your database files on disk. Will you benefit from multiple datafiles across multiple LUNs or will it suffice to have just one?
3. What sort of indexing scheme are you going to use?
The list could easily go on and on.
The best answer though is to learn what is expected from a database infrastructure and how to build it in such a way that it is scalable to take into account Things that might increase the load in the future.
December 10, 2016 at 11:48 am
Benki Chendu (12/8/2016)
Can someone help me out on this pls
Until you draw out a full ERD and understand the logic required to solve both batch problems and front-end lookups, it just not possible to measure so-called complexity. Even if you do this up front, the complexity will change because you can't correct a blank piece of paper.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2016 at 12:48 pm
Beyond the number of objects in the database, there can be complexity in seemingly small things. For example, one report procedure that goes against a single table can be complex and take things into account the developer doesn't know about.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply