1 / 3

SQL Azure Online Training | Azure SQL Training

Visualpath is the best source to learn SQL Azure Online Training. We are providing Instructor-Led Online Classes by our Experienced Faculty and project Explanations are available. For more information contact us @ 91 9989971070.

bhanusree
Télécharger la présentation

SQL Azure Online Training | Azure SQL Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Azure SQL Database vs Azure SQL Data Warehouse Case As we gradually move from on-premises information distribution centers with Microsoft SQL Server to cloud information stockrooms in Microsoft Azure, we have to find out about the different choices in Azure. Arrangement In 2013, Microsoft presented Azure SQL Database which has its source in the on- premises Microsoft SQL Server. In 2015 (anyway open accessibility was in July 2016) Microsoft added SQL Data Warehouse to the Azure cloud portfolio which has its inception in the on-premises Microsoft Analytics Platform System (APS). In this post we will quickly depict the contrasts between these two Microsoft Azure Services, however first Microsofts possess definitions: •Purplish blue SQL Database is a social database-as-an administration utilizing the Microsoft SQL Server Engine (more); •Purplish blue SQL Data Warehouse is an enormously parallel preparing (MPP) cloud-based, scale-out, social database equipped for handling huge volumes of information (more); Contrasts 1) Purpose: OLAP versus OLTP Albeit both Azure SQL DB and Azure SQL DW are cloud-based frameworks for facilitating information, their motivation is extraordinary. The greatest contrast is that SQL DB is explicitly for Online Transaction Processing (OLTP). 2) Architecture So as to make the distinctions all the more clear a snappy see of the engineering of Azure SQL Data Warehouse, where you see an entire assortment of Azure SQL

  2. Databases and isolated stockpiling. The most extreme number of registering notes right now is 60. 3) Storage size The present size farthest point of an Azure SQL Database is 4TB, however it has been getting greater in the course of recent years and will presumably wind up around 10TB sooner rather than later. 4) DTU versus DWU SQL DB has 15 distinctive valuing levels which indicate the quantity of Database Transaction Units (DTU) and the capacity size/type: - Basic - Standard (S0, S1, S2, S3) - Premium (P1, P2, P3, P4, P6, P11, P15) - Premium RS (PRS1, PRS2, PRS4, PRS6) 5) Concurrent Connection In spite of the fact that SQL DW is an assortment of SQL Databases the greatest number of simultaneous associations is a lot of lower than with SQL DB. SQL DW

  3. has a limit of 1024 dynamic associations where SQL DB can deal with 6400 simultaneous logins and 30000 simultaneous sessions. 6) Concurrent Queries Other than the most extreme associations, the quantity of simultaneous inquiries is additionally a lot of lower. SQL DW can execute a limit of 32 questions at one minute where SQL DB can have 6400 simultaneous laborers (demands). 7) PolyBase Sky blue SQL Data Warehouse underpins PolyBase. This innovation enables you to get to information outside the database with standard Transact SQL. It can, for instance, utilize a document in an Azure Blob Storage compartment as an (outer) table. 8) Query language contrasts In spite of the fact that SQL DW utilizes SQL DB out of sight there are a couple of minor contrasts while questioning or making tables: - SQL DW can't utilize cross-database questions. So the entirety of your information ought to be in a similar database. - SQL DW can utilize IDENTITY, however just for INT or BIGINT. Besides, the IDENTITY segment can't be utilized as a major aspect of the dispersion key. - Also, see this SQL DW rundown of unsupported table highlights. 9) Replication SQL DB underpins dynamic geo-replication. This empowers you to design up to four intelligible auxiliary databases in the equivalent or various areas. SQL DW doesn't bolster dynamic geo-replication, just Azure Storage replication.

More Related