SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Files with larger disk consumption


Files with larger disk consumption

Author
Message
Junior Galvão - MVP
Junior Galvão - MVP
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6042 Visits: 252
Comments posted to this topic are about the item Files with larger disk consumption
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)

Group: General Forum Members
Points: 912435 Visits: 48738
So.... how do you find out what's causing the problem?

--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.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

When you put the right degree of spin on it, the number 318 is also a glyph that describes the nature of a DBAs job. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Junior Galvão - MVP
Junior Galvão - MVP
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6042 Visits: 252
Jeff Moden - Thursday, January 10, 2019 9:11 AM
So.... how do you find out what's causing the problem?

Hi Jeff,
Did you refer to slowness issues in reading the data?

Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)

Group: General Forum Members
Points: 912435 Visits: 48738
Junior Galvão - MVP - Thursday, January 10, 2019 3:43 PM
Jeff Moden - Thursday, January 10, 2019 9:11 AM
So.... how do you find out what's causing the problem?

Hi Jeff,
Did you refer to slowness issues in reading the data?


No. I'm talking about finding high values in the things you measured. How do you find what is causing those high values? The article doesn't really provide a clue as to how to determine if it's code, hardware, or simply a temporary "data storm". I realize that you're "just" providing a script but it seems to me that at least mentioning that it could be one of those 3 would make the script article more valuable because being able to identify a problem doesn't really help if you don't know what the actual problem really is.

--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.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

When you put the right degree of spin on it, the number 318 is also a glyph that describes the nature of a DBAs job. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Junior Galvão - MVP
Junior Galvão - MVP
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6042 Visits: 252
Jeff Moden - Thursday, January 10, 2019 10:21 PM
Junior Galvão - MVP - Thursday, January 10, 2019 3:43 PM
Jeff Moden - Thursday, January 10, 2019 9:11 AM
So.... how do you find out what's causing the problem?

Hi Jeff,
Did you refer to slowness issues in reading the data?


No. I'm talking about finding high values in the things you measured. How do you find what is causing those high values? The article doesn't really provide a clue as to how to determine if it's code, hardware, or simply a temporary "data storm". I realize that you're "just" providing a script but it seems to me that at least mentioning that it could be one of those 3 would make the script article more valuable because being able to identify a problem doesn't really help if you don't know what the actual problem really is.


Jeff,
I really shared the script, which I'm always using in my consulting activities here in Brazil, at no time I thought of writing an article that can illustrate or guide how we can reach this values, maybe do it, even if you want to access my humble blog: pedrogalvaojunior.wordpress.com, may have a dimension of what I do and a little of what I aim to do.
There are several possibilities that can cause the presentation of these values, this will depend very much on what is being executed or even processed by the instance, server or hardware that we are analyzing.
When this script is run in an environment is the values ​​presented are close to what I highlighted, we then have to start analyzing their possible causes, by default when faced with a supposedly slow reading process, the main causes can be:
- Hard Disk presenting performance problems in the search of data;
- Fragmentation of data in our tables and indexes;
- Lack of indexes in our tables;
- Use of columns in the where clause that do not satisfy the condition to obtain the data in a better time; and
- As well as the query being executed may be one of the causes.
At this point, you see these items as possible causes of slow reading of data that is on disk.
But reinforcing again that this script is meant to alert the values ​​that are being presented at the time of its execution, the causes or reasons will vary from scenario to scenario.

Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)SSC Guru (912K reputation)

Group: General Forum Members
Points: 912435 Visits: 48738
Junior Galvão - MVP - Friday, January 11, 2019 6:49 AM
Jeff Moden - Thursday, January 10, 2019 10:21 PM
Junior Galvão - MVP - Thursday, January 10, 2019 3:43 PM
Jeff Moden - Thursday, January 10, 2019 9:11 AM
So.... how do you find out what's causing the problem?

Hi Jeff,
Did you refer to slowness issues in reading the data?


No. I'm talking about finding high values in the things you measured. How do you find what is causing those high values? The article doesn't really provide a clue as to how to determine if it's code, hardware, or simply a temporary "data storm". I realize that you're "just" providing a script but it seems to me that at least mentioning that it could be one of those 3 would make the script article more valuable because being able to identify a problem doesn't really help if you don't know what the actual problem really is.


Jeff,
I really shared the script, which I'm always using in my consulting activities here in Brazil, at no time I thought of writing an article that can illustrate or guide how we can reach this values, maybe do it, even if you want to access my humble blog: pedrogalvaojunior.wordpress.com, may have a dimension of what I do and a little of what I aim to do.
There are several possibilities that can cause the presentation of these values, this will depend very much on what is being executed or even processed by the instance, server or hardware that we are analyzing.
When this script is run in an environment is the values ​​presented are close to what I highlighted, we then have to start analyzing their possible causes, by default when faced with a supposedly slow reading process, the main causes can be:
- Hard Disk presenting performance problems in the search of data;
- Fragmentation of data in our tables and indexes;
- Lack of indexes in our tables;
- Use of columns in the where clause that do not satisfy the condition to obtain the data in a better time; and
- As well as the query being executed may be one of the causes.
At this point, you see these items as possible causes of slow reading of data that is on disk.
But reinforcing again that this script is meant to alert the values ​​that are being presented at the time of its execution, the causes or reasons will vary from scenario to scenario.


I get and very much appreciate all of that, Junior. If you would have stated the very things in the preamble of your script as possibly "Here are the things that can go wrong with your system...." followed by the rest of what you wrote as a first measure to see if you even have a problem (which you did very well!), people would see the value in your script even more.

It's meant as a suggestion because there are too many people that write scripts out there without emphasizing why the script is valuable.

--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.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

When you put the right degree of spin on it, the number 318 is also a glyph that describes the nature of a DBAs job. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Junior Galvão - MVP
Junior Galvão - MVP
SSCertifiable
SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)SSCertifiable (6K reputation)

Group: General Forum Members
Points: 6042 Visits: 252
Jeff Moden - Friday, January 11, 2019 8:00 AM
Junior Galvão - MVP - Friday, January 11, 2019 6:49 AM
Jeff Moden - Thursday, January 10, 2019 10:21 PM
Junior Galvão - MVP - Thursday, January 10, 2019 3:43 PM
Jeff Moden - Thursday, January 10, 2019 9:11 AM
So.... how do you find out what's causing the problem?

Hi Jeff,
Did you refer to slowness issues in reading the data?


No. I'm talking about finding high values in the things you measured. How do you find what is causing those high values? The article doesn't really provide a clue as to how to determine if it's code, hardware, or simply a temporary "data storm". I realize that you're "just" providing a script but it seems to me that at least mentioning that it could be one of those 3 would make the script article more valuable because being able to identify a problem doesn't really help if you don't know what the actual problem really is.


Jeff,
I really shared the script, which I'm always using in my consulting activities here in Brazil, at no time I thought of writing an article that can illustrate or guide how we can reach this values, maybe do it, even if you want to access my humble blog: pedrogalvaojunior.wordpress.com, may have a dimension of what I do and a little of what I aim to do.
There are several possibilities that can cause the presentation of these values, this will depend very much on what is being executed or even processed by the instance, server or hardware that we are analyzing.
When this script is run in an environment is the values ​​presented are close to what I highlighted, we then have to start analyzing their possible causes, by default when faced with a supposedly slow reading process, the main causes can be:
- Hard Disk presenting performance problems in the search of data;
- Fragmentation of data in our tables and indexes;
- Lack of indexes in our tables;
- Use of columns in the where clause that do not satisfy the condition to obtain the data in a better time; and
- As well as the query being executed may be one of the causes.
At this point, you see these items as possible causes of slow reading of data that is on disk.
But reinforcing again that this script is meant to alert the values ​​that are being presented at the time of its execution, the causes or reasons will vary from scenario to scenario.


I get and very much appreciate all of that, Junior. If you would have stated the very things in the preamble of your script as possibly "Here are the things that can go wrong with your system...." followed by the rest of what you wrote as a first measure to see if you even have a problem (which you did very well!), people would see the value in your script even more.

It's meant as a suggestion because there are too many people that write scripts out there without emphasizing why the script is valuable.

Jeff, thanks for understanding, within the possible I will seek to share my experiences and knowledge.

robert.sterbal 56890
robert.sterbal 56890
SSCrazy Eights
SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)SSCrazy Eights (9.7K reputation)

Group: General Forum Members
Points: 9650 Visits: 1729
Having read through this quickly I thought it was valuable. Performance tools are always welcome!

I wondered if the title

Files with larger disk consumption

would be better as

Files with slower disk consumption


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search