Does it matter if the end user knows what the database is?
Recently I got a wonderful view of a database from the end user perspective.
While I was traveling I had found a restaurant where I had decided to let friends who live locally know where I was at. Part way through my food I got a message from a local friend that said "Don't eat there, their food always makes people sick!"
"Always" is a word that I would think would be a little too strong when applied to a restaurant, right?
Nope, the next day I got to feel the full truth of the word.
A couple of days later I am telling some friends about this and a local asked me "Where was this, I want to avoid them." I didn't get asked this question once, I got it asked a dozen times.
I don't know where the place is. Why is that? Because the system I was using lost the entire day worth of my data. I don't know how …
Does it matter if the end user knows what the database is?
Welcome to Log Buffer, the weekly roundup of DBA industry happenings.
Read on for the latest updates in Log Buffer #193. Don’t forget, we’re always looking for volunteer editors to publish and host an issue of Log Buffer. If you’d like this to be you, contact the Log Buffer coordinator.
ODTUG/Kaleidoscope 2010 roundup:[Read more]
OpenSQLCamp is less than 4 months away, and I have finally gotten around to updating the site. Special thanks go to Bradley Kuzsmaul and the folks at Tokutek for getting the ball rolling and making the reservation at MIT. Using MIT means that we will have *free* reliable wireless guest access and projects.
OpenSQL Camp is a free unconference for people interested in open source databases (MySQL, SQLite, Postgres, Drizzle), including non-relational databases, database alternatives like NoSQL stores, and database tools such as Gearman. We are not focusing on any one project, and hope to see representatives from a variety of open source database projects attend. As usual I am one of the main organizers of Open SQL Camp (in previous years, Baron Schwartz, Selena Deckelmann and Eric Day have been main organizers too; this year Bradley Kuzsmaul is the other main organizer). The target audience …[Read more]
One of the things I preach about a lot is good monitoring of your
database servers; having tools in place to tell you both what
good looks like and when things go bad is critical for large
scale success. But sometimes you just need to monitor a momentary
process, where setting up a check in your normal monitoring
software is overkill. In these cases one tool that can help out
is the watch command.
Case in point, the other day I needed to back up a fairly large partitioned table (about 1.3TB on disk). The plan? A quick little script to pg_dump each of the partitions (about 325). Feed the script through xargs -P so I don't swamp the box, but I get some concurrency out …
During the MySQL conference Call for Papers there was some
talk of getting one or two Postgres sessions into the mix, as a lot of MySQL
users seem to have questions about Postgres these days. Alas,
looking through the MySQLcon schedule I don't see any on there.
I've also looked through the BOF's and nothing about Postgres to
be found there either. So, maybe no one is interested in Postgres
However I held a Postgres BOF at MySQLcon last year and we got a handful of people, and since I am going to be at MySQLcon again this year, I might as well host one again. I think it's too late to schedule one formally, but I can put some info on the schedule sheets once I'm at the conference; if you are interested in learning some more about Postgres, please keep an eye out.
Before all my fellow DBAs' heads explode, let me just say that I
am a relational guy. I like the relational model, think it's the
best tool for the job, and think every programmer (not just
DBA's) should aspire to be as familiar with it as they are with
AJAX, MVC, or whatever other technology pattern you think is
important. I'll even take that a step further; I think the NoSQL
movement is mostly a re-hash of failed technologies from the last
century. Object and document databases had their run in the
market (some might say "they had their time"), and they were pretty
thoroughly beaten by the RDBMS; that some people have reinvented
that wheel doesn't change the game.
That said, I find the recent comments from Jeff Davis on the relational model and scalability …
I've just publicly released another Postgres-related script, this one called "boxinfo". Basically, it gathers information about a box (server), hence the catchy and original name. It outputs the information it finds into an HTML page, or into a MediaWiki formatted page.
The goal of boxinfo is to have a simple, single script that quickly gathers important information about a server into a web page, so that you can get a quick overview of what is installed on the server and how things are configured. It's also useful as a reference page when you are trying to remember which server was it that had Bucardo version 4.5.0 installed and was running pgbouncer.
As we use MediaWiki internally here at End Point (running with a Postgres backend, naturally), the original (and default) format is HTML with some MediaWiki specific items inside of it.
Because it is meant to run on a wide a range of boxes as possible, it's written in Perl. …[Read more]
Oracle, after dating HP, Dell, Netapp and EMC has found its mate
in Sun. Oracle is now becoming a systems company, and unceremoniously dumping
these former paramours. These leaves the spurned lovers to find
alternate accommodations, especially in the area of the
As I have stated previously on this blog, the clear partner of choice on the Windows front is Microsoft. This is demonstrated by today’s partner announcement around MS SQL Server for OLTP. But who is their partner in the Linux segment?
The following are contenders:
* Postgres (HP rolls their own)
* EnterpriseDB (pre-rolled Postgres)
* Ingres or Sybase—Oracle has felled them both in the past, …
It's been interesting watching the MySQL drama unfold, but I have to take issue when people start trying to drag Postgres into it again by spreading FUD (Fear, Uncertainty, and Doubt). Rather than simply rebut the FUD, I thought this was a good opportunity to examine the strength of the Postgres project.
Monty recently espoused the following in a blog comment:…[Read more]