Featured Article(s)
SQLCMD — Part I
(Vadivel Mohanakrishnan) This is the first of the three part series on SQLCMD of SQL Server 2005. The target audience of these articles are Basic to intermediate level readers.
Need to Get Up To Speed on BI?
BI is a core requirement for many companies and something that many people are struggling with – not only on a "how do I do that" basis, but also on a "how do I get started" basis. If this is you, check out the SQL Server 2005 Business Intelligence Workshop. Here you’ll learn how to use this powerful, comprehensive platform to integrate your data, report on your data and analyze results – leading to competitive advantages and overall better decision making. Find out more here and get a schedule of classes.
Webcast: Moving from SQL Server 2000 to SQL Server 2005 Security
We’ll look into the differences between the approaches to security, how they apply to your database, the information you’re managing and tips along the way. There are some strong abilities in SQL Server 2005 and this show will look to explain the differences from the perspective of moving from SQL Server 2000. We’ll compare and contrast and make sense of the updates so you’re ready to move forward.
> Register Now
> Webcast Date 10/4/2007 at 12:00pm Noon Pacific
Where is the Line?
More data losses, and more trouble for some previous data losses as well. What’s intriguing to me is that "they" call these data losses, but they’re really wireless network hacking for access in some cases. Why is this interesting? Well, it has me thinking a bit on where the line in the sand is?
You can bet that someone came to the DBA and had their hide about the data loss. Of course, they’d be right in this because the data should be protected at rest and that is, indeed, the DBAs responsibility. But…
Is the DBA responsible for the DATA? Because if so, that would suggest that we need to be far more involved in thinking through things like data transmission protection, encryption in front of the database and so-on. This whole question lends itself well to the discussion in last week’s show about working with IT and managment – how you combine the roles of DBA and management (another topic for another day). It suggests that we should indeed be heavily involved in the data design processes – from soup to nuts, really.
But I don’t think, especially based on some of the "feedback" (yeah, that’s what I’ll call it, feedback) mail I’ve had about the IT vs Management discussion in the show, that it’s realistic in companies today to include the DBA in those discussions. It seems like the more a DBA-type gets involved and starts to point to weak points in the structure, the more they’re blocked from the process.
You’d be amazed at how many emails I’ve had suggesting that DBAs need to butt out and not point out flaws in designs, that it’s not their place.
I’ve been amazed by the suggestion that they back off. Of course, they’re also held accountable for those data breaches, for the security of the information.
Can’t have it both ways! How do you straddle this line? What do you do? Email me, please, and let me know how you address this.
Featured White Paper(s)
Improve SQL Tuning with Best Practices
Tuning SQL statements on Microsoft SQL Server with native tools or by hand can be time consuming and labor intensive. Let SQL… (read more)
Microsoft T-SQL Performance Tuning Part 2: Analyzing and Optimizing T-SQL Query Performance on Microsoft SQL Server using Indexing Strategies
This white paper, authored by SQL Server expert Kevin Kline, discusses the basics of indexes, such as density and selectivity… (read more)
7 Steps to Successful SQL Server Auditing
This easy-to-read guide will explain and simplify the basic steps associated with successful SQL Server auditing & give you t… (read more)
Anatomy of an Archiving Project – Seven Basic Principles for Managing Your Enterprise Data
According to a January 2006 study conducted by the Enterprise Strategy Group (ESG), database archiving has helped companies m… (read more)