%3CLINGO-SUB%20id%3D%22lingo-sub-1513355%22%20slang%3D%22en-US%22%3EComprehensive%20workload%20management%20capabilities%20for%20your%20analytic%20workloads%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1513355%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fsynapse-analytics%2Fsql-data-warehouse%2Frelease-notes-10-0-10106-0%23may-2020%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWorkload%20isolation%20in%20Azure%20Synapse%20Analytics%20is%20now%20generally%20available%3C%2FA%3E%20where%20you%20can%20use%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsql%2Ft-sql%2Fstatements%2Fcreate-workload-group-transact-sql%3Fview%3Dazure-sqldw-latest%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eworkload%20groups%3C%2FA%3E%26nbsp%3Bto%20reserve%2C%20contain%2C%20and%20manage%20resources%20across%20different%20workloads%20running%20on%20your%20SQL%20pool.%20Previously%20users%20had%20to%20provision%2C%20secure%2C%20and%20manage%20multiple%20pools%20with%20different%20endpoints%20orchestrating%20additional%20ETL%20processes%20to%20achieve%20workload%20isolation%20and%20avoid%20resource%20contention.%20This%20can%20become%20an%20expensive%20and%20a%20complex%20process%20to%20manage%20where%20you%20can%20end%20up%20with%20multiple%20production%20environments%20each%20with%20potentially%20hundreds%20of%20end%20users%20running%20queries%20at%20different%20times.%20There%20are%20also%20scenarios%20where%20adhoc%20end%20users%20can%20submit%20poorly%20written%20and%20runaway%20queries%20which%20consume%20unnecessary%20resources.%20Having%20comprehensive%20workload%20management%20capabilities%20is%20critical%20to%20achieving%20consistent%20performance%20and%20reducing%20time%20to%20insight%20to%20meet%20your%20business%20objectives.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20the%20general%20availability%20of%20workload%20isolation%2C%20you%20can%20use%20familiar%20T-SQL%20syntax%20to%20quickly%20ensure%20resources%20are%20appropriately%20allocated%20and%20managed%20for%20your%20most%20demanding%20workloads.%20Workload%20isolation%20can%20all%20be%20done%20within%20a%20single%20pool%20where%20you%20no%20longer%20need%20to%20manage%20multiple%20endpoints.%20You%20can%20also%20configure%20query%20timeouts%20to%20cancel%20any%20runaway%20queries%20without%20having%20to%20build%20alerting%20infrastructure%20or%20manually%20connect%20to%20your%20database%20to%20cancel%20these%20queries.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20simple%20example%20below%20demonstrates%20how%20to%20configure%20a%20single%20workload%20group%20where%20100%25%20of%20resources%20from%20the%20SQL%20pool%20will%20be%20allocated%20to%20a%20single%20load.%20This%20is%20an%20extreme%20example%20of%20workload%20isolation%20which%20can%20be%20used%20when%20you%20need%20to%20initially%20onboard%20and%20ingest%20a%20dataset%20as%20quickly%20as%20possible%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-sql%22%3E%3CCODE%3ECREATE%20WORKLOAD%20GROUP%20adhocdataload%0AWITH%20(%20%0A%20%20%20%20%20%20%20%20MIN_PERCENTAGE_RESOURCE%20%3D%20100%0A%20%20%20%20%20%20%2C%20CAP_PERCENTAGE_RESOURCE%20%3D%20100%0A%20%20%20%20%20%20%2C%20REQUEST_MIN_RESOURCE_GRANT_PERCENT%20%3D%20100%0A%20%20%20%20%20%20%2C%20QUERY_EXECUTION_TIMEOUT_SEC%20%3D%20900%20--Load%20cannot%20be%20longer%20than%2015%20minutes%0A)%3B%0A%0ACREATE%20WORKLOAD%20CLASSIFIER%20%5Badhocloader%5D%0AWITH%20(%0A%20%20%20%20%20%20%20%20WORKLOAD_GROUP%20%3D%20'adhocdataload'%0A%20%20%20%20%20%20%2C%20WLM_LABEL%20%3D%20'COPYStatement'%0A%20%20%20%20%20%20%2C%20MEMBERNAME%20%3D%20'myloaduser'%0A)%3B%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERequests%20coming%20from%20the%20%E2%80%98myloaduser%E2%80%99%20user%20will%20automatically%20be%20classified%20to%20the%20%E2%80%98adhocdataload%E2%80%99%20workload%20group%20which%20will%20be%20given%20100%25%20of%20the%20SQL%20pool%20resources.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20more%20information%20on%20workload%20isolation%2C%20see%20the%20following%20documentation%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fsql%2Ft-sql%2Fstatements%2Fcreate-workload-group-transact-sql%3Fview%3Dazure-sqldw-latest%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3ET-SQL%20syntax%20for%20workload%20groups%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsql-data-warehouse%2Fquickstart-configure-workload-isolation-tsql%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EQuickstart%3A%20Configure%20workload%20isolation%20using%20T-SQL%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1513355%22%20slang%3D%22en-US%22%3E%3CP%3EWorkload%20isolation%20is%20now%20generally%20available!%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Workload%20Isolation.png%22%20style%3D%22width%3A%20727px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F204509iC36490C0259A1A6E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Workload%20Isolation.png%22%20alt%3D%22Workload%20Isolation.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1513355%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESynapse%20SQL%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Workload isolation in Azure Synapse Analytics is now generally available where you can use workload groups to reserve, contain, and manage resources across different workloads running on your SQL pool. Previously users had to provision, secure, and manage multiple pools with different endpoints orchestrating additional ETL processes to achieve workload isolation and avoid resource contention. This can become an expensive and a complex process to manage where you can end up with multiple production environments each with potentially hundreds of end users running queries at different times. There are also scenarios where adhoc end users can submit poorly written and runaway queries which consume unnecessary resources. Having comprehensive workload management capabilities is critical to achieving consistent performance and reducing time to insight to meet your business objectives.

 

With the general availability of workload isolation, you can use familiar T-SQL syntax to quickly ensure resources are appropriately allocated and managed for your most demanding workloads. Workload isolation can all be done within a single pool where you no longer need to manage multiple endpoints. You can also configure query timeouts to cancel any runaway queries without having to build alerting infrastructure or manually connect to your database to cancel these queries.

 

The simple example below demonstrates how to configure a single workload group where 100% of resources from the SQL pool will be allocated to a single load. This is an extreme example of workload isolation which can be used when you need to initially onboard and ingest a dataset as quickly as possible:

 

CREATE WORKLOAD GROUP adhocdataload
WITH ( 
        MIN_PERCENTAGE_RESOURCE = 100
      , CAP_PERCENTAGE_RESOURCE = 100
      , REQUEST_MIN_RESOURCE_GRANT_PERCENT = 100
      , QUERY_EXECUTION_TIMEOUT_SEC = 900 --Load cannot be longer than 15 minutes
);

CREATE WORKLOAD CLASSIFIER [adhocloader]
WITH (
        WORKLOAD_GROUP = 'adhocdataload'
      , WLM_LABEL = 'COPYStatement'
      , MEMBERNAME = 'myloaduser'
);

 

Requests coming from the ‘myloaduser’ user will automatically be classified to the ‘adhocdataload’ workload group which will be given 100% of the SQL pool resources.

 

For more information on workload isolation, see the following documentation: