Featured Article(s)
Top 10 Agile Database Development Practices
Many organizations like the idea of rapid application development without a long waterfall Software Development Life Cycle (SDLC). They recognize the effort to generate a complete "to be document", such as a database Entity Relationship Diagram meeting all system requirements, to be an exercise in futility. Rather than swinging to an opposite extreme of chaos and inadequate design, Agile developers have established practices resulting in reliable and efficient software design. This articles reviews what I believe to be the top 10 principles that, when applied to Agile Database Development, result in the optimum production reliable code.
Learning SQL Server, SharePoint, Business Intelligence…
– Learn More or Register: Virtual Workshop: SQL Server Performance (Mar 12!)– key concepts, learning and how-to information for working with SQL Server
– Register: Spring 2010 SSWUG.ORG Virtual Conference (Apr 7, 8, 9) – SQL Server, Business Intelligence, SharePoint – 75 sessions, 20 speakers…
– Register: DBA School – (60% sold-out already) 15 ppl max – (Apr 19, 20, 21) – In-Person class that focuses on the things you really need to know – and shows/teaches how to apply it.
Time’s running out to register for each of these – please register soon to save your spot.
New SelectViews Video Program Released
Talking to experts – the show today features Kevin Kline, talking about his experiences in field. Also, Adam Jorgensen is on the show today talking about his experiences helping clients with BI projects and more.
[Watch the Show]
Next Idera "Secrets" Webcast – Register Now
Are you a SQL Server developer dealing with an increasing number of administrative tasks traditionally assigned to DBAs? Expert Donabel Santos will ease your database administration headaches in a “Secrets of SQL Server” webcast March 10, 2010 at 3 p.m. CST. During the event, you will learn tips, tricks and solutions to common administrative challenges. Santos will also share ways that DBAs and developers can work together to ensure successful implementation of development projects and avoid those terrible ‘oops’ moments. Register now for the webcast.
Privacy a Thing of the Past?
The SSWUG/Bits team was at a recent conference where they were talking about technologies and where things are going, how they’ll apply to what we’re doing today and so-on. One comment stood out. "Privacy" is a done deal. Just write it off. "fuggetaboutit…" and move on.
The comments were part of talking about technology, the cloud and how things will morph in the near (not sure what "near" is) future. Specifically, that there was more value in the global access than risk in the data exposure.
Now, before everyone gets all up in arms, I think this is not so much about "identity" type items – social security numbers, credit card numbers, etc. It’s more about the fact that we need to be coming up with better ways to protect the identity items and better ways to make available those items that benefit from being open to the tools and technologies here now and coming soon. I quickly thought of the commercial I’ve seen recently with the man in the doctor’s office. The Dr. asks a question and the patient answers… then an audience of doctors, also with knowledge about the patient and/or condition chimes in.
I *think* it’s supposed to be an uncomfortable moment, but it makes a good point too. We all talk about crowd-sourcing so much of the knowledge we rely on daily. If we focus on solid technologies to apply and crowd-source other things, we could see some interesting benefits. Yes, I do get it that some information needs to be controlled and that this opens up all sorts of issues, and I do understand that the combination of life-clues and data potentially leads to people knowing more about us that we like publicly, but …
So, without degrading this to another privacy discussion, my real question is this… what things should we be doing, developing, creating, etc. today to address this? We have issues of data protection, we have issues of opening up information sources, etc. What else will need to be addressed and, perhaps as important, are there things today that we should be doing to not close off systems to the opportunities? Is it just to make sure you’ve designed your systems well? That you’ve incorporated some protections on information selectively?