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 do 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…

 

Another change in jobs: and upcoming events

Recently I was forced to make a job change. 

I am now working for a reputable local bank as a DBA and I am no longer a consultant.  l enjoyed my time as a consultant even though I never could get used to the idea of being “billable”.  And putting the fate of your job in the hands of other individuals (sales department) was nerve racking to say the least.  But I learned valuable skills and information from my time as a consultant.

I hope to continue participating in the SQL community.  In fact, I am presenting my newest presentation “You want me to Isolate What? An Introduction into Data Integrity and Isolation Levels of SQL Server” THIS Saturday at SQL Saturday Pensacola #617.  Of course I will upload my slide deck and demos after this weekend.

And you can catch me in two weeks at SQL Saturday Houston #651.

Hope to see you there!

Expanding a DBA’s Role

I have never really considered my self a System Administrator, but I am familiar enough with the Windows Operating System to consider myself a little dangerous. However, with more and more of our clients utilizing the power of Microsoft Azure VMs I see my role as a SQL Consultant starting in encompass System Administrator duties.

Recently a client found this article on “Best Practices for SQL Server in Azure Virtual Machines” and wanted to re-provision his volumes to adhere to them.

No my first thoughts was wait, I’m a DBA, not a System Admin that’s not my role! But thinking more about it I realized the client views this as a SQL Server issue and I am the SQL Server Consultant and that it is my job to remedy this problem.

Not being 100% confident in Azure, I spun up a VM SQL Server and attempted to add some volumes.  To my surprise, this was way too easy.

After selecting the server I wanted to manage….

Step 1:    Select Disk on the left menu and then click “+ Add Data Disk”AddingDisks1 

Step 2: Configure Disk

  • You will need to provide a name or you can use the pre-populated name
  • Select Source Type, in this case I left it at the default “New (empty disk)”
  • Select Account Type, again, left it at the default of “Premium (SSD)”
  • Choose the Size.  From 0 t0 1023 which is a Terabyte of space.
  • Select Storage Container.  This will open another tab and just pick the one you want or create a new one
  • Storage Blob name – once again you can use the pre-populated name

AddingDisks2

Step 3: Select a Container

This is where the actual VHD file will reside, you can use an existing container or create a new one for these files

AddingDisks3

 

That’s it!  That is all that is need to mount a new volume to an existing VM SQL Server. It automatically populates in the OS Disk Management where you will need to create a “Simple Volume” (or however you would like to do it) and format the drive (remember MSFT recommends 64K for data and log drives)

You are now ready to do. 

And removing an existing drive is even easer.  At the top of the Disk Panel is the work “Edit” click there and you are given the option to delete. It will automatically remove it from your server, no reboot no warning!  So be careful.

Heck, maybe being a System Administrator in Azure isn’t so tough after all!