Azure SQL Data Warehouse is a fully managed, elastic data warehouse-as-a-service for processing enterprise workloads.
The process of loading data into a traditional data warehouse typically follows the pattern of Extracting, Transforming, and Loading (ETL). Most businesses use a dedicated server to perform these operations.
However, with MPP architecture and the ability to load data fast, the new standard is becoming Extract, Load, and Transform or ELT.
The “Cloud” is surrounded with so much marketing hype we may rightly expect to be awestruck when we come into contact with it. In reality, the cloud is becoming more and more a part of our everyday lives in ways that probably go unnoticed. If you are unsure what a cloud app is, check out our previous post: What is a Cloud App.
Much of the buzz surrounding all things “tech” now revolves around a single word: “Cloud.” The “Cloud” is everywhere. The “Cloud” is all-knowing. The “Cloud” is curing the diseases that science did not even know existed. “Cloud Cloud Cloud!”
The “Cloud” is surrounded with so much marketing hype we may rightly expect to be awestruck when we come into contact with it. In reality, the cloud is becoming more and more a part of our everyday lives in ways that probably go unnoticed.
As the technology demands of today's business environments expand, protecting both virtual and physical assets becomes an increasingly complex matter. As such, multiple disaster recovery solutions are often required to address the entire technology infrastructure.
However, this added complexity adds cost and creates doubt as to whether the DR solutions will actually work as intended when everything "hits the fan."
Microsoft's Operations Management Suite (OMS) eliminates the complexity and offers a comprehensive disaster recovery solution for VMware, Hyper-V, and physical servers to analyze, manage, and protect your business.
Answering Automation - Project Planning Questions
In this series, we set out to answer some common strategic and project questions about Automation. In the previous blog posts, we’ve talked about what automation is, and how to decide what functions and processes should be automated. Now we are going to tackle project planning questions, or issues that come up once you the target of automation is chosen, such as:Where do you start?
How far do you go?
How do you know when you are done (at least for the moment)?
Previously, we’ve talked about some broad concepts, but these questions are a little more narrow and practical.
Let’s dig in!
Application development is tough. CIO.com reported the typical development time for an iOS app to be 12 weeks, and that does not include the time needed to research, plan, or develop the scope properly. Nor does it factor in development time for “other” necessary mobile or desktop environments.
Suffice it to say, the complexity of the business requirement is proportional to the development time and resources needed to complete the project. Therefore, it is incumbent for companies to gain efficiencies from all available avenues in order to “go to market” within the window of profitability the business case requires.
Developing your app in the cloud can provide these efficiencies.
What is PaaS?
Platform as a service (PaaS) is a complete development and deployment ecosystem for the cloud.
PaaS hides the complexity and need to manage the underlying infrastructure. With PaaS, businesses can avoid the expense and complexity of buying and managing the disparate software licenses and the underlying application infrastructure and simply manage the applications and services they develop.
For example, PaaS services on Azure include:
- Web servers
- File storage
- Message queues and service buses
- Machine learning services
- Big data services
Answering Automation - What should we Automate?
In our last blog article (What is Automation?), we talked about some of the broad, common questions about tackling an automation initiative in IT. We said that automation is the use of applications, integrations, and runbooks to configure solutions that remove manual work from IT, and that is important because it reduces costs, improves accuracy, and overall improves the customer experience.
We also broke out automation into three buckets:
- Apps, which are tools that automate some work in a standard way.
- Integrations, which let systems talk to each other and perform automation that way.
- Runbooks, which take a complex process and work through it in multiple technologies from end to end.
What is automation?
Automation is a broad set of practices, and never is that truer than when an organization sets out to automate a function, process, or solution. There are several questions that get asked when an initiative to automate begins, such as:
- Where do you start?
- How far do you go?
- How do you know when you are done (at least for the moment)?
In this blog series, we are going to help you answer these questions and give you tools to help educate your organization and promote automation throughout your enterprise.