Editorials

Columnar Databases, Job Schedules and SQL Server

Watch The Latest SQL Server Weekly Show Here
Last chance to catch last week’s show before the new show posts tomorrow.
> Watch Here

Featured Article(s)
Stopping your Jobs on a Schedule
Do you ever need to make sure a job does not run in the next production day? If your code can be sectioned off to do smaller pieces, then this article may help you.

Speed Up Your SQL Server Development

Build complex joins with a few click…Build stored procedures in seconds…Parent-child relationships with a single click. Automate daily database builds, manage multiple database implementations and more. Do you want a database tool that will save you a great deal of time and effort? dbOrchestra can help save you and your enterprise time and money. Find out more here.


Have You Considered Different Database "Technologies?"
I’ve been trying to read and understand about some new technologies that may be coming for databases. From object storage to columnar-type data management. I’m curious what your thoughts are about the future of databases from a reality-basis.

I admit that a relational model makes sense to me, that I’ve used it for a while and that it’s quite possible I’m biased at this point to that model just because it’s familiar. That aside though, I wonder about these technologies because I can’t help learning about them but still thinking that "yeah, but if you have related data that you need to pull back, isn’t relational-type access still required, perhaps on top of the other techniques for storage??"

Does this mean that we’ll have either multiple databases for a given application, with each database providing "tweaked" storage for a given purpose? Does it mean that you’ll have to have an abstraction layer so your application doesn’t know or care about the storage mechanism behind the scenes? If you have to have an abstraction layer, does it negate the positive effects of these storage engines?

Given all of this, and the fact that applications will have to be rebuilt to support either the proxy layer or the different database approaches, will people really see that much increase in performance as to warrant a rewrite?

Inquiring minds want to know… and understand better. Drop me a note with your thoughts, insights and theories

I’m off to read, inquire and learn… I’ll keep you posted.

Featured White Paper(s)
Data Privacy Compliance in the Application Testing Environment – Data Masking and Transformation for Privacy Compliance
News of high-profile data breaches has increased awareness and heightened the need to protect data privacy in the more vulner… (read more)

Common Table Expressions
Common Table Expressions(CTEs) are new to SQL Server 2005. CTEs are defined in the ANSI SQL-99 standard. We need to begin lea… (read more)

Improving SQL Server Performance through Better Application Monitoring
Learn how to provide higher performance and availability for your SQL Server by knowing the key drivers behind SQL Server per… (read more)