Browse categories
I will resolve microsoft sql server tempdb issues
Pro
Expert in:
Databases
About this Gig
Pro
TempDB:
One of the most common performance problems that exist in SQL Server instances across the world is known as tempdb contention. Tempdb contention has nothing or very little to do with IO issues. The problem is always somewhere else.
I will also resolve SQL Server TempDB size increase rate. I am a Microsoft MVP award winner solid Database Administrator that uses enterprise-level best practices to anchor high transactional, zero downtime data solutions.
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
- Microsoft awarded Most Valuable Professional award in 2014-2015
- SQL Server version 2008 to 2019
- Handled up to 35TB/Database
- Handled up to 200 million batches/client/day
- 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***
Database type:
Relational database
Platform:
MS SQL
•
SQL Server
Expertise:
Data structure
•
Normalization
•
SQL
•
Performance
Offers hourly rates
Pay by the hour, as reported by the freelancer.
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 35TB 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 issues fixes are made directly on servers.
