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…

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!