Search /
Docfinder:
Advanced search  |  Help  |  Site map
RESEARCH CENTERS
SITE RESOURCES
Click for Layer 8! No, really, click NOW!
Networking for Small Business
TODAY'S NEWS
Apple tops the $100B+ tech club
How to get the IRS' attention: Forge nearly $8 million in tax returns, steal identities
Microsoft details Windows 8 for ARM devices
Blogger exposes major Google Wallet security flaw
Web app lets enterprise set security, sharing for Google Apps users
Cloudscaling to offer OpenStack private cloud platform
Valentine's Day Patch Tuesday: Microsoft to issue 9 patches, 4 critical
Mobile World Congress sneak peek: Quad-core smartphones, Ice Cream Sandwich & more
Microsoft details 'Windows on ARM' program
March debut of 'iPad 3' a sure bet, says analyst
Resume Makeover: How an Information Security Professional Can Target CSO Jobs
FBI unbolts Steve Jobs 1991 investigation file
Cisco boosted profit, sales in Q2 while cutting costs
Macs take on the enterprise
/

Directories vs. relational databases

Related linksToday's breaking news
Send to a friendFeedback

Sign up to receive this and other networking newsletters in your inbox.

"A directory is just a special-purpose database" is a truism I hear everyday. It's usually spoken by someone who wants to use Oracle, Sybase, SQL Server or another relational database management system to store information about users, platforms, applications or infrastructure items that are normally stored in the directory. It's often a relational DBMS administrator or a programmer saying this.

On the other hand, I frequently am asked why financial or order entry data can't be stored in the directory to ease browsing the information. This often comes from directory or Web server administrators looking to ease the load on their servers or other resources (such as their own database administration skills).

What both groups are forgetting is that a relational DBMS is also a "special-purpose database." We need to remember that a computer database is simply a file or group of files used to store data. A list of names and phone numbers written up in a text editor is a database, but it certainly isn't a directory or a relational DBMS.

Every special-purpose database is designed and structured to perform its special purpose optimally. A relational DBMS is designed to let items of data be related to one another either permanently or on an ad hoc basis, while a directory service uses the object-oriented style of database (with its built-in hierarchy) to create a database supporting a tree-like view of the data.

Using a directory for relational data or a relational DBMS for directory data is like using a hammer to cut wood: It can be done, but a real carpenter wouldn't do it.

RELATED LINKS

Dave Kearns is a writer and consultant in Silicon Valley. His most recent book is "Peter Norton's Complete Guide to Networks" published by SAMS. Dave's company, Virtual Quill, provides content services to network vendors: books, manuals, white papers, lectures and seminars, marketing, technical marketing and support documents. Virtual Quill provides "words to sell by..." Find out more at Virtual Quill or by e-mail at info@vquill.com

Directories archive
Past newsletters.

Whatis.com: Relational database

More on relational databases from KnowledgePool

Archive of Network World on Directories newsletters


NWFusion offers more than 40 FREE technology-specific email newsletters in key network technology areas such as NSM, VPNs, Convergence, Security and more.
Click here to sign up!
New Event - WANs: Optimizing Your Network Now.
Hear from the experts about the innovations that are already starting to shake up the WAN world. Free Network World Technology Tour and Expo in Dallas, San Francisco, Washington DC, and New York.
Attend FREE
Your FREE Network World subscription will also include breaking news and information on wireless, storage, infrastructure, carriers and SPs, enterprise applications, videoconferencing, plus product reviews, technology insiders, management surveys and technology updates - GET IT NOW.