Browse categories
I will resolve sql server 2016 post migration slowness
Pro
Expert in:
Databases
About this Gig
Pro
Microsoft has changed a lot in SQL Server 2016 and above. New cardinality estimation can make your old queries' performance worst. New default settings can also behave abnormally for your workload. You were thinking the new SQL Server 2016 will improve your database performance but it's worst than before. No worries I will help you to resolve all these issues. I am a Microsoft MVP award winner solid Database Administrator and know What's New in SQL Server 2016 and above.
There are all sorts of smart cookies who could potentially help you with this project. So why work with me? Here are several reasons that I trust you will find compelling:
- 13 years of in-hand experience
- Recognized by Microsoft by awarding Most Valuable Professional award in 2014-2015
- Handled up to 35TB SQL Server Database
- Handled up to 200 million batch request in 10 production hours
- Well aware of SQL Server internals and its marketing buzz words and shortcomings.
***I never assess an hourly or daily fee, since you should not have to make an investment decision every time my assistance may be needed. Please note that these are fixed prices, not estimates. You will not pay a dime more than the selected price***
Platform:
SQL Server
Other Databases Services I Offer
FAQ
Please describe your experience with MS SQL Server environments:
I am an SQL Server DBA with 13+ years of in-hand experience. Worked with SQL Server 2000 to 2019. The biggest database (in size) of my life was 4TB and the largest transaction load I had handled was 200 million transactions in 10 working hours.
Please describe you prior experience with Production / On-call support?
A DBA can only work better if he works proactively. Besides this, most of the client calls are regarding performance issues. TempDB, missing indexes, out-dated statistics, improper hardware, table design, and query structure are the main issues. Recent: Performance degradation after moving to 2016+.
Availability for Production / On-call rotations according to EST ?
7:00AM to 12PM EST is the perfect time for me.
How fix will be provided ?
If a fix is related to a stored procedure or script, it is highly recommended that it should not be deployed directly on the production server. Proper QA is a must for these kinds of changes. Configuration issue fixes are made directly on servers.
