Blog Anniversary
Two years old. In March of 2008 I received a whopping 96 visits. I'm up to 1900 so far this month. I'd call that a positive growth trend. Thanks for stopping by, especially if you've been here more than once.
MacGyver?
Who the heck is MacGyver? Television program you say? Hang on. I need to visit imdb.com... Oh, the late eighties... Yeah, I wasn't watching TV in the late eighties. Actually I didn't own a TV in the late eighties. But reading a few of the plot lines (you guys watched this?) I get the idea. Nuts. I don't think I'm MacGyver. Can't we just buy something to fix the problem? Honestly, the only thing that comes to mind was the time when I needed to get alerts when jobs failed, but I couldn't install DBMail on the server because our admin types didn't want mail clients on our machines. What to do? Use event forwarding. Instead of setting up the mail client on a server, I got it installed on a…
Powershell for Batch Operations
I'm right in the middle of moving one of our databases from Oracle to SQL Server (and I just love saying that, over & over). Evidently the most common practice in Oracle is to leave all the tables as heaps. That's a tad bit problematic approach for SQL Server. We moved the structure from Oracle to SQL Server with almost no changes and now we're cleaning up the mess fixing the structure iterating the design. I needed to drop & recreate 250 plus indexes. Remember, I'm lazy. A few minutes bouncing around the web and looking at the wonderful book "SQL Server 2008 Administration with Windows Powershell" and I put together a simple little script that generates a script for dropping and recreating all the primary keys on the tables and, as a…
Help with Learning Powershell
If you're not reading Buck Woody's blog, why not? Today he posted a helpful hint for getting performance counters directly out of PowerShell v2. I'll add a little bit to the hint, don't try running this on your XP boxes. It doesn't hurt anything, but you get a helpful little message "Get-Counter : This cmdlet can only run on Vista and above."
So You Want to Write a Book?
What the heck is wrong with you? Still interested? Fine. I'll tell you my take on this whole business. I'm only an expert on this if you take the adage that the expert is the guy that's a page head of you in reading a book. To date I have published two full books and three chapters in a third. I can easily think of enough people who all have more experience than that with book writing that I'd have to take off both shoes to count them all. Is anyone still reading? Cool. So you have the desire to write a book? Let me pop your first bubble. You will make very little money. This bears repeating. You will make very little money. If you were to figure out your hourly…
Buck Woody on Code Writing Code
I realize I'm prejudiced, being one of those evil DBA's & all, but I can't help but agree with him. It's a short post, but worth the read.
nHibernate Database, First Look
I'm getting my first look at a full-fledged nHibernate database developed by consultants for our company. I thought I'd share my initial impressions. I'll be capturing trace events from the database over the next couple of weeks, so I'll be following up on the behavior of nHibernate within this database as well. The first thing I saw & thought was, "Foreign key constraints. Thank the gods." That really is good news. I was frankly concerned that they might go with the "let the code handle it" approach. There are quite a few null columns. I'm also seeing tons & tons of nvarchar(255) which must the default string size. Lots of bit fields too. They also used bigint in a lot of places too. None of this is definitively good or bad,…
SQL Saturday #34 Wrap-up
Whew! It's over. New England Data Camp v2, aka, SQL Saturday #34, was completed on Saturday. Going in we had maxed out our online registrations at 500, an accomplishment by itself. During registration on the day of the event, we shut down registration and just started waving people through the door at 300. Our best guess at the total attendance was 340 (not the 375 I tweeted during the delirium of the day). There were a couple of minor glitches and one major one. The major glitch was not enough vegetarian food. We just ran out. Everyone else seemed to get a meal. We had just a few, read that 3 or 4, sandwhiches at the end of the day. I want to personally thank Adam Machanic for all the…
SQL Saturday #34
The event is this Saturday. Take a look at our sponsors, speakers and the program. It's going to be a great opportunity to learn about SQL Server and things around SQL Server. If you're in the New England area, please register and take advantage of this excellent event. 450 of your peers are already pledging to show up. This is going to be a good time for networking too.
A Call to Arms
Phil Factor's most recent guest editorial over at SQL Server Central has, to a degree, pointed out that the emporer's spiffy new outfit... well, it's not exactly there. That's why he looks so nekkid. But seriously, the very idea of naming objects inside of the database with Hungarian-style notation really should end. Phil's right. There's absolutely no reason why you should name a unique index ixuTableName when UniqueTableName or TableNameUnique would do the job just as well and not be nearly as obscure. I confess to using this type of naming convention all the time, but I'm realizing that I don't need it and it's largely just habit. There are possible exceptions, for instance you want to group all lookup tables in your database so you name them lkTableName, but…