License requirements for SSIS on VMRole in Azure - azure

We are running integration services (SSIS) on a VMRole on Azure. I understand the Win 2008 OS license requirements but can someone shed light on the license requirements for using SSIS in a VM Role? Do we need to obtain a production lic for SQL server? IF that is the case doesnt that defeat the cloud utility model?
Any insight is appreciated.
Thanks.

I'm not an expert on the licensing strategies of Microsoft, but SSIS is not a supported product under Azure special licensing. Only Windows Server "Azure edition" if you will is included in the cost of an Azure VM. And obviously, SQL Server license of SQL Azure is included in the price of SQL Azure. Nothing about external to the cloud-based Azure ecosystem SSIS is covered, afaik.

Related

Difference between Azure database for MySQL and Azure SQL database

I am learning azure from Microsoft learn using this link. Does anyone know the basic difference between "Azure Database for MySQL" and "Azure SQL Database"? Both seem very similar.
As I am a beginner, can anyone explain the difference in an easy way?
Add to #CoderRambo's answer. The difference between Azure Database for MySQL and Azure SQL Database is as follows:
Azure Database for MySQL is powered by the MySQL community edition. We can choose versions 5.6, 5.7, and 8.0.
Azure SQL Database is SQL Server database engine, based on the latest stable Enterprise Edition of SQL Server.
The only similarity is: they are all hosted in the Microsoft cloud and fall into the industry category of Platform-as-a-Service (PaaS). So your question is mysql vs sql server.
ok lets start with what is common for both. with Azure prefixed, both are installed in cloud and managed by Microsoft. Meaning Microsoft is responsible for the databases to be installed, up and running with 0 or minimal downtime. I think this is clear.
Now lets start with differences. Please visit the links below and let me know if you have any issues. Thanks!
https://www.guru99.com/sql-vs-mysql.html
https://www.javatpoint.com/mysql-vs-sql
Mysql is opensource database, where as when you say SQL it refers to Microsoft SQL Server.
In general both are two different types of databases. Microsoft SQL Server is a licensed version.
When you prefix them with Azure, it means they are hosted on cloud , i.e Azure cloud and Microsoft manages them as PAAS(platform as a service).
Kindly let me know if you need more information.

Best practices when deploying Dynamics CRM to Azure virtual machines

Are there any recent best practices / guidance for deploying Dynamics CRM (eg 2016) to Azure virtual machine IaaS (eg Windows Server 2016)?
In case you ask, we are pursuing this to control licensing costs.
I'm familiar with the Microsoft whitepaper from 2015, Deploying Microsoft Dynamics CRM in Microsoft Azure Virtual Machines, but it is somewhat dated and Azure / cloud service providers have evolved tremendously in the past 4 years.
Are there any newer best practices / guidance? Are there any gottchas?
I've looked in some depth at SQL Server 2016 on Azure virtual machines, some examples of the Azure-specific guidance there would be:
tempdb on D: ephemeral disk (credit Brent Ozar)
backups on storage blogs mapped by URI (credit Microsoft in DBA Stack Exchange)
storage spaces (pools) for enhanced performance of Azure data disks
several Azure Quickstart Templates for SQL Server
etc
There is no mention of Dynamics (CRM or otherwise on-server) in the Azure Quickstart Templates.
I'm looking for equivalent guidance for Dynamics CRM on Azure VMs.
You are probably not going to find any Azure Templates for CRM because Microsoft is generally trying to push everyone to use Dynamics 365 Online. Without knowing your situation, that would always be my recommendation since you're essentially trying to create a cloud hosting solution for a product with a cloud hosting solution.
However, I understand that there are circumstances that would prevent this.
With that said, the guide seems relevant even if it's outdated. You can still set up the VMs using the plan recommended in the guide even if the steps may change.
Also, whenever I set up on-prem hosting, I would need to set up an ADFS server. This was always a separate VM that only ran ADFS and nothing else. Fortunately, Microsoft Docs have a pretty reference for creating ADFS in Azure.
https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs

SSRS report deployment on azure

I am using SSRS report in my web application now, I want to deploy SSRS report on azure, I found one option using azure VM but its costly as I am using free account, Is there any other option?
Please suggest me the proper way.
Now spinning a SQL Server VM might result in costs way higher than you might expect (due to licenses), so always make sure you run it on a version of SQL Server Developer, which has all the features of the highest SQL edition, but it is free (not to be run in production). See here.
If you use one of the SQL Gallery Images, then you don't need an additional SQL Server license. See Azure VM pricing here
You can try Pay-As-You-Go option
You need to be more specific - the cost of licensing what? Azure SQL Reporting? Virtual Machines? SQL Server licensing?
you would have to set up SSRS somewhere. Azure-hosted VM depends on a lot of factors such as your budget, on-premise infrastructure capacity, overall cloud strategy of your organization.
Licensing - Azure lets you pay directly for VMs that include SSRS. For example you can get SQL Server Standard 2012 (which includes SSRS) on a "Small" Server 2012 vm for about

Azure VM and SQL Azure

My web project uses an software, which need to be installed on destination PC. So, I have to use Azure VM and no way to use Azure Cloud Service, right?
Also, can I use SQL Azure with Virtual Machine?
You can install any third party software on Azure Web/Worker roles (Cloud Services), as long as the installer supports a quiet/unattemded install from a command line with switches. Learn more how to do this via StartUp tasks here.
As for Azure SQL Database - you can use with any combination of services. Even with on-premises only solution. You have to take care of Firewall rules.
Azure SQL Database tends to be much less expensive than a VM with SQL Server installed. It won't run on a VM but you can access an Azure SQL database from an VM or web application in the same way you access local databases - You just set the connection string to the Azure SQL connection string.
There is an excellent post that can help you with in order to understand how to configure customization with cloud services.
microsoft-azure-cloud-services-part-4-lifecycle-and-customization-of-your-vm
As the link explains there is nothing persisted on a cloud service VM but this is not a limitation instead a good practice which allows easy scaling out by adding more instances if required.
You can use Azure PaaS SQL just like a SQL server installed on a different server then your web server with some limitations. Please have a look at the link below from MSDN to understand these limitations.
sql-database-transact-sql-information

How do I develop for Azure without using a live SQL Azure instance?

I have a BizSpark account and I get some Azure freebies from Microsoft. But, I'm forced to create a live SQL Azure database to use in my local development. This slows me down a bit because I have to read/write over the wire when I'm developing, and I must remain connected at all times.
Is there a way, or a technique, to build locally and have my deployments access the express edition of SQL Server on my machine? I'm using EF4 to access the database.
First of all, as a part of Bizspark, you get 3 SQL Azure databases for free. http://msdn.microsoft.com/en-us/subscriptions/ee461076.aspx
This will allow you to have 1 DB for testing, 1 for dev, and 1 for production
If this does not work out for you, you CAN develop on your local SQL Express and keep deploying your changes to SQL Azure as you deploy your application to Azure. There are two tools that help you here:
1) open-source SQL Azure Migration Wizard: http://sqlazuremw.codeplex.com/ -- we personally do not use this for deployments, so I am not super knowledgeable to comment on this. It is a decent tool to back your SQL Azure database.
2) You can use Red Gate's SQL Compare product, as of v9.0+, they support synchronizing cross SQL Azure and on-prem SQL servers. We use this for AzureWatch and are very happy. It is commercial product and is somewhat pricey.
HTH
+1 to Igorek's answer - plenty of good suggestions there.
In addition to his advice, if you are a BizSpark licensee then I suggest you deploy full SQL Server 2008 R2 to a local box and develop against that.
There are differences between full SQL Server and SQL Azure - you should read around to be aware of these - http://social.technet.microsoft.com/wiki/contents/articles/comparing-sql-server-with-sql-azure.aspx
As long as you are aware of the differences (especially the SQL Azure limitations) then migrating back to SQL Azure later, should be reasonable.

Resources