So I’m sitting here at the blogger table at the 2nd PASS keynote by Tom Casey and he brings up a good point. Now this is something I’ve blogged about in the past, but it’s about that guy in your org who goes off and does his own thing and puts a small DB on his desktop and starts doing data loads, and crunching things on his own. That can be a problem because IT isn’t involved and IT doesn’t even know it exists. That’s why slammer was so devastating because of all those “unauthorized” DBs out there. And everyone should be going through IT for these types of projects… or should they?
Tom actually brings up a good point that every piece of data, or every query doesn’t have to go through IT. Some things aren’t big enough or are only for short-lived times and there’s no reason for it to be spun up as a project. And again this is a fine line because as a DBA I really do have to know where my data’s going and if I let everyone just pull whatever they wanted, then server performance would be crap. So it’s a tough line to walk because while we need to have some kind of decent control over where our server resources are going, we also don’t need to be involved in every little thing that crosses someone’s mind.
IT quite often also isn’t very responsive because we do have to plan things better than the users do and I think they lose sight of that. The trick is for us to make it a real project while at the same time not slowing them down too much.
So I’m gonna go ahead and say that office users are free to keep things under our radar, but know that comes at a price. If you lose the data or the code or it starts performing badly, then don’t come crying to us. These are the things that IT brings to the table. We bring recoverability, stability, accountability, etc. And it’s quite possible that you start something on your own and then get IT involved when it gets too big or too important for you to manage yourself. I really like this scenario because it’s often times easier for us to take over a project than it is to build it from scratch. Sometimes it’s not because you have to re-write it to actually make it stable, but even that’s often times easier because you’ve already got the business logic and the GUI defined for you.
So anyway, I like what I see in the demos on their new excel plugin (PowerPivot), but personally I’m waiting to see if it’ll actually work as well as they expect. Because the data they’re using is highly specialized and I have to wonder how well my data will work with the product. PowerPivot is a new BI plugin for excel 2010 but I really expect that it won’t really take hold for a couple yrs because the requirements to duplicate the scenario they outlined in the keynote are office 2010, sql server R2, and sharepoint 2010, and I just don’t see many people converting all of these that fast.
Watch my free SQL Server Tutorials at:
Read my book reviews at:
Blog Author of:
Database Underground – http://www.infoworld.com/blogs/sean-mccown
Follow my Twitter:
- Sean McCown
- I am a Contributing Editor for InfoWorld Magazine, and a frequent contributor to SQLServerCentral.com as well as SSWUG.org. I live with my wife and 3 kids, and have practiced and taught Kenpo for 22yrs now.
- ▼ November (11)