Editorials

What Would You Call SQL Server?

Featured Article(s)
Useful Undocumented Miscellaneous SQL Server 2008 DBCC Commands
In this article, Alexander Chigrik shows some useful undocumented miscellaneous DBCC commands that shipped with SQL Server 2008.

Combine Named Sets and Calculated Members in Analysis Services, Pt. 3
Part 3: Combine Named Sets with Calculated members to meet client and employer business requirements. Join BI Architect Bill Pearson as he leads hands-on exploration of Named Set / Calculated Member combinations in Analysis Services.

No More Restoring a Database to a Temporary Location!
Have you ever had to restore a database to a temporary new database location, just so you could select key bits of information from it to restore to a production system? I know it’s a super-common thing to have to do and can be maddening. You have to have the disk space, it’s a slower process, etc. It can really be a challenge to get the information bits you want to specifically restore. You now have an option – there is a new tool from Idera – SQL Virtual Database – that lets you attach a backup file to SQL Server as a virtual database. From there, you can use any native or third-party tool to pull the information you need and you’re all set. It’s really quite cool. Get more information here and give it a try – it could save you a LOT of time and aggravation. Check it out.

What Would You Call SQL Server?
I was at SQL Connections this week and listening to a presenter during Microsoft day talking about SQL Server, the future of the platform and where it’s headed. The emphasis was on SQL Server as an information platform, not a database engine. I don’t think that’s any big surprise to many. There is information at the conference about spatial data, about the new abilities in R2 and much more. One thing that caught my attention though was this presentation and one thing in particular. The presenter mentioned that the name "SQL Server" was really old-fashioned and outdated.

It really caught my attention when they said this. I get that the product has evolved and includes a whole lot more than an SQL language parsing ability, but I had kind of thought that the "segments" of SQL Server (reporting services, analysis services, etc.) kind of made up for the "restrictive" naming of SQL Server as a core product.

I had to stop and think though – what *should* or could it be called? I am NOT saying that a name change is in the works, only that it’s true that SQL Server is more than an SQL engine.

Some other interesting points revolved around Microsoft’s work to address what I saw as a series of different "customers." Developers, IT in general, business analyst-types and management all come into play, but the technologies also mix this up a bit. From desktop to mobile to enterprise-class traditional databases to cloud-based solutions – there is a lot influence in the product development cycle that has to be considered.

The big take-away at the conference and all of the different events going on this last month or so, is that cross-platform is something that everyone with database responsibilities is going to have to face up to sooner, rather than later. From keeping track of data to making it available in the first place to supporting the different options and environments, it’s clear that these options are not only "here to stay," but becoming mainstream and assumed, rather than odd exceptions to the norm.

What would YOU name SQL Server? Would it be more broad or more specific? Drop me an email here.

Featured White Paper(s)
The 6 Key Points of SharePoint Infrastructure Planning
SharePoint products and technologies have readily found a place within the business environments of many organizations. Share… (read more)

Featured Script
unixtime to readable date/time
This function convert an unix to a comprehensible / understandable /readable format … (read more)