Just wondering, how many of you actually find E-R diagrams useful in modeling data?

Sometimes I find informal sketching along those lines to be useful, both for getting a handle on an existing system and designing a new one. I've never used a formal E-R diagram, though.

I suppose if I was stuck doing design by committee it might be useful, but informal and reasonable stuff has never merited it. Anything more complex that circuit diagrams had better buy me an awful lot of return for the effort as compared to a notepad sketch.

thanks, I am trying to prove a point to one of my colleagues...

Basically E-R diagrams are for people who are probably going to come in after you had already created the program to be able to see whats going on. Its much like having wiring diagrams with control panels, even though if I design them and know exactly what each wire is wired to, the next guy coming in needs a map. Any job shop creating database driven software will require ERD's. Your going to have a hard time convincing anyone they are not useful.

Depends on the audience and design methodology.

I think Ibudin makes a good point about using them as high level documentation. I rarely make them before the system is designed anymore though. It sounds good in theory, but I find that over-designing up front leads to all kinds of fail, more often than not.

I find them useful, but since my company won't buy any tool to use them, I'm stuck with the diagramming wizard in sql server (and visio). The boss doesn't like planning of any reasonable sort, so we don't (translation: cannot) get into BDUF, and instead make lots of balls of mud.

If you had used ErWin at some time in your past, I think you'd be more in favor of ERDs, but since that program is now like $5k + $2k/year, it is priced out of the pockets of most companies. If the price of ErWin was 1/10 of what it is now, then I'd gladly pay for it out of my own pocket, but what can you expect from the evil greedy jerks of Computer Associates?

I found them mostly an academic exercise.

Fuck E-R diagrams, that is all!

I am with Sanchek, hate over designing in the initial stages but it is needed for robust, losely coupled, yet tightly cohesive software. (old comp sci classes talking)

Basically, a new guy was hired, and he wants to bring his bloated "enterprise" ivory tower thinking into our company (I have been opposed to his employment from day one). We've never used an E-R diagram to map our databases. We find schemas and objective programming to be sufficient along with frameworks/custom libraries that abstract database level interaction.

We're a 60-person company, not a 1000-person company. I can see the point in E-R diagrams if you are trying to keep some consistency in the company, but ideas can usually be communicated much more effectively than what university professors would include in a publication in an effort to show how clever they are.

We have some Ruby on Rails applications, Objective-C, J2EE, and some .NET applications. We are mapping our materials requirement planning internal application to our MySAP installation.

We'll some times its better to let the new guy at least show you how valuable it would/could be. Some times change is tough, some times the ideas do stink, but I'd let it play out unless it is uterally useless. Great, even good programmers are hard to come by or even keep employed, turn over for greener pastures so he may turn out to be good. The funny thing is that hes promoting it, when I was interviewing for S.E. jobs all the places I went to wanted to hear about my knowledge of all CASE tools. Every place I looked at used them, pretty extensively.

They're nice for documentation but I've still yet to see a full blown E-R for anything non-trivial be human readable, either, so it's also fairly important to know how to be concise in them I suppose. The real danger with stuff like that is people getting stuck on the diagrams and using those as claims of validity or correctness, that's how you end up with committee-ware.

I'd be fairly suspect of "the new guy" wanting big changes just because I remember being 22, the new guy, and wanting to change stuff.

Ok, what exactly is an E-R diagram?

I saw the mention of Visio which we use especially to demonstrate complex cluster systems, network, resource groups, applications, etc....but you use these for what in the programming/database world exactly? Any examples of this?

It's a formalized pictographic language of essentially making flow-charts of Relationships between Entities. Think Visio for the ultra-anal. I'm sure there is software that maps between ER-descriptions and insert-your-DB-and-middleware-here, but I'd be mildly frightened to have to use it.

This isn't the correct syntax but you'd have like:


Diamond (Account) --squigle -- box (Entry) -- bunch of lines to (uID), (name), (firstdate),(lastdate),(birthday),(balance), etc, with maybe othe boxes named (Product) that have lines and squiggles to various things maybe pointing back to the "Account" box so you'd have a map between between your Product's Best Friend's College Roomate's Dog and the Account's Name's Numerological Report as Indexed by Astrological sign. Sometime they're in pretty colors.

haha that pretty much sums it up.

When I do my informal sketches I don't spell out relationship types when they are obvious, and most of the time they are. They tend to look similar in style to this, though typically with less detail (I usually omit data types and most fields that are not relevant to the relationships):
http://www.ofset.org/uploadfiles/60/image/gnuedu.png

Looks like busywork to me, but I know manager types dig pictures. I think I'd need a class just to know how to read it.

There are 2 main types of ERD. One is logical, and the other is physical. Palarran's link is a physical one, where it shows the datatypes (and sizes where appropriate). The wikipedia article (http://en.wikipedia.org/wiki/Entity-relationship_model) has a link to a logical (http://en.wikipedia.org/wiki/Image:ER_Diagram_MMORPG.png) model. Almost no one remembers what those little crows feet and circles mean, so you'll always look them up, but they make it far easier to graphically explain things like "an account can have many characters" and "a character can belong to one and only one account" or "an author is a contributor" or "a skill can have many keywords and a keyword can be associated with many skills."

Logical diagrams are pretty useful with the business users because they'll usually get lost in "one and only one... wah?" But the pictures make sense to almost anyone who doesn't lower your IQ when you talk to them. The physical diagrams make sense only to another dev or DBA, so those get hidden from the users.

Most higher end ER tools let you also estimate how big the DB is going to be, and how big things will get with various combinations of indices. Yes, that is more of a DBA role, but my current employer won't hire a full-time DBA and thus every software dev has to be the DBA for their own project. One of the projects on my plate involves some huge (for us) database (about 1 terabyte) and there not only is no database server in our company with that much disk space (which the pointy haired bosses don't want to believe), but there is further no disk in the company large enough to hold the back ups (policy is that we keep 7 days of full back ups on disk, so that each backup tape grabs a week of data backups). They also refuse to authorize purchasing a disk that's big enough. We've wasted far more than the $200 that a 1T disk would cost in meetings about why that project is stalled.

Most higher end ER tools let you also estimate how big the DB is going to be, and how big things will get with various combinations of indices. Yes, that is more of a DBA role, but my current employer won't hire a full-time DBA and thus every software dev has to be the DBA for their own project. One of the projects on my plate involves some huge (for us) database (about 1 terabyte) and there not only is no database server in our company with that much disk space (which the pointy haired bosses don't want to believe), but there is further no disk in the company large enough to hold the back ups (policy is that we keep 7 days of full back ups on disk, so that each backup tape grabs a week of data backups). They also refuse to authorize purchasing a disk that's big enough. We've wasted far more than the $200 that a 1T disk would cost in meetings about why that project is stalled.


The idea of being able to see how large a DB will grow as well as the indices might be beneficial. But, I'm wondering how much effort/time is necessary to get your existing data into one of these models?

Also, please tell me where you're buying 1TB for $200. I just got this quote yesterday for some "used" 400GB drives for one of my older SANs.

Qty. PART No. DESCRIPTION UNIT PRICE AMOUNT

1 4603 400GB 7.2K SATA Drive (Used) $778
1 Shipping charge per drive $50

TOTAL $828.00


I can tell you for our really large oracle databases use RMAN and go right to tape.


Anyway back to predicting space. I'm in a quandry as a SAN admin. One of our databases the most important one is using RAW logical volumes. From the OS perspective when I make these LVs and give them to my DBAs they look like they are used up but from the OS I have no way of knowing just how "used" they are. I'm no DBA but I do have a few sneaky tricks to keep them in line. My storage is costly b/c of licenses for mirrors, flash copies, and TPC, etc. I have to keep them under thumb or they'd go nutty. Anyway, currently we have a set number of sizes for their LVs (data and indexes) we keep them as usuable scratches for them but I suspect we're making too many. I wonder how I can see what is in use and what is growing the fastest?

I have a little cheat sql script but it doesn't tell me what I need to know. How are you guys managing this stuff and projecting growth? This is something my company is never good at we just throw more storage and money at it. Now we have so many copies of this DB it's beyond costly, prod, a cert, standby, and DR so yes 4.

Anyway this is the output of my script, I'm more than willing to accept suggestions :) Formatting sucks and yes, each logical volume is a multiplier of 64M meaning the smallest possible size is 64M. This is an OS setting on the volume group and one the vendor made us do, believe me I see so much wasted space I want to smack Cerner but there's nothing I can do :(

Connected to:
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.5.0 - Production

Date - Wednesday 18th June 2008 11:24:42
Database Name -
Username -

Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
PL/SQL Release 9.2.0.5.0 - Production
CORE 9.2.0.6.0 Production
TNS for IBM/AIX RISC System/6000: Version 9.2.0.5.0 - Production
NLSRTL Version 9.2.0.5.0 - Production

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CALLCENTER 66,060,288 65,536 65,994,752
.1
D_DISCERN_LOG 66,060,288 65,536 65,994,752
.1
D_DMS_MEDIA_TA8232 66,060,288 65,536 65,994,752
.1
D_PROCALL 66,060,288 65,536 65,994,752
.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_OMF_SMR 66,060,288 65,536 65,994,752
.1
D_OMF_SM 66,060,288 65,536 65,994,752
.1
I_CALLCENTER 66,060,288 65,536 65,994,752
.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_DMS_MEDIA_TA8232 66,060,288 65,536 65,994,752
.1
I_OMF_SMR 66,060,288 65,536 65,994,752
.1
I_PROCALL 66,060,288 65,536 65,994,752
.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_OMF_SM 66,060,288 65,536 65,994,752
.1
I_DISCERN_LOG 66,060,288 65,536 65,994,752
.1
D_BMDI_ACQUIRE8836 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_DMS_MEDIA_ID0486 66,060,288 131,072 65,929,216
.2
D_CDS_BATCH_CO0473 66,060,288 131,072 65,929,216
.2
D_CE_DYNAMIC_L2000 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_DR_RO 66,060,288 131,072 65,929,216
.2
D_ENCOUNTER_ALIAS 66,060,288 131,072 65,929,216
.2
D_PFT_REVENUE_8504 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_PFT_BALANCE8810 66,060,288 131,072 65,929,216
.2
D_ORDER_RECON_1263 66,060,288 131,072 65,929,216
.2
D_ORDER_RECON1262 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_ORDER_COMPLI1261 66,060,288 131,072 65,929,216
.2
D_ORDER_COMPLI1260 66,060,288 131,072 65,929,216
.2
D_ORDERS_SPECIMEN 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_OMF_UM 66,060,288 131,072 65,929,216
.2
D_MRNET 66,060,288 131,072 65,929,216
.2
I_ENCOUNTER_ALIAS 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_WH_RC_CLN_AREA 66,060,288 131,072 65,929,216
.2
D_SHR_PERSON 66,060,288 131,072 65,929,216
.2
D_SA_PARAMETER7913 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_RESULT 66,060,288 131,072 65,929,216
.2
D_RC_F_REVENUE 66,060,288 131,072 65,929,216
.2
D_RC_F_CLAIM_EVENT 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_PROFILE_TASK_R 66,060,288 131,072 65,929,216
.2
D_PM_POST_DOC0061 66,060,288 131,072 65,929,216
.2
I_SA_PARAMETER7913 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_MEDNET 66,060,288 131,072 65,929,216
.2
I_IQHOLAP 66,060,288 131,072 65,929,216
.2
I_FLEXTOOL 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_MEDNET 66,060,288 131,072 65,929,216
.2
D_IQHOLAP 66,060,288 131,072 65,929,216
.2
D_GS_MED_CLAIM9146 66,060,288 131,072 65,929,216
.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_FLEXTOOL 66,060,288 131,072 65,929,216
.2
D_ENCNTR_SLICE8895 66,060,288 131,072 65,929,216
.2
D_ASSAY_PROCESSING_R 66,060,288 196,608 65,863,680
.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CPO 66,060,288 196,608 65,863,680
.3
D_HEA 66,060,288 196,608 65,863,680
.3
I_WH_D_MEDIUM 66,060,288 196,608 65,863,680
.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_SHR_PERSON 66,060,288 196,608 65,863,680
.3
I_SERVICE_DIRECTORY 66,060,288 196,608 65,863,680
.3
I_RESULT 66,060,288 196,608 65,863,680
.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ESO_REF 66,060,288 196,608 65,863,680
.3
I_DISCERN_REF_LOG 66,060,288 196,608 65,863,680
.3
D_WH_F_MEDIUM 66,060,288 196,608 65,863,680
.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_WH_D_LARGE 66,060,288 196,608 65,863,680
.3
D_PROTOCOL_DEF 66,060,288 196,608 65,863,680
.3
D_INFRA 66,060,288 196,608 65,863,680
.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_I18N 66,060,288 196,608 65,863,680
.3
D_DISCERN_REF_LOG 66,060,288 196,608 65,863,680
.3
D_ESO_REF 66,060,288 196,608 65,863,680
.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_DMS_MEDIA_IN8231 66,060,288 196,608 65,863,680
.3
D_BR_BB_PRODCA0519 66,060,288 262,144 65,798,144
.4
D_BR_BB_PRODUC0522 66,060,288 262,144 65,798,144
.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_BR_COLL_CLAS9224 66,060,288 262,144 65,798,144
.4
I_PROTOCOL_DEF 66,060,288 262,144 65,798,144
.4
I_ORDER_RECON_1263 66,060,288 262,144 65,798,144
.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ORDER_RECON1262 66,060,288 262,144 65,798,144
.4
I_ORDER_COMPLI1261 66,060,288 262,144 65,798,144
.4
I_ORDER_COMPLI1260 66,060,288 262,144 65,798,144
.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_GS_MED_CLAIM9146 66,060,288 262,144 65,798,144
.4
I_ENCNTR_SLICE8895 66,060,288 262,144 65,798,144
.4
D_WH_D_MEDIUM 66,060,288 262,144 65,798,144
.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_OMF_BATCH 66,060,288 327,680 65,732,608
.5
I_CPO 66,060,288 327,680 65,732,608
.5
I_MRNET 66,060,288 327,680 65,732,608
.5

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_I18N 66,060,288 327,680 65,732,608
.5
I_OMF_BATCH 66,060,288 327,680 65,732,608
.5
L_A_SMALL 66,060,288 327,680 65,732,608
.5

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_WH_RC_CLN_AREA 66,060,288 327,680 65,732,608
.5
I_PROFILE_TASK_R 66,060,288 327,680 65,732,608
.5
D_WH_F_SMALL 66,060,288 393,216 65,667,072
.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_HEA 66,060,288 393,216 65,667,072
.6
I_BMDI_ACQUIRE8836 66,060,288 393,216 65,667,072
.6
I_CE_DYNAMIC_L2000 66,060,288 393,216 65,667,072
.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_ARC_LARGE 66,060,288 458,752 65,601,536
.7
D_MMR 66,060,288 458,752 65,601,536
.7
D_ORDERS_RESULTS 66,060,288 458,752 65,601,536
.7

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ASSAY_PROCESSING_R 66,060,288 458,752 65,601,536
.7
I_RC_F_CLAIM_EVENT 66,060,288 458,752 65,601,536
.7
I_LOCATION 66,060,288 458,752 65,601,536
.7

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CMT_CONCEPT_7688 66,060,288 458,752 65,601,536
.7
I_CDS_BATCH_CO0473 66,060,288 458,752 65,601,536
.7
I_BR_COLL_CLAS9224 66,060,288 458,752 65,601,536
.7

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_ACCESSION 66,060,288 524,288 65,536,000
.8
I_INFRA 66,060,288 524,288 65,536,000
.8
TOOLS 66,060,288 524,288 65,536,000
.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CMT_CONCEPT_7688 66,060,288 589,824 65,470,464
.9
I_ORDERS_SPECIMEN 66,060,288 589,824 65,470,464
.9
L_R_SMALL 66,060,288 589,824 65,470,464
.9

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_REF_RANGE_FACTOR 66,060,288 589,824 65,470,464
.9
I_RC_F_REVENUE 66,060,288 589,824 65,470,464
.9
I_MMR 66,060,288 589,824 65,470,464
.9

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_PURGE_ARCHIVE 66,060,288 655,360 65,404,928
1.0
I_BR_BB_PRODCA0519 66,060,288 655,360 65,404,928
1.0
I_WH_D_LARGE 66,060,288 655,360 65,404,928
1.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_BR_BB_PRODUC0522 66,060,288 655,360 65,404,928
1.0
I_ARC_LARGE 66,060,288 655,360 65,404,928
1.0
D_SERVICE_DIRECTORY 66,060,288 655,360 65,404,928
1.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CN_OMF 66,060,288 720,896 65,339,392
1.1
D_OMF_RAD 66,060,288 720,896 65,339,392
1.1
D_SIT 66,060,288 720,896 65,339,392
1.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_DISCERN_DYN 535,822,336 5,963,776 529,858,560
1.1
D_LOCATION 66,060,288 786,432 65,273,856
1.2
D_WH_F_LARGE 66,060,288 786,432 65,273,856
1.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_COLLECT 66,060,288 851,968 65,208,320
1.3
D_PFTOMF 66,060,288 917,504 65,142,784
1.4
I_PURGE_ARCHIVE 66,060,288 917,504 65,142,784
1.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_WH_F_MEDIUM 66,060,288 917,504 65,142,784
1.4
D_OPF 66,060,288 983,040 65,077,248
1.5
I_WH_F_SMALL 66,060,288 983,040 65,077,248
1.5

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ACCESSION 66,060,288 1,048,576 65,011,712
1.6
I_PFT_BALANCE8810 66,060,288 1,048,576 65,011,712
1.6
D_RRD 66,060,288 1,114,112 64,946,176
1.7

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_OPF 66,060,288 1,114,112 64,946,176
1.7
I_DISCERN_DYN 535,822,336 9,895,936 525,926,400
1.8
D_WH_D_SMALL 66,060,288 1,245,184 64,815,104
1.9

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CLINICAL_IMAGING 66,060,288 1,376,256 64,684,032
2.1
D_MMC 66,060,288 1,376,256 64,684,032
2.1
I_OMF_UM 66,060,288 1,507,328 64,552,960
2.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_WH_D_SMALL 66,060,288 1,507,328 64,552,960
2.3
D_AP_REF 66,060,288 1,572,864 64,487,424
2.4
I_PFT_REVENUE_8504 66,060,288 1,572,864 64,487,424
2.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ORDERS_RESULTS 66,060,288 1,572,864 64,487,424
2.4
D_PATHNET 66,060,288 1,638,400 64,421,888
2.5
I_SIT 66,060,288 1,638,400 64,421,888
2.5

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_OEN 66,060,288 1,835,008 64,225,280
2.8
D_QC 66,060,288 1,966,080 64,094,208
3.0
I_ALPHA_RESPONSES 66,060,288 1,966,080 64,094,208
3.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_AP_REF 66,060,288 1,966,080 64,094,208
3.0
I_RRD 66,060,288 1,966,080 64,094,208
3.0
D_PROCEDURE_DIR_2 66,060,288 2,031,616 64,028,672
3.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_OMF_RAD 66,060,288 2,031,616 64,028,672
3.1
I_PROCEDURE_DIR_2 66,060,288 2,031,616 64,028,672
3.1
D_REF_RANGE_FACTOR 66,060,288 2,162,688 63,897,600
3.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_DISCERN 2,146,435,072 72,876,032 2,073,559,040
3.4
I_DISCERN 1,072,693,248 37,879,808 1,034,813,440
3.5
I_COLLECT 66,060,288 2,359,296 63,700,992
3.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_OUTREACH 66,060,288 3,014,656 63,045,632
4.6
D_ALPHA_RESPONSES 66,060,288 3,276,800 62,783,488
5.0
D_EEM 66,060,288 3,276,800 62,783,488
5.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_IQHEALTH 66,060,288 3,276,800 62,783,488
5.0
D_CATALYST 66,060,288 3,407,872 62,652,416
5.2
I_QC 66,060,288 3,407,872 62,652,416
5.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_MEMBER 133,169,152 6,946,816 126,222,336
5.2
I_CN_OMF 66,060,288 3,670,016 62,390,272
5.6
I_CATALYST 66,060,288 3,932,160 62,128,128
6.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CLINICAL_IMAGING 66,060,288 3,997,696 62,062,592
6.1
I_MEMBER 66,060,288 4,194,304 61,865,984
6.3
I_PFTOMF 66,060,288 4,259,840 61,800,448
6.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
UNDO1 51,533,316,096 3,566,731,264 47,966,584,832
6.9
I_PATHNET 66,060,288 4,653,056 61,407,232
7.0
D_AP_DATA 66,060,288 4,915,200 61,145,088
7.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_WH_F_LARGE 66,060,288 5,111,808 60,948,480
7.7
D_CQM_BMDI_RES8835 66,060,288 5,308,416 60,751,872
8.0
D_DMS_MEDIA_XR8611 66,060,288 5,308,416 60,751,872
8.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_OUTREACH 66,060,288 5,373,952 60,686,336
8.1
D_HLA 66,060,288 6,029,312 60,030,976
9.1
I_IQHEALTH 66,060,288 6,488,064 59,572,224
9.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_REORG_TOOL 66,060,288 6,815,744 59,244,544
10.3
I_ESO 1,072,693,248 112,132,096 960,561,152
10.5
I_MMC 66,060,288 7,536,640 58,523,648
11.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CERNER_STATS 535,822,336 61,145,088 474,677,248
11.4
I_OEN 267,386,880 34,537,472 232,849,408
12.9
D_ESI 2,146,435,072 302,907,392 1,843,527,680
14.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_BLOODBANK 66,060,288 9,568,256 56,492,032
14.5
D_MICRO 66,060,288 10,027,008 56,033,280
15.2
D_RADIO 66,060,288 10,027,008 56,033,280
15.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_EEM 66,060,288 10,158,080 55,902,208
15.4
D_UMLS 17,177,772,032 2,691,760,128 14,486,011,904
15.7
I_HLA 66,060,288 10,616,832 55,443,456
16.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_DMS_MEDIA_IN8231 66,060,288 11,141,120 54,919,168
16.9
I_AP_DATA 66,060,288 11,403,264 54,657,024
17.3
D_REORG_TOOL 66,060,288 13,041,664 53,018,624
19.7

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_ESO 535,822,336 109,838,336 425,984,000
20.5
D_PROFIT 66,060,288 14,548,992 51,511,296
22.0
I_R_SMALL 667,942,912 160,301,056 507,641,856
24.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_DMS_MEDIA_XR8611 66,060,288 15,990,784 50,069,504
24.2
MISC 535,822,336 131,858,432 403,963,904
24.6
I_CQM 534,773,760 144,179,200 390,594,560
27.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
STATSPACK 8,587,837,440 2,316,828,672 6,271,008,768
27.0
I_MICRO 66,060,288 18,415,616 47,644,672
27.9
D_PERSONNEL 66,060,288 18,612,224 47,448,064
28.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_R_MEDIUM 1,873,805,312 542,113,792 1,331,691,520
28.9
I_UMLS 534,773,760 157,876,224 376,897,536
29.5
I_RADIO 66,060,288 20,316,160 45,744,128
30.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ESI 266,338,304 82,313,216 184,025,088
30.9
I_CQM_BMDI_RES8835 66,060,288 21,037,056 45,023,232
31.8
D_BEDROCK 66,060,288 21,102,592 44,957,696
31.9

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_PERSONNEL 66,060,288 21,495,808 44,564,480
32.5
I_SCHED 2,146,435,072 704,446,464 1,441,988,608
32.8
D_A_LARGE 66,060,288 22,216,704 43,843,584
33.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_SCHED 2,146,435,072 776,339,456 1,370,095,616
36.2
I_OMF 8,587,837,440 3,152,543,744 5,435,293,696
36.7
I_PRSNL_RELTN_8245 2,145,386,496 852,885,504 1,292,500,992
39.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_PERSON_NAME 4,292,870,144 1,775,697,920 2,517,172,224
41.4
D_A_SMALL 66,060,288 27,721,728 38,338,560
42.0
D_DCP 4,292,870,144 1,821,573,120 2,471,297,024
42.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_NOMEN 4,292,870,144 1,843,068,928 2,449,801,216
42.9
L_A_LARGE 66,060,288 28,442,624 37,617,664
43.1
I_PROFILE 4,292,870,144 1,877,147,648 2,415,722,496
43.7

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_MULTM_LOAD 132,120,576 58,064,896 74,055,680
43.9
I_MAT_MGT_2 534,773,760 236,060,672 298,713,088
44.1
D_HLTHPLAN 133,169,152 59,113,472 74,055,680
44.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CE_BLOB 2,145,386,496 953,679,872 1,191,706,624
44.5
D_CODE_VALUE 66,060,288 29,556,736 36,503,552
44.7
D_OMF 4,293,918,720 1,967,194,112 2,326,724,608
45.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_HLTHPLAN 266,338,304 124,387,328 141,950,976
46.7
D_R_SMALL 399,507,456 188,809,216 210,698,240
47.3
D_PERSON_1 8,587,837,440 4,060,217,344 4,527,620,096
47.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_BLOODBANK 66,060,288 32,243,712 33,816,576
48.8
I_R_MEDIUM 1,070,596,096 523,108,352 547,487,744
48.9
D_ORGANIZATION 1,072,693,248 526,057,472 546,635,776
49.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_OTG 2,145,386,496 1,053,032,448 1,092,354,048
49.1
I_CODE 534,773,760 264,634,368 270,139,392
49.5
I_BEDROCK 66,060,288 33,751,040 32,309,248
51.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ENCOUNTER 8,588,886,016 4,406,116,352 4,182,769,664
51.3
D_CE_MISC 1,071,644,672 565,182,464 506,462,208
52.7
D_MAT_MGT_1 132,120,576 70,713,344 61,407,232
53.5

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_SN 4,292,870,144 2,308,767,744 1,984,102,400
53.8
D_ENCNTR_PRSNL_RELTN 12,882,804,736 7,046,561,792 5,836,242,944
54.7
D_MAT_MGT_2 266,338,304 146,210,816 120,127,488
54.9

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CODE 6,439,305,216 3,551,526,912 2,887,778,304
55.2
D_ENCNTR_ALIAS 8,588,886,016 4,765,777,920 3,823,108,096
55.5
D_ENCOUNTER 17,177,772,032 9,664,004,096 7,513,767,936
56.3

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ORGANIZATION 535,822,336 304,742,400 231,079,936
56.9
I_ORDER_DETAIL 25,766,658,048 14,898,364,416 10,868,293,632
57.8
I_PERSON_1 8,588,886,016 4,985,847,808 3,603,038,208
58.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_PRSNL_RELTN_8245 534,773,760 310,509,568 224,264,192
58.1
I_CE_MISC 25,766,658,048 15,119,876,096 10,646,781,952
58.7
I_PERSON_MISC 17,177,772,032 10,119,282,688 7,058,489,344
58.9

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CE_RESULTS 17,177,772,032 10,180,362,240 6,997,409,792
59.3
D_PERSON_NAME 4,293,918,720 2,550,267,904 1,743,650,816
59.4
I_PHARMACY 38,648,414,208 23,250,010,112 15,398,404,096
60.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_TASKLIST 2,145,386,496 1,291,649,024 853,737,472
60.2
I_A_LARGE 66,060,288 39,780,352 26,279,936
60.2
I_MAT_MGT_1 66,060,288 39,976,960 26,083,328
60.5

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_PROFILE 4,293,918,720 2,615,607,296 1,678,311,424
60.9
I_NOMEN 4,293,918,720 2,654,404,608 1,639,514,112
61.8
I_ENCNTR_ALIAS 4,293,918,720 2,657,550,336 1,636,368,384
61.9

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_DM_CHG_LOG7773 66,060,288 42,008,576 24,051,712
63.6
I_A_MEDIUM 8,587,837,440 5,558,239,232 3,029,598,208
64.7
I_MULTUM 66,060,288 42,795,008 23,265,280
64.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_TRACKING 1,607,467,008 1,047,330,816 560,136,192
65.2
I_PHARM_MGMT 25,766,658,048 16,881,221,632 8,885,436,416
65.5
SYSTEM 535,822,336 357,040,128 178,782,208
66.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_A_MEDIUM 4,292,870,144 2,902,982,656 1,389,887,488
67.6
I_PERSON 12,882,804,736 8,750,694,400 4,132,110,336
67.9
I_ENCOUNTER_MISC 17,177,772,032 11,788,288,000 5,389,484,032
68.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_SN 2,146,435,072 1,473,314,816 673,120,256
68.6
D_ENCOUNTER_MISC 21,471,690,752 14,851,768,320 6,619,922,432
69.2
I_SYS_MGMT 6,440,353,792 4,507,172,864 1,933,180,928
70.0

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_SCD 4,290,772,992 3,019,374,592 1,271,398,400
70.4
D_PROCEDURE_DIR 66,060,288 46,596,096 19,464,192
70.5
I_PROCEDURE_DIR 66,060,288 47,054,848 19,005,440
71.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_MULTUM 66,060,288 47,251,456 18,808,832
71.5
I_MULTM_LOAD 66,060,288 47,448,064 18,612,224
71.8
D_PERSON_MISC 17,177,772,032 12,464,685,056 4,713,086,976
72.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_PROFIT 66,060,288 48,037,888 18,022,400
72.7
D_ORDERS 25,766,658,048 18,859,622,400 6,907,035,648
73.2
I_PM 4,293,918,720 3,195,731,968 1,098,186,752
74.4

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_CHART 267,386,880 199,491,584 67,895,296
74.6
I_ENCNTR_PRSNL_RELTN 8,588,886,016 6,417,350,656 2,171,535,360
74.7
D_TRACKING 1,071,644,672 801,767,424 269,877,248
74.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CHART 267,386,880 202,309,632 65,077,248
75.7
D_CE_RESULTS 30,060,576,768 22,894,870,528 7,165,706,240
76.2
D_ORDERS_MISC 42,944,430,080 32,723,632,128 10,220,797,952
76.2

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CODE_VALUE 66,060,288 50,593,792 15,466,496
76.6
D_PM 8,588,886,016 6,591,610,880 1,997,275,136
76.7
D_CQM 34,355,544,064 26,482,245,632 7,873,298,432
77.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_A_SMALL 66,060,288 51,773,440 14,286,848
78.4
I_DCP 3,218,079,744 2,522,742,784 695,336,960
78.4
I_ORDERS_MISC 30,059,528,192 23,680,188,416 6,379,339,776
78.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_SYS_MGMT 8,588,886,016 6,779,109,376 1,809,776,640
78.9
D_CE_EVENT 85,888,860,160 68,899,569,664 16,989,290,496
80.2
D_SCD 6,439,305,216 5,190,320,128 1,248,985,088
80.6

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_ORDERS 38,648,414,208 31,493,914,624 7,154,499,584
81.5
I_TASKLIST 5,363,466,240 4,410,966,016 952,500,224
82.2
D_PHARM_MGMT 17,175,674,880 14,277,672,960 2,898,001,920
83.1

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
D_ORDER_DETAIL 42,944,430,080 37,111,529,472 5,832,900,608
86.4
D_CE_BLOB 137,422,176,256 120,193,024,000 17,229,152,256
87.5
I_PRICE 77,297,876,992 67,770,318,848 9,527,558,144
87.7

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CE_EVENT 154,599,948,288 135,987,200,000 18,612,748,288
88.0
D_CLINICAL_EVENT 137,422,176,256 121,870,745,600 15,551,430,656
88.7
D_PRICE 90,180,681,728 80,070,377,472 10,110,304,256
88.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
I_CLINICAL_EVENT 197,544,378,368 180,667,023,360 16,877,355,008
91.5
D_PERSON 124,535,177,216 114,097,061,888 10,438,115,328
91.6
D_PHARMACY 309,199,896,576 290,181,677,056 19,018,219,520
93.8

Tablespace Name Bytes Used Free
-------------------- ------------------ ------------------ ----------------
%
Used
------
------------------ ------------------ ----------------

sum 2,115,359,473,664 1,665,093,337,088 450,266,136,576

298 rows selected.
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.5.0 - Production
oracle on cdb1>

The idea of being able to see how large a DB will grow as well as the indices might be beneficial. But, I'm wondering how much effort/time is necessary to get your existing data into one of these models?


Well, if you have something like Toad, it can do that for you based on your current data without any pretty pictures in the process.


Also, please tell me where you're buying 1TB for $200. I just got this quote yesterday for some "used" 400GB drives for one of my older SANs.


He's probably throwing a SATA drive on a bsd/linux machine.

As for estimating DB size, make your DBAs do their f'n jobs and tell you, and when they run out, tell them it's their fault and quote their original mail back to them :> Works for us.

I think pretty much any decent tool these days goes two-way with a database schema.

As for estimating DB size, make your DBAs do their f'n jobs and tell you, and when they run out, tell them it's their fault and quote their original mail back to them :> Works for us.

Yar we do that usually, however if this dB goes down it's all of IS's fault from the organization's perspective. We actually aren't "out of space" I think we're over allocating for them but I can't be sure b/c I don't know and they won't tell us. :p

Now that I have to allocate LVs in three places each time I add space I'd like to be sure I have a better grasp on what they're doing. The other copy is synchronous but still it's another copy.

Thanks for the info on Toad, I'll look it up and see what I can find.

Sorry, yeah. Simple little SATA drive for the older decrepit servers (originally I had been allowed an older ML370 for my large database server, but since the hard drives for it cost a fortune, I now get a 3 year old desktop machine).

We've wasted far more than the $200 that a 1T disk would cost in meetings about why that project is stalled.

This. Is. Classic.
This is when you offer up your managers job to pay for the cheap hardware it takes to get your work done.

Realistically, if the "time it takes to engineer a solution that takes less than 7 terrabytes costs more than 8 terrabyte SAN + new server" argument doesn't work, it's time to suggest that all team members use up their vacation time until the hardware is delivered and on site. :)