One thing I really enjoy about the SQL Server community is its vibrancy. I'll give you details on the SQL Server community's explosive growth in a moment, but let's start by comparing Microsoft SQL Server's user community with those of other significant database platforms.
Posted May 10, 2010
If you spend any time at all reading IT trade journals and websites, you've no doubt heard about the NoSQL movement. In a nutshell, NoSQL databases (also called post-relational databases) are a variety of loosely grouped means of storing data without requiring the SQL language. Of course, we've had non-relational databases far longer than we've had actual relational databases. Anyone who's used products like IBM's Lotus Notes can point to a popular non-relational database. However, part and parcel of the NoSQL movement is the idea that the data repositories can horizontally scale with ease, since they're used as the underpinnings of a website. For that reason, NoSQL is strongly associated with web applications, since websites have a history of starting small and going "viral," exhibiting explosive growth after word gets out.
Posted April 07, 2010
After the misery that was 2009, most of the SQL Server users I talk to are happy that 2010 started in languid fashion. Not that there isn't a lot of work to do; on the contrary, there's more work than ever. However, the long hours and multiple projects of 2009, compounded by freezes in all levels of spending, raised the general stress level to unhealthy heights. With the new year, stress levels dropped significantly, and many IT leaders see signs of improving prospects. What does that bode for 2010? I have a couple of predictions, though I doubt they'll surprise many people.
Posted March 04, 2010
One fall semester many years ago, I was a university freshman. Actually, I was anything but "fresh." I was dumb enough to think that 8 a.m. was a wonderful time to attend Economics 101. After staying up until the wee hours most every night, the "dismal science" took on more than one meaning as I set my clock just early enough to get to class on time. Along with 30 other very naïve classmates, I staggered into class and did my bleary-eyed best to focus on the lessons at hand. There were lots of Greek compound words and lots of graphs. I learned, for example, that the word economics derives from the Greek "oikonomikos," which means, approximately, "death by slidedecks" and, specifically, "house" (oikos) and "management" (mikos). I barely survived the experience and never took an 8 a.m. class again. Imagine my surprise, then, when a lesson I'd learned (and promptly forgotten) all those years ago jumped back into my consciousness late last year.
Posted February 09, 2010
I was once asked what I thought Microsoft's overall product trajectory for SQL Server was, in light of Oracle's rather obvious trajectory of acquiring multiple application vendors who will, in turn, deploy more and more of their applications to the Oracle database platform. To be honest, I had a little difficulty perceiving a clear and concise strategy statement for the sort of work going on in Redmond. I could see a lot of great features being developed. And I knew the SQL Server development team had developed a lot of new "plumbing" with each new release - features like Service Broker and Extended Events and exponentially more robust capabilities in the Analysis Services product lines. But the strategy itself was veiled and, since Microsoft wasn't explicitly telling us what the grand strategy was, I had difficulty putting my finger on it.
Posted January 11, 2010
Listen to a group of database professionals talk for awhile and someone will eventually bring up the topic of data deduplication. Data deduplication is a means to eliminate redundant data, either through hardware or software technologies. To illustrate, imagine you've drafted a new project plan and sent it to five teammates asking for input. That single file has now been reproduced, in identical bits and bytes, on a total of six computers. If everyone's email inbox is backed up every night, that's another six copies backed up on the email backup server. Through data deduplication technology, only a single instance of your project plan would be backed up, and all other instances of the identical file would simply be tiny on-disk pointers to the original.
Posted December 14, 2009
If you've read the IT press at all these days, you know that SQL Injection (SI) attacks are very common and can be devastatingly effective. In fact, SI attacks-equally easy to execute against Oracle, MySQL, IBM DB2, or Microsoft SQL Server-are among the most common hacks on the Internet today. If a web application runs a relational database on the backend, it can be subject to an SI attack, which ironically, is among the easiest web hacks to prevent.
Posted November 11, 2009
In this season of recession and financial meltdowns, a common question seems to be, "How big is ‘too big to fail'?" Titans of the financial industry made big bets with lots of risk and, when they didn't pan out, American society overall has to pay the price. But, that aside, the very scale of our financial system, by just about every metric, has reached amazing heights, be that number of financial transactions per second, number of traders, number of funds traded, amount of money changing hands—you name it. This might seem like a tangent to the point of databases in general and SQL Server in particular, but there are actually quite a few similarities in my mind.
Posted October 13, 2009
If you haven't paid attention to the new social media, you're doing yourself a disservice. Just as email was a game-changer in the 1980s and the internet revolutionized society in the 1990s, social media is making a huge impact on the way people work and interact today. Personally, I was skeptical about social networking until some good friends persuaded me to give it a trial run. It seemed like a great way to dither away some valuable time, but I didn't see the business value in the whole proposition until I tried it.
Posted September 14, 2009
Microsoft SQL Server's relational engine has offered new instrumentation that improves by light years with each new release. The introduction of Dynamic Management Views (DMVs) in SQL Server 2005 provided a much-needed equivalent to Oracle's long-standing and capable V$ and X$ system views. SQL Server 2008 has provided another dramatic improvement to its instrumentation with Extended Events (also known as XEvents) that promises to offer even greater opportunities to tune, trace and troubleshoot the inner workings of a SQL Server application. All of this stands in stark contrast with the anemic instrumentation offered in SQL Server Analysis Services, Microsoft's wonderful multi-dimensional data repository that is a free feature-set within the SQL Server product.
Posted August 14, 2009
At a rather muted Microsoft TechEd in Los Angeles in May, the crowds were diminished and the educational content was slimmed down. In the past, SQL Server sessions were so abundant that you'd have trouble choosing which of several you might want to attend. This year, the state of the economy was reflected in many ways, including the one, or, in just a few cases, two sessions per time slot allotted SQL Server professionals. Despite the low ebb, the Microsoft SQL Server team made an exciting announcement about the upcoming availability of the SQL Server 2008 R2 CTP (Community Technology Preview).
Posted July 13, 2009
Now that I know I can post, let me state at least some of what I stated broefe.The thinking patterns of a person is something that is learned over time and is driven by success and motivation and curiosity. Success , of course, does not necessairly mean the greatest success to be had, but some success.Outside of people like you and I, most get rather lazy about thinking and once they become somewhat successful are reluctant to improve further.Optimizing SQL require one of two approaches: (a) an intimate knowledge of how the underlying database works basically, how it will parse the SQL, how it will attempt to optimize the SQL, how it will attempt to match it to indexes and the like. The other approach is by trial and error .Alas, SQL, if my may say so myself, sucks as a language. Basically, it works hard at trying to hide all the low-level machinations of the database system; yet you can't write good SQL unless you deal with those low-level machinations!!! The very fact that it hides these details makes it even trickier to optimize, because its optimizer is trying to be a one size fits all , and it has to guess about a lot.Indeed, in optimizing SQL, not only are you dealing with the low-level machinations, but you are also dealing with the default assumptions of its optimizer, as well! It's kinda insane having to work around both.So, that certain data analyist will never be able to deal with all of these complications. He is to be understood, actually, because he is actually trying to use SQL in the way it was intended so as to not have to deal with all the low-level details that he shouldn't have to deal with anyway.Alas, this is really the failing of many, if not most computer languages, ORMs, and other systems designed to simplify and to hide complexity to really effectively use them eventually you have to understand the complexity it's trying to hide you from, and worse how it's trying to hide you from it!!!!!It's amazing how little has changed over the years. I ran into these same issues dealing with Microsoft's infamous MFC framework, and even Java. I had to deal with this in my C and C++ days, and also had to deal with it when I wrote a lot of PHP code.So, for just kicking it around, the SQL language it great! But when you get serious that all the limitations comes to the fore. And this is true of nearl everything in computerdom.My, this came out quite a bit different from what I wote broefe!
Posted June 15, 2009
Third-party applications are a very important part of the IT landscape. Many of us have faced the common dilemma of trying to decide whether to build or buy that next important application our organizations need. (By the way, I'm talking about smaller, specialized applications like an inventory management system for the company warehouse, or a practice management system for a doctor's office. I'm not talking about the huge and incredibly sophisticated ERP systems like SAP and Oracle Financials.)
Posted May 15, 2009
The idea of "SQL Server in the cloud" is all the rage as I write this article. Many SQL Server experts already predict the demise of the IT data center and a complete upending of the current state of our industry, in which large enterprises can spend millions of dollars on SQL Server licenses, hardware and staff. I have to admit, when I first heard about this idea, I was ecstatic. What could be better for an enterprise than to have all the goodness of a SQL Server database with none of the hardware or staffing issues? However, on deeper examination, there is much about which to be cautious.
Posted April 15, 2009
The Future of Coding for SQL Server, Part 2
Posted March 15, 2009
SQL Server has supported VLDBs (very large databases) for some time now. Back in the SQL Server 2000 days, I recall hearing multi-terabyte databases were unusual but doable. Now, they are commonplace, while databases in the hundreds of terabytes inhabit the part of the map that says "there be dragons." While VLDBs are quite common on SQL Server today, highly scalable systems that can be flexibly extended in the same fashion as Oracle/RAC are less so. So, how do you design a highly available architecture for SQL Server if it's not like Oracle/RAC.
Posted January 15, 2009
Implementing PBM in your environment will probably require more than just a few superficial changes.
Posted December 15, 2008
Posted September 15, 2008