Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Call That a Database? This is a Database.


Call That a Database? This is a Database.

Author
Message
simonball
simonball
Forum Newbie
Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: General Forum Members
Points: 2 Visits: 40
pbowman-543344 (2/27/2012)
diddybase - < 1Gb, especially the "test" or "proof of concept" databases, beloved of developers, with less than 10,000 records in each table, or with an entire dataset < available RAM.

terrorbase - Terabytes. Lots of em.

But I agree with Phil, the biggest lack is words for proper OLTP systems with hundreds/thousands of simultaneous processes needing to do non-repudiable, acid-compliant transactions without deadlocking. Think stock exchanges or other trading platforms.


Love Diddybase!

suggestion for an Online transactransaction mega massive database?

an Oltrabase? or an Oltra Mega-base

me:"Emily! We do not pull the wallpaper off the walls!"
Emily (aged 3)<sulkily mumbles>:"We do because we can."

Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36344 Visits: 18752
Great one, Phil, and we certainly need better terms. This large/very large, isn't a good choice as that will constantly evolve. Made up words that describe size, scale, or even rate of transactions, would be better.

Provided that we don't try to be marketers and create words that imply we've ever reached some limit, like the Ultimabase or something similar.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
JimBama08
JimBama08
Grasshopper
Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)Grasshopper (22 reputation)

Group: General Forum Members
Points: 22 Visits: 195
Great topic. I think there's a perfect metaphor around highway interchanges. I particularly like this description of so-called stack interchanges: "This is not only expensive but also creates an eyesore among local residents, leading to considerable NIMBY (Not In My Back Yard) opposition. Large stacks with multiple levels are often colloquially described as Mixmasters or spaghetti bowls due to their complex appearance, being compared to boiled spaghetti." So perhaps something like this works:

CASE
WHEN DatabaseSize > 1Tb and Concurrency > 1000
THEN 'CloverStack'
WHEN DatabaseSize BETWEEN 100Gb AND 1Tb and Concurrency > 500
THEN 'CloverLeaf'
WHEN DatabaseSize BETWEEN 1Gb AND 100Gb and Concurrency > 50
THEN 'Roundabout'
WHEN DatabaseSize BETWEEN 1Mb AND 1Gb and Concurrency < 20
THEN 'Mayberry'
END as DatabaseClass

I'm sure there are holes in my CASE statement, but there are tons of possibilities. And when you think about it we're trying to keep everything flowing as best we can with unpredictable inputs (volume of traffic, size of vehicles, weather conditions, etc.), a limited budget and specs that change after the infrastructure has been hardened.

Great topic.

~~ Everything in moderation, including moderation. ~~
Phil Factor
Phil Factor
Right there with Babe
Right there with Babe (754 reputation)Right there with Babe (754 reputation)Right there with Babe (754 reputation)Right there with Babe (754 reputation)Right there with Babe (754 reputation)Right there with Babe (754 reputation)Right there with Babe (754 reputation)Right there with Babe (754 reputation)

Group: General Forum Members
Points: 754 Visits: 2950
I've just used the term 'unCoddly' for a database that had all sorts of de-normalisations in it.
As regarding having to remember the types of database, we all find it easy to remember the sixty names of types of dog. It is just as well, considering that there is a huge difference between a Chihuahua and a Great Dane.


Best wishes,

Phil Factor
Simple Talk
Tony Palmeri
Tony Palmeri
Grasshopper
Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)Grasshopper (17 reputation)

Group: General Forum Members
Points: 17 Visits: 125
Here's my two cents, FWIW: The fault for the effects of poor communication does not fall on the English language for it's lack of overly specific terminology. The fault lies with every one of us, who uses terms like "database" ambiguously. If you *mean* something like MS-Access running on a local workstation, say so. If you *mean* something like a mega/giga/tera-OLTP, say so. We have the words... use them.

This has always been one of my pet peaves.... Too often, the speaker/writer has a fully formed specific idea of what he is talking about and in his own mind he knows what he, himself, specifically means by a word like "database" - - - but he fails to take into account the the context of the listener/reader with whom he is endeavoring to communicate. I always try to be concsious of ambiguities in certain terminology, and to explicitly resolve the specifics in my communication wherever warranted.

Most miscommunication that I see happening comes BOTH from speakers *and* listeners failing to notice (even fairly obvious) abiguities in their words.

For example, if there is *ANY* chance that the listener/reader might interpret my use of the word "database" as something like MS-Access, when I really mean something like SQL Server, .... *and* if that difference is germane to the discussion, I'll try to be very explicit in what I am talking about and why it is a relevant distinction.

I don't think we need to invent new words for this. In fact, I think it might actually be counter-productive because there are SO many combinations and permutations of database features, scopes, scales, etc... that we'd end up with such a proliferation of new words, they would only confuse things further.
gserdijn
gserdijn
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1341 Visits: 816
A few things come to mind when reading the article.

1. Kate Bush's album '50 Words for Snow' - excellent stuff.
2. An uncle talking about his database containing a few hundred records. 'Oh, yes, databases, I have one too...'
3. Crocodile Dundee: Michael J. "Crocodile" Dundee: [chuckling] That's not a knife. [draws a large Bowie knife] That's a knife.

The simple distinctions I make:
Small databases: sandboxes
Critical databases: handle with care-databases

Nice article.



Dutch Anti-RBAR League
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21143 Visits: 18259
InOverYourHeadBase



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

pdanes
pdanes
SSC-Addicted
SSC-Addicted (446 reputation)SSC-Addicted (446 reputation)SSC-Addicted (446 reputation)SSC-Addicted (446 reputation)SSC-Addicted (446 reputation)SSC-Addicted (446 reputation)SSC-Addicted (446 reputation)SSC-Addicted (446 reputation)

Group: General Forum Members
Points: 446 Visits: 1350
SQLRNNR (2/28/2012)
InOverYourHeadBase

Boy, do I have the corner on those.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search