I know I’ve been really slacking on getting this year judges list for speaker idol posted. A lot of this is just because of everything else that’s been going on leading up to the PASS summit, specifically my insane travel schedule to SQL Saturday’s Microsoft Ignite, and the SQL 2017 Launch, and shifting the schedule to slide the judges in where possible so there are no conflicts.
Without delay, and in no specific order, here are your 2017 Speaker Idol Judges.
- Karen Lopez
- Joey D’Antoni
- Kendra Little
- Mark Simms
- Allan Hirt
(Even spelled correctly this year)
I know our judges are going to give all 12 of our contestants some great feedback, and they are going to do a great job picking out first PASS Summit 2018 speaker.
The post PASS Summit 2017 Speaker Idol Judges appeared first on SQL Server with Mr. Denny.
We’ve had another change to the PASS Summit speaker idol line up. Tzahi has had to withdraw due to work commitments and won’t be able to attend the PASS summit at all this year. Which is good news for Jeremy Frye as he will be taking the open spot. Like all the contestants we with Jeremy the best of luck and we’ll see everyone at the PASS summit.
Your new and improved speaker idol line up now stands at:
Your Wednesday lineup for speaker idol is:
- Jim Donahoe
- Brian Carrig
- Jonathan Stewart
- Robert Volk
Your Thursday lineup for Speaker Idol is:
- Javier Villegas
- Eric Peterson
- Ed Watson
- Dennes Torres
Your Friday lineup for Speaker Idol is:
- Daniel de Sousa
- Joseph Barth
- Jeremy Frye
- Simon Whiteley
The post PASS Summit Speaker Idol Lineup Change Redux appeared first on SQL Server with Mr. Denny.
Building, implementing and executing a proper DR plan successfully is a challenging undertaking. It is a lot more complicated
than most experienced IT professionals and/or consultants think it is. This is because there are a LOT of moving parts to build a DR platform that’s going to fail over and allow the application to keep working. I’ve been bringing this point up in my sessions a lot recently. Our job in IT isn’t to build the cool, slick, sexy, solution. Our job is to make it so that the sales guy can sell widgets. Whatever widgets your company sells, the job of IT is to help the sales guy sell widgets. If the sales guy can’t sell widgets (and the shipping department can’t fulfill those orders and everything else that goes with selling widgets) then your company doesn’t get paid. If the company doesn’t get paid, then you don’t get paid. Then you have a pissed off spouse, and a pissed off mortgage company. And these aren’t good things to have. So let’s get back to talking about helping the sales team sell widgets.
HA Failover is pretty straightforward. There’s no data loss, everything is done using two-phase commit as it’s all inside the data center. So I don’t want to talk about that. I want to talk about when things really fall apart. The production site fails. Things are getting really interesting. Lets design for this.
just talk about what we need to think about.
- Active Directory
- IP Space
- Connection String Issues
- Remote Access
- End-user application access (web front end)
- Employee access (web / fat client)
That’s a lot of things that have to be thought about. You’ll notice that I haven’t even talked about the database stuff yet. Once we get into the database stuff starts getting more complex.
- Recovery Point Objective (RPO)
- Recovery Time Object (RTO)
- Am I using features that make availability groups not supportable (probably not on current versions)
- How many replicas do I need?
- Am I correctly licensed?
- Can I do this in the cloud?
- Should I do this in the cloud?
- How many values do I need to skip for sequences and IDENTITY columns?
This is clearly a complex topic. Because of this, we’ve put together a roundtable of experts on high availability and disaster recovery to have a roundtable discussion to talk about some of this complexities that there are that people stumble on. The webinar will be at 11 am Pacific Time / 2 pm Eastern Time on Tuesday, October 24th.
To register for the webinar so that we can remind you about it, click over to our registration page. Download the Outlook calendar entry and we’ll remind you when it’s time for the webcast. Can’t make it on the 24th? No problem. We’ll be recording the webcast and sharing making it available for viewing after for free.
When it comes to DR, you only get one chance. If you screw it up the company goes out of business so you really need to be taking your DR planning experience from the very best. And that’s who we have scheduled for our round table.
The post DR is more than just building an AG appeared first on SQL Server with Mr. Denny.
I’ll be honest, when I first learned about SQL Server on Linux, I didn’t get it. It took like an hour for it to make sense to me. After a week of talking to customers, a lot of whom were super interested in deploying SQL Server on Linux or SQL Server in Docker it just makes even more sense to me.
Let’s run down the various use cases, then let’s dive into each one and break them down.
- LAMP stack developers
- Small SQL Instances for 3rd party apps
- Shops which are primarily Linux shops today and want/need to deploy SQL Server
- Shops who want to replace Oracle, MySQL, and/or PostgreSQL
Let’s explore each of these a little more, shall we?
LAMP stack developers
There’s LOTS of developers out there that when they start a new project they fire up new containers and grab PHP, a database (MySQL, PostgreSQL, etc.) and go to town programming away. Microsoft SQL Server being available for Linux and having it being just a quick docker download (or yum install) away gives them the option of having a full enterprise class database behind their application with a quick, easy 2 minute config that’s like 3 questions, for the same cost in development. And when they go to deploy their application to their users (customers) they have the confidence of telling them that the database they they’ve selected is Microsoft SQL Server, supported by a multi-billion-dollar company which they are probably used to dealing with already.
The developer can build their application with confidence knowing that the programming surface is identical between the Linux and Windows versions of the product so they can expect it to react exactly the same no matter if the customer installs it on RedHat, Ubuntu, Docker, or Windows.
Small SQL Instances for 3rd Party Apps
An interesting potential workload that a car manufacture brought up while I was working the booth at the Microsoft Ignite conference, was small database applications like 3rd party applications, or even 1st party applications but which are typically single core VMs with small memory footprints. Today they take up a large percentage of the VMware farm, and what did I think of moving these into a Linux host running Docker containers and running really small containers (assuming that the CPU and memory were fine). My response, sounds like a great use of the docker deployment of SQL Server on Linux.
The docker deployment is going to give you a really thin, really lightweight deployment option as you don’t have to worry about deploying the OS within the VM. In a large host running dozens of containers this could led to some major resource savings.
There are lots of companies which are primarily Linux and don’t want to run or manage Windows servers for one reason or another, but they often have to because they need to support SQL Server to support either line of business applications or back office business applications such as HR applications or payroll applications, even if those applications are Java applications running on Linux servers.
Now those companies can toss their Windows servers and run Linux OSes that they are used to running and still have the SQL Server database that they need to run their applications. The power to do what you need to do, to run your organization and the flexibility to do it the way that you want to do it without any vendor lock in. It’s like Microsoft has been listening to the Linux community or something (no they aren’t going to open source SQL Server, stop asking).
I was shocked the number of people who came to the booth, knowing that I do not work for Microsoft, telling me that this gives them the ability to replace Oracle, MySQL or PostgreSQL in their shops. Most of these companies were primary Linux (or all Linux) server OS shops so suddenly having the flexibility to get out from under the thumb of their Oracle sales rep while staying on their server OS platform of choice, is huge. One customer came up and said that even after the cost of converting their applications from Oracle to SQL Server (which was not going to be cheap), and the cost of paying for the SQL Server licenses, the annual savings was still in the millions because of the Oracle licensing costs. I’m guessing that the Oracle sales guy really isn’t going to like that phone call, but his car is nice enough already.
Given that it’s only been out for a few days, that’s good start.
The post So, what’s with this whole SQL Server on Linux thing? appeared first on SQL Server with Mr. Denny.