In part one we developed a query that nets us some cool performance metrics and compacts the big-ugly syssislog into a more readable format. In part two, we’re going to use SSRS to visualize that data. If you’re using SQL Server 2012, checkout the Execution And Logging Reports. For the rest of us pedestrians on SQL Server 2008 or 2005, there is a download button at the bottom of this article filled with SSRS reports that will create an SSIS monitoring dashboard. These will query the sysssislog and present that data in a similar fashion. When you execute the report, here is what you should see… Continue reading Simple SSIS package monitoring for SQL Server 2008, Part Two
Business Intelligence analyst have been using SSIS for almost a decade now and yet we still have no centralized place to answer some very common operating questions. Such as…
- How many packages do we have?
- How often are they run?
- How are they configured?
- How are these packages performing over time?
Microsoft recently addressed this in their latest version of SQL Server 2012 by introducing the SSIS Catalog and the new Execution and Logging reports. They enable a fast way to visualize and troubleshoot performance.
But what about those of us still using SQL Server 2008 or 2005? Are we left without a way to visualize our package environment? Continue reading Simple SSIS package monitoring for SQL Server 2008, Part One
I haven’t visited Wolfram Alpha in years, but I have fond memories. It was a major contributor to my passing score in multivariable calculus. Thankfully, my lack of patronage hasn’t slowed down the good work of physicist and founder Mr. Stephen Wolfram. Today the team at Wolfram announced another scientific breakthrough. Wolfram Alpha is now capable providing a full social analysis of your facebook activity. That’s right! Think you’re a social outcast? Now we can back that up with HARD data.They are calling it a facebook report. You can get your report by visiting the site and typing facebook report into the search bar.
The website will redirect you to facebook and ask for your permission to gather data and build your report, but the resulting explosion of graphs, drill down data, and infographics is totally worth it.
The Internet 2.0
Internet Service Providers like AT&T are slowly providing IPv6 service to their customers, but if your ISP doesn’t currently assign your household a public IPv6 address then you’ll need the help of a tunnel broker to get you connected. Why is getting connected to the IPv6 internet that important? Honestly, for casual users, its not. But geeks know that some things are only available if your home network has an IPv6 address. Whether you just want to finally see the dancing kame, or you want access to some of the IPv6-only goodies like free usenet servers, the following guide will get you started creating your first 6in4 or protocol 41 tunnels. Read more to find out how to get your home network off the IPv4 island and connected to the internet 2.0.
The little router that couldn’t
Part 1 of Working with Uverse covered a Uverse install, upgrading the speed, and discovering problems with DNS. Since the NVG510 forces customers to use AT&T’s flakey DNS
servers implementation, Part 2 is intented to resolve that. It will guide users in relieving the NVG510 of it’s DNS-chokehold and pass control to an alternate, more accommodating router. Ron Berman has a comprehensive page setup to help answer common questions about the NVG510. As a reference, I’m going to follow his steps while providing screen captures of process. Warning: the official word from AT&T is that migrating away from their DNS servers may degrade the performance of their streaming service. But I haven’t experienced any so far. However, if you have TV service through AT&T and notice a degradation or improvement after making the following changes, please let me know in the comments. For those with Internet service only, please read on for a path to DNS salvation. Continue reading Working with Uverse and DNS. Part 2 – Ditching the NVG510
Help for new customers, and a first week review of AT&T Uverse.
When AT&T announced that they were bringing Uverse service to my neck of the woods, I found myself checking their availability web page more often than I checked my old rusted mailbox. It was only a matter of time before my dreams of tripled internet speed came true. I’m pretty sure I simultaneously shouted in joy, signed up for service, and possibly peed – just a little. I’m a bit ashamed, but how else can I explain it? For a techie, the anticipation created by “faster internets” is equal to a junkie knowing he is about to triple his supply. It was probably that same geeky-level of anticipation that made AT&T’s gloriously botched install job all the more painful. In typical “too-big-to-function” fashion, it took no more than two “IP-DSL tier 2” tech-support phone calls, five on-site tech visits, and ten days of waiting before they finally got me up and running. Not exactly smooth transition from DSL, but I was confident that together AT&T and I could thaw that icy start into water under the bridge. All I needed to do was witness my first Uverse-delivered web page. Continue reading Working with Uverse and DNS. Part 1 – Installation and Testing