Search results matching tags 'tools' and 'SQLMag'

SQLMag = SQL Server Pro. Goes all-digital!

KKline — Fri, 27 Apr 2012 13:30:00 GMT

I was recently chatting with Megan Keller, my long-time editor for the Tool Time column and Executive Editor at SQL Server Pro,DevProConnections, and SharePoint Pro.

I've subscribed to SQLMag ever since it was first put to print back in the late 1990's. (That's a pic of me, on the right, in the shirt given my by SQLMag's first publisher way back in the day). I have many bookshelves in my office, but SQLMag consumes more than half of the shelf closest to my desk. It's that good. Some of my personal favorites and perpetual must-read content are the columns SQL Server Questions Answered by Paul Randal & Kimberly Tripp as well as the always excellent columns Puzzled by T-SQL by Itzik Ben-Gan and all of the great content by Kalen Delaney.

Megan recently told me about the exciting changes afoot there. For starts, SQL Server Magazine’s has new name—SQL Server Pro. This name, as you can tell from its sister publications listed at the top of the blog post, puts all of the Penton Media properties on an equal and consistent footing.

Please take some time to check out hands-on, how-to content from SQL Server experts at sqlmag.com. The on-line magazine features the same great expert advice and writers as before. And you can access my articles on sqlmag.com just as you have in the past.

Suggestions for the Tool Time Column?

And while we're at it, let me know if there are any SQL Server related tools you'd like to see in the Tool Time column! My requirements are that the tool must be free, must be supported, and of course must be relevant to SQL Server professionals.

Enjoy,

-Kev

Follow me on Twitter!

Dev Advice: Make a Tiny Dev Database Act Like a HUGE Prod Database

KKline — Fri, 16 Mar 2012 14:30:00 GMT

Here's an evergreen question. It's a question that never completely goes away. But lately, I've been getting it a few times per week. So I thought it's time to readdress the question, which usually takes some form of the following:

I can't really do effective development on my little dev laptop because our production SQL Server database is 15 gazillionbytes, way too big for my workstation. What's a uber-nerd to do?

Well, maybe they didn't use the word "uber-nerd". But you get my drift, right? The production database is really, really big - unmanageably big for keeping a local copy. So that means the dev either has to create a metadata-only version of the database, which won't produce realistic query plans, or somehow crush their laptop under 15 gazillionbytes of MDF and LDF files.

Actually, you have a better alternative - a clone database, sometimes called a shell database. Here's how I described a cloned database a few years ago here in my Tool Time column for SQL Server Pro Magazine:

In effect, a cloned database includes all of the schema objects of the database (e.g., tables, views, stored procedures), as well as the statistics and histograms (the so-called "statistics blob"). This metadata is quite small by volume but can tell you what estimated query plans look like outside of a large production environment and how those estimated query plans might change when SQL Server is upgraded. Cloned databases are especially useful when the data is confidential, classified, or subject to privacy laws.

The article gives you all the detail you need to effectively and quickly create a small version of a big, ol' production database that produces the same query execution plans as you'd get on the prod server.

If you're struggling with doing development on a big SQL Server database, learn the ropes on cloned databases asap! You'll be glad you did.

Enjoy!

-Kev

-Follow me on Twitter

Microsoft Windows Platforms Blog Watch

KKline — Wed, 20 Jul 2011 14:44:00 GMT

Remote Desktop Services Component Architecture Poster

Grab your own poster! A visual guide to key Remote Desktop Services technologies in Windows Server 2008R2

Virtually Free

Get the latest update rollup package for the Hyper-V role in Windows Server 2008 R2 and be sure to bookmark the Windows Virtualization Team Blog. Be sure to check out blog World Simplified is a Virtual World. And doncha evah neglect application virtualization, such as the goodness at the App-V Product Team Blog.

Let's Optimize Some Desktops (Assuming You Have Gone Full Cloud Yet)

Check out The Official Microsoft Desktop Optimization Pack (MDOP) Blog where you can get cool tools like the Diagnostics and Recovery Toolset (DART), currently in its v7 beta release.

We Can Always Perform a Little Better

Have you checked out the Ask the Performance Team blog yet. You should! Then there's the Microsoft Enterprise Networking Team blog. And if you're looking for help with the Windows Server Core, be sure to check out the Ask the Core Team blog. Excellent stuff! As the Tool Time columnist at SQL Server Magazine, I'm always on the lookout for great free tools that get on-going support from their creators. One common experience is finding a nice debugging tool, only to discover that there's no information on how to interpret the debugger result sets! (SQLIOSim anyone?) That's why I love the Microsoft Advanced Windows Debugging and Troubleshooting blog. Another must-have on your Favorites list.

Enjoy!

-Kev

Follow me on Twitter

Is There Such a Thing as Easy ETL?

KKline — Thu, 30 Jun 2011 04:57:00 GMT

E.T.L. That's Extract - Transform - Load. That doesn't sound like a lot of work when all you need to get loaded is a simple Access database or an Excel spreadsheet. In a situation like that, the process is so simple, all you really need to focus on is the L in ETL. There's not a whole lot of E.T. to process, despite how wonderful that movie is. [pun intended] But as soon as your data loading process involves some difficult or sophisticated cleansing or transformations, it gets really, really hard. The other cross-thread that had really caught my interest lately is the USA federal governments Open Data Initiative. I think it's remarkable that President Obama is the first president to appoint a federal CIO. (Shouldn't that have happened in the past?) In addition, President Obama instructed the entire executive branch to open up their data (where security isn't at risk) and make it readily available to the public. And the US government collects mountains of interesting and valuable data for its own uses, but figuring out how or who to share it with was always an afterthought. While I was a contractor for NASA, for example, I worked on some incredibly interesting projects which yielded amazing and commercially valuable information. It was all public domain. But unless you knew it was there, you couldn't get to it. Making use of all of that data always intrigued me. Now, with ODI, it's all being put on the internet at an ever-increasing rate at Data.gov. However, all of this data, while open and available, is not standardized. Some data sets might be a CSV file, while others might be something like a spreadsheet. That means you'll need to extract, transform, and load that data if you want to synthesize more valuable data sets. For those reasons, I've been researching tools to help make this process easier. (I also wanted to research SSIS and ETL tools for my Tool Time column in SQL Server Magazine.) Now, I've been following expressor software for quite some time and really like their unique approach. (I actually ran into the expressor software team at a PASS Summit one or two years ago and asked for a demo of their software. And I really liked what I saw.) Rather than the workflow approach used by SSIS, expressor software uses a data mapping approach combined with reusable business rules. Their mapping approach is fundamentally different from the traditional point-to-point, source-to-target mappings paradigm. Basically, you can define a semantic type representative of your business data, create a business rule(s) to apply to the data, and then implement a "canonical" mapping which connects data sources and targets to that same semantic type. And it's free!

Abstraction is Awesome

What's cool about that? Don't forget that "semantic" means "meaning". So a semantic type is an abstraction of the meaning of the data. The net result is that expressor shields your data integration application, with its associated business and transformation rules, from changes that might occur to underlying target or source files with different field names and data type representations have to be processed. For example, let’s assume that you need to process invoices from different vendors in slightly different formats. If you use a traditional ETL tool like SSIS, any changes in the source and/or target formats will require you to modify your data mappings and transformation rules, because the mappings are tied directly to the metadata structure of the invoice file format(s). expressor, on the other hand, lets you define a common “invoice” semantic type, build all your downstream data processing off that type and map one or multiple invoice file schemas to the type. This approach greatly simplifies the mapping process and provides for more flexible data integration applications that can be more easily adapted to changes in the source and target data sources.

Benefits Abound

Since the semantic types in expressor are captured as reusable artifacts, you can also reuse them again in new data flows within your project(s). You can even share them across your entire organization. As I tinkered with the expressor Studio tool, I hit on a few other benefits with this approach:

Handles data type conversions automatically without having to write data transformation rules for these conversions
Builds new semantic types from existing types and reuses types in existing and new applications
Creates multiple, reusable business rules against a single type and applies them repeatedly as needed
Easily implements data quality rules and constraints

In an Ideal World...

In an ideal world, I'd figure out some brilliant way to make money from bringing together all kinds of that government data that I used to work with. Other folks are doing it at the Windows Azure Data Market. But in the meanwhile, I'm also looking forward to tinkering with this data to build better demos. Along the way, I'm going to use the expressor Studio desktop ETL tool (Did I mention that it's free!) as well as tell you about my experiences as I try to build out some Data.gov data sets. Those of you who know me, know that I look a good discussion and cooperative, constructive team work. So I encourage your feedback and suggestions, as I work through these data integration challenges and share my experiences. I'm looking forward to sharing with you my insights on what the expressor data integration software can do with this challenge and what some of its features and capabilities are. In upcoming releases, I'll let you know what I find intriguing and worth mentioning. Check out their website, www.expressor-software.com, to learn more about their company and products. Enjoy, -Kev Follow me on Twitter More content on KevinEKline.com

New on SQLMag - Automating the Startup and Shutdown of Windows Services

KKline — Tue, 27 Apr 2010 22:21:00 GMT

I just posted a new blog entry on how I automate the shutdown and startup of Windows services.

Check it out at http://www.sqlmag.com/blogs/tool-time.aspx. Be sure to let me know what you think and if you have your own unique methods for automating the control of Windows services!

Many thanks,

-Kevin
-Twitter @kekline
-More content at http://KevinEKline.com