Тэги:
#SQL #SQL_Server #SQLAuthority #pinaldave #Sixty_SecondsКомментарии:
Thanks for this. This has to be one of the most contentious issues - telling the infrastructure team that a disk is slow... "no, no, no, we just put in a new <<some brand name>> super duper drive on our VM host. It must be your code that it is slow" :P
Thanks for sending out videos like these, they are both entertaining and educational !!
Sir one more help I am unable to shrink a DB log file , fyi sir that db has partitioning file groups one MDF three ndf and a log file. Log file size is 1.5 tb.
Now I am taking transaction log backup then backup size is 50 to 100 mb which is equal to available free space size. And after log backup in shrink file option still the current size is 1.5 tb and available free space size is 50 to 100 mb. So unable to shrink log. But daily 5 to 6 gb log is increasing. My log drive size 50 gb is remaining only .
Now what should I do sir ?
Kindly suggest.
Thanking you sir
Hi Sir, it is related to both data files and deletion. I am deleting data from huge db on daily basis, but I can see space is not cleared from data files after deletion. I am rebuilding indexes to reclaim deleted data space in data files. Please share if there are any other ways to claim deleted data's space. Thank you.
Ответитьthank you very much pinal! one of the best world wide :-)
ОтветитьSir , my query is not belonging of this topic , but I have.
If I shrink MDF file as available space is almost 95% , will log size be increased?
I am not getting proper solution in Google, please help.
Thank you for the video. Around what number is generally considered as a high number for io_stall_read and io_stall_write?
Ответитьhello sir please make a video on soql performance & index
Ответитьwhat values do you consider high?
ОтветитьGood video and useful.. please provide the link also for those scripts.. it will help us..
ОтветитьThanks very much for this gem! Is io_stall something you'd want to monitor? Not necessarily for alerting when over a threshold; I'm mostly thinking of data collection as a performance counter. This can be done for troubleshooting purposes, to see if latency was the cause of an issue, or to compare a before and after an application update.
ОтветитьI should send my database admins to you for a course :-)
ОтветитьThank you for this video
ОтветитьYeah I have combined this with the indexes status reads to determine how to approach a slow performance on a high traffic system. Great video
Ответить