Whew – this week freakin’ flew past with all of the blog syndication stuff. I kid you not, I actually broke a sweat this week.
SQL Server Links
Preventing Users from Copying Data – DBAs normally concentrate (or, uh, ignore) big security issues like a user copying backup files or doing a DTS export, but what about the more subtle ways of stealing data?
Roll Your Own SP_Who2 – if you want to learn about SQL Server’s dynamic management views, Jason Strate suggests that a good way to do it is to build your own sp_who2 replacement. If you like that, check out Jason Massie’s replacement for the Activity Monitor on SQLServerPedia’s script library.
How SQL Server Decides on Seeking or Scanning – Jason Massie gives a peek under the covers at how the SQL Server engine works, along with a tutorial script to see it in action.
Row-Based Security Tutorial – say you want to make sure each salesperson only sees data about their own customers. Jeremiah Peschka explains how to build row-based security. Warning: this does affect your query performance, and you have to build your queries and indexes appropriately. I would highly recommend against using SQL Server’s built-in variables for usernames in enabling this. I’ll blog about a data warehouse horror story around that.
Covering Index Tutorial – shows how to create and use covering indexes. When you understand this part, take the next step and learn about SQL 2005’s new INCLUDE parameter on indexes, which makes covering indexes even more powerful.
Are You Using Enterprise Edition Features? – if you’re developing your database application on SQL Server Developer Edition or Enterprise Edition, you might be using features like partitioning that are not available in Standard Edition. Find out – before you find out the hard way. (Restores onto a Standard Edition will fail if you’re using partitioning, which can give you a very ugly surprise if your disaster recovery server is running Standard.)
Using SQL’s Management Data Warehouse in Your App – I haven’t met anybody who’s actually using the Management Data Warehouse in production yet, and I want to sit in on at least one session about it at PASS. This is one of those things that sounds really cool in theory.
PASS Update from Andy Warren – Andy’s building on the momentum of PASS’s new web site and recruiting volunteers to help flesh it out. I’m glad he’s taking that approach, because there’s some web-savvy people in his list of volunteers:
- Brian Kelley: SQLServerCentral, Twitter
- Grant Fritchey: ScaryDBA (syndicated at SQLServerPedia), Twitter
- John Magnabosco: Simple-Talk, Twitter
- Tim Mitchell: SQLServerCentral, Twitter
- Tim Ford: SQLAgentMan (syndicated at SQLServerPedia), Twitter
- Jessica Moss: Blogspot, Twitter
- Jack Corbett: Wiseman-Wiseguy, Twitter
- Brad McGehee: SQLServerCentral, Twitter
- Chuck Heinzelman: Me, My Database and I, not on Twitter (yet)
- John Allman: (couldn’t find a blog)
- Scott Klein:(couldn’t find a blog)
All but three are both blogging AND Twittering – a great sign for the people who will be doing some well-appreciated work!
Cloud & Virtualization Links
What’s the Blade Break-Even Point? – I rolled out a blade infrastructure at Southern Wine, and I was really impressed by how much work the blade vendors put into their power & cost calculators. Putting in a blade chassis requires a LOT of power and cooling, even when the blade chassis is nearly empty. Scott Lowe walks you through the break-even points for HP blades.
The Junk Drawer
Prankster filling loud exhaust pipes with foam – now that’s just wrong. And by wrong I mean right.
Do you really need solid state disks? Mike Ault, an Oracle expert and former Questie, explains how to judge whether or not expensive solid state drives make sense in your environment. He works for a solid state disk company now, but his advice is sound.
First Look at Windows 7 Backups – I long for the days when my Windows machines will be as easy to back up as my Macs. Time Machine is amazing, but Windows 7 is getting closer, especially with the ability to back up to any network share. Nice.