I have been plotting sessions that I’d like to present at SQL PASS for a little while now, and the June 5 deadline is approaching. Since I’m on vacation this week, I took some time to write up my abstracts. Man, oh man, that was more work than I thought! Condensing ideas into 1000 characters or less and still saying all you want to say isn’t as easy as it seems.
As for all posts on this blog, this post provides no guarantees for the tools described: use at your own risk, and make sure to test all functionality. This came to mind recently just because I wondered– is there any other free tool that does this better?
Times change, but some things stay the same.
This post is about a really little detail that isn’t a big deal.
I have been working away building out servers in our new prod test environment, and automating as much as possible along the way with PowerShell. I have to say that it’s been really fun and PoSH has brought back that loving feeling that I always had for Perl. If a programming language can be friendly, PowerShell manages it.
There are a couple of local security policy rights that are not granted by default in SQL Server setup that I’ve been setting manually for a few years now:
Somehow, I didn’t know about slipstreaming installations of SQL Server until last week. I heard about them at SQLPASS in Allan Hirt’s session on installing SQL Server 2008 on Windows 2008 clusters.
SQLPass unfortunately can’t last forever, but happily it’s still going strong. Here’s some highlights from my Day #2.
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.