Featured Article(s)
Oracle 2-Day DBA in x Days Post 14; Creating a Tablespace
We have taken a look at the physical storage structures for Oracle, now let’s dive into tablespaces and how to create some.
Getting In Touch with Developers
We’ve been debating. It all started with SQL Injection – and getting the word to people that there is an issue. Now, I’m not going to go into Injection here… again… at least not now. 🙂
But… the question really revolves around the realization that many developers don’t know what they don’t know. They don’t realize that SQL Server isn’t just a big MDB. That there are things that should be considered for recovery, for tuning, for security as you build out a SQL Server-based solution. This is true even if it’s a "casual" solution – one where the database interaction is simple and not in need of optimization.
How do you reach out to these folks and get them up to speed? Even if it’s just to help them with best practices that are pretty straightforward to implement, but might not be clear enough that you need to do them. We haven’t been able to come to any good resolution on this, this idea of how do you reach these folks.
So, my question to you – how do you get to those developers – truly accidental DBAs (or accidental database users) – and let them know there are a few things they should know about?
What’s do you think? Any ideas? Internally to your organization, externally for the "common good" and so-on – how could this be approached?
[Drop me a note] – Ideas?
Featured White Paper(s)
Whole Server Protection from a Single Solution
The complexity of traditional recovery solutions compounds an already difficult situation, and heightens the opportunity for … (read more)
Microsoft SQL Server 2005 Deployment and Tests in an iSCSI SAN
iSCSI SANs offer an alternative for building Storage Area Networks. Consolidating storage in a SAN offers storage management … (read more)