Exam DP-300: Administering Microsoft Azure SQL Solutions

Comments

Post a Comment

Popular posts from this blog

DP-300 dumps

Image
 Question #1 Topic 1 You have 20 Azure SQL databases provisioned by using the vCore purchasing model. You plan to create an Azure SQL Database elastic pool and add the 20 databases. Which three metrics should you use to size the elastic pool to meet the demands of your workload? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point. A. total size of all the databases B. geo-replication support C. number of concurrently peaking databases * peak CPU utilization per database D. maximum number of concurrent sessions for all the databases E. total number of databases * average CPU utilization per database Correct Answer: ACE  CE: Estimate the vCores needed for the pool as follows: For vCore-based purchasing model: MAX(<Total number of DBs X average vCore utilization per DB>, <Number of concurrently peaking DBs X Peak vCore utilization per DB) A: Estimate the storage space needed for the pool by adding the number of bytes needed for ...
Read more

Deterministic and Non -deterministics

  Deterministic and Non-deterministic Two approximate algorithms are offered for the approximate percentile functions: Non-deterministic: fastest method, whenever reproducibility is not required. This is the default method. Deterministic: slightly slower, but delivers deterministic results. Note that the differences will not be apparent with the small dataset in use here. REM Approximate median, NON DETERMINISTIC select approx_median(volume), approx_median(volume, 'ERROR_RATE' ) from approxt where state = 'CA' ; REM Approximate median, DETERMINISTIC select approx_median(volume deterministic), approx_median(volume deterministic, 'ERROR_RATE' ) from approxt where state = 'CA' ; REM Approximate percentile, DETERMINISTIC select approx_percentile( 0.1 deterministic) within group ( order by volume) from approxt where state = 'CA' ;
Read more

Cast Conversion

  Overview Doesn’t matter who much testing you do (well, it actually does but that’s a whole different issue!) you can guarantee that at some point your beautiful code that parses data input from a web form or loads data from some external file will pop up with the error: SQL Error: ORA-01722: invalid number 01722. 00000 - "invalid number" *Cause: The specified number was invalid. *Action: Specify a valid number. Of course, what’s is really annoying at this point is that you don’t know which column value of the record failed (assuming that you have more than one numeric column) Module 2 Setting up a staging table For this tutorial let’s build some simple staging and target tables in our schema: CREATE TABLE STAGING_EMP ( "EMPNO" VARCHAR2( 6 ), "ENAME" VARCHAR2( 10 ), "JOB" VARCHAR2( 9 ), "MGR" VARCHAR2( 4 ), "HIREDATE" VARCHAR2( 10 ), "SAL" VARCHAR2( 7 ), "COMM" VARCHAR2( 9 ), ...
Read more