General question on tuning

Question

General question on tuning

vsamantha35

SSChampion

Points: 11529
More actions
December 1, 2017 at 1:34 pm

#333878

Hi All
Need some suggestions and clarity. Its a general basic question on Query tuning.
Is there any difference(s) when it comes to query tuning of a Azure database and OnPremise database?
In one of our env, they are looking for someone who can do azure db migration and query tuning? So, checking out for differences while performance tuning a azure db queries
when compared to a Onpremise database queries.
Thanks,
Sam

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Steve Jones - SSC Editor SSC Guru Points: 734418 More actions · Answer 1

You have a little more insight into hardware on premises, but the principles are really the same. Good design, good code, index well.

Grant Fritchey SSC Guru Points: 398679 More actions · Answer 2

It's largely the same. Good code, good structure, proper indexes, statistics up to date, these are what you have to do. The difference is, as you tune the queries, you can almost literally show how you're saving money. The faster everything runs, the lower the service tier you need and the lower the cost to the business.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

sqlgrease SSC Journeyman Points: 84 More actions · Answer 3

I tune for response time first and resource usage second for on premise. In azure I tune to reduce DTU usage (i.e. resource usage) first and response time second (so long as it is with reason).

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 4

sqlgrease - Friday, December 15, 2017 9:59 AM
I tune for response time first and resource usage second for on premise.

Although there are certainly exceptions, I've found that the two are usually fairly well joined at the hip.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

sqlgrease SSC Journeyman Points: 84 More actions · Answer 5

Jeff Moden - Friday, December 15, 2017 10:03 AM
sqlgrease - Friday, December 15, 2017 9:59 AM
I tune for response time first and resource usage second for on premise.
Although there are certainly exceptions, I've found that the two are usually fairly well joined at the hip.

Parallel vs non parallel plans is usually where I run into that exception. But yeah, they usually are one and the same.