Don’t forget me when I’m gone!

It has been almost exactly one year since my last post and quite frankly, I am embarassed, ashamed and down right just feeling close to failure.

But I hope to change that!

My last post announced that I was going to document my learning with PowerShell. Since then, SQL 2019 has been released and there are so many new “toys” with SQL! But before I go into that, I really must finish what I started.

Today, I not only downloaded SQL 2019 Developer Edition to install, but I also actually installed DB Tools for PowerShell!!!

Let’s get this Party Started!!!

Learning something new!

old-dog-new-tricks

You all know the old saying, “Can’t teach an old dog new tricks”. Well I am here to tell you, I AM old (at least in the IT world) and I can learn new tricks.

After study, testing, studying and testing; I finally passed enough exams to earn my Microsoft Certified Solutions Expert: Data Management and Analytics Certification. (Yeah me!). This is not to brag and this was not required of my job, but a personal endeavor for me to complete it. Yes, I know some people put zero stock in MSFT exams and certificaitons and I understand that, but again this was a personal goal.

So what’s next?

I know in the IT world if you are not always learning something new you will be left behind and become a dinasaur real quick. Since my current job role is primarily “to keep the engine running” and we have over 100 instances of SQL; I felt I needed to expand my toolbelt. The first logical option is Powershell for SQL and DBAtools (http://dbatools.io)

I know there are 100s if not 1000s of blog posts about SQL Powershell, but I hope to document this learning (i.e. take notes) and hopefully I can retain some of this information, because you know I am getting old and such!

Missing in Action (not really)

I know it has been a while since my last post, but when one is working, I mean really working, a full time job, plus kids, hobbies, and everything else, where does one find time to blog???

My work though is allowing me to learn new things, delve into different areas and become more proficient with SQL 3rd party tools.

Right now I am working on a T-SQL security report. A simple, or not so simple, batch of t-sql that will provide 2 options: 1) full or 2) deficiencies.

Option 1 will give you a list of every server principal in the system and what permissions it has, all the way down to the object level. Option 2 will only provide you with the things that need to be remedied based on security best practices.

The future is Power(ful)

I am finally geting around to reading up on SQL Server vNext 2017 which will hopefully be released sometime this year.

Of course we have all been spinning up RedHat boxes so we can play with SQL on Linux (btw, this does not excite me), but something else caught my eye that made me step back, scratch my head and say “uh, excuse me”

I found this statement to be very troublesome.

  • SQL Server Reporting Services is no longer available to install through SQL Server’s setup as of CTP 2.1.

(https://docs.microsoft.com/en-us/sql/sql-server/what-s-new-in-sql-server-2017)

SSRS is no longer available?  Say WHAT?

Reading on I discover that it is now “Power BI Report Server”, in the cloud or a downloadable on premise with desktop version. (https://powerbi.microsoft.com/en-us/documentation/reportserver-get-started/)

Truth be told, I have not experimented with anything “Power” since MS PowerPivot and Excel.  (Hey I’ve been busy with Admin stuff.  Yes, I know I need to get into the current decade.)  This looks to be a promising direction MSFT is taking SQL Reporting.  What I have seen of Power BI through blogs, SQL Saturday’s and other presentations, I have been somewhat impressed with its capabilities.

I am just concered about converting all those 2008 – 2016 SSRS reports to PowerBI!  Well, at least it is job security!

Until next time…