1

Topic: What demands a DB file?

Good afternoon.
Prompt that is necessary for  the big file? (1 Tb).
Whether something will be generated in a broad gull?
It is required for an occasional seat on a disk for ?
What can be demanded  ?
About that that Bd will work I know more slowly, so this question can to be affected in a subject.

2

Re: What demands a DB file?

1. "Resources" - with one

3

Re: What demands a DB file?

Hupin wrote:

1. "Resources" - with one

It  - here and two with.
.  for  it is not necessary.

4

Re: What demands a DB file?

All relocation at  are written to a broad gull
For  resources of the processor and disk operations are used
If on tables in a file there are indexes in certain cases it entails their reorganization
If after  you do a defragmentation on it as resources be required

5

Re: What demands a DB file?

wrote:

if on tables in a file there are indexes in certain cases it entails their reorganization

I.e.  also indexes ?

6

Re: What demands a DB file?

o-o wrote:

it is passed...
I.e.  also indexes ?

Fragments

7

Re: What demands a DB file?

aleks222 wrote:

.  for  it is not necessary.

So can, with it and at all to replace regular ?
For last the place as though is necessary.
And here what a difference .  (a C the Grandfather), wants nothing (a C aleks222), resources does not guzzle, continuous profit

8

Re: What demands a DB file?

o-o;
The grandfather is somewhat right, here or  to preferable) or after it is necessary. Resources it CPU and time

9

Re: What demands a DB file?

TaPaK wrote:

fragments

I.e. reorganization <> rebuild
Reorganization = a fragmentation?
----
All.  [img=http://www.en.kolobok.us/smiles/light_skin/bye.gif]

10

Re: What demands a DB file?

o-o wrote:

it is passed...
I.e. reorganization <> rebuild
Reorganization = a fragmentation?
----
All.  [img=http://www.en.kolobok.us/smiles/light_skin/bye.gif]

SHRINK fragments indexes, what here it is not clear, where  there comparing?

11

Re: What demands a DB file?

TaPaK wrote:

o-o;
The grandfather is somewhat right, here or  to preferable) or after it is necessary. Resources it CPU and time

If you badly understand sense of a phrase in Russian, I will explain:
"Passage from a heap to the cluster attracts evolution "
Means: not I want/not I want I will rebuild or not ;
And that they will be rebuilt in a creation consequence on a heap of clustered index.
And here if at someone  attracts reorganization of indexes, mine to it sympathy

12

Re: What demands a DB file?

o-o wrote:

it is passed...
If you badly understand sense of a phrase in Russian, I will explain:
"Passage from a heap to the cluster attracts evolution "
Means: not I want/not I want I will rebuild or not ;
And that they will be rebuilt in a creation consequence on a heap of clustered index.
And here if at someone  attracts reorganization of indexes, mine to it sympathy

What it for a dial-up  from different subjects? If the ram, does not master consequence SHRINKA for extents it is its problem

13

Re: What demands a DB file?

wrote:

SQL Server DBCC SHRINKFILE Demonstration
DBCC SHRINKFILE with TRUNCATEONLY to a target size which does not cause index fragmentation
DBCC SHRINKFILE with TRUNCATEONLY to the last allocated extent which does not cause index fragmentation
DBCC SHRINKFILE which causes fragmentation

14

Re: What demands a DB file?

o-o wrote:

and here if at someone  attracts reorganization of indexes, mine to it sympathy

I will explain...
I specially wrote "in certain cases".
If at you on the table is not present cluster and is not cluster transferring pages operation  including changes addresses at sheet level not cluster
(I had it under evolution).

15

Re: What demands a DB file?

The grandfather;
At it today all is one-sided

wrote:

it entails their reorganization

equally SHRINK does REBUILD, overheated...

16

Re: What demands a DB file?

wrote:

it is passed...
I will explain...
I specially wrote "in certain cases".
If at you on the table is not present cluster and is not cluster transferring pages operation  including changes addresses at sheet level not cluster
(I had it under evolution).

I.e. indexes nevertheless will not be rebuilt?
[spoiler] and not  evolution a broad gull of transactions? [/spoiler]

17

Re: What demands a DB file?

wrote:

I specially wrote "in certain cases".
If at you on the table is not present cluster and is not cluster transferring pages operation  including changes addresses at sheet level not cluster
(I had it under evolution)
.

Here, by the way, thanks.
I had doubts that the Grandfather, yes clumsily expressed... It would be too strange.
So, companion aPaK, put at all in a fragmentation.
The grandfather under evolution meant absolutely other moment...
to name difficult, for it is faster "update" not cluster in connection with heap moving.
But a fragmentation precisely at anything, not about it there was a speech

18

Re: What demands a DB file?

o-o;
And now we consider "for it more likely" update "not cluster in connection with heap moving."? On yours the fragmentation at SHRINK all remaining does not concern???

19

Re: What demands a DB file?

In
https://docs.microsoft.com/en-us/sql/re … a-database

wrote:

Follow Up: After you shrink a database
Data that is moved to shrink a file can be scattered to any available location in the file. This causes index fragmentation and can slow the performance of queries that search a range of the index. To eliminate the fragmentation, consider rebuilding the indexes on the file after shrinking.

20

Re: What demands a DB file?

TaPaK wrote:

o-o;
And now we consider "for it more likely" update "not cluster in connection with heap moving."? On yours the fragmentation at SHRINK all remaining does not concern???

In a pancake, what you were anchored to me with a fragmentation?
Fragmentation a fragmentation,  , expenditure CPU...
Let's continue?
I had a specific question to the Grandfather under its specific message:
"If on tables in a file there are indexes in certain cases it entails their reorganization".
Now that, will enumerate all what concerns to , but does not concern this phrase?
Its this phrase about update of sheet level not cluster,
We clarified it and are happy.
It not "reorganization" for the index structure  changes, the new object does not form, it is a simple update of an index.
Which, for example, happens and at  a clustered index key.
Not cluster thus will not be rebuilt, but will be updated
-----
I suggest to answer a companion its question at last
"What  demands  a DB file?"
Good picture
A SQL Server DBA myth a day: (9/30) data file shrink does not affect performance

21

Re: What demands a DB file?