1

Topic: Layout of basis and file broad gull on disks

All greetings!
The server 1 on MSSQL which basis it is planned to allocate on SSD a disk is planned, and for a file broad gull alas places do not suffice. The question, productivity 1 interests and basis operations will be strong cause a stir if a broad gull a file, to allocate on normal HDD? Whether file SQL the broad gull needs a productive disk generally?

2

Re: Layout of basis and file broad gull on disks

Depends on kind of work with basis.  generally I hardly represent that 1 against the stop loaded MS SQL, unless whose that curve hands

3

Re: Layout of basis and file broad gull on disks

Seed88 wrote:

the question, productivity 1 Interests and basis operations will be strong cause a stir if a broad gull a file, to allocate on normal HDD? Whether file SQL the broad gull needs a productive disk generally?

Yes, productivity is defined by a broad gull-file so at shortage of a place it is better to arrive on the contrary, the data on HDD, a broad gull on SSD. But it is better to buy still a disk :-)

bga83 wrote:

  generally I hardly represent that 1 against the stop loaded MS SQL unless whose that curve hands

Is necessary, heard about high loadings and expensive servers almost only in a context 1

4

Re: Layout of basis and file broad gull on disks

And as to the system, Windows with installed MSSQL, they need a productive disk in an operating time with basis, or a productive disk preferably for bases?

5

Re: Layout of basis and file broad gull on disks

Seed88 wrote:

Windows with installed MSSQL, they need a productive disk in an operating time with
Basis, or a productive disk preferably for bases?

It for certain will be in the nobility in the section specializing on MS SQL. Moreover, I am assured,
That there already is 100500 that devoted to productivity of disks.

6

Re: Layout of basis and file broad gull on disks

Seed88 wrote:

And as to the system, Windows with installed MSSQL, they need a productive disk in an operating time with basis

Are not present, on a system disk loading should be zero.

7

Re: Layout of basis and file broad gull on disks

alexeyvg;
That is, if I correctly understood, for system it is possible normal SATA

8

Re: Layout of basis and file broad gull on disks

Seed88 wrote:

alexeyvg;
That is, if I correctly understood, for system it is possible normal SATA

Yes.

9

Re: Layout of basis and file broad gull on disks

If storage does not suffice you rest against a disk so make a fresh start from storage

10

Re: Layout of basis and file broad gull on disks

alexeyvg wrote:

... Productivity is defined by a broad gull-file...

The sir, you are assured of it?
All strongly depends on a loading profile on a specific database. A checkout word . It is not necessary to be such haughty and categorical... It is necessary to be easier also people to you will be pulled. wink

11

Re: Layout of basis and file broad gull on disks

BOBKA.UA wrote:

the Checkout word .

What relation Cooking the House has to 1?

12

Re: Layout of basis and file broad gull on disks

Dimitry Sibiryakov;
All 1 is a bit different... At someone there 10 000  in a minute and 3  and at someone there 10 000  on 3 . So it is necessary to look at a loading profile at first. Suddenly there same as at forgive My God as at , then oh.
On good all certainly is necessary on .

13

Re: Layout of basis and file broad gull on disks

BOBKA.UA wrote:

it is passed...
The sir, you are assured of it?
All strongly depends on a loading profile on a specific database. A checkout word . It is not necessary to be such haughty and categorical... It is necessary to be easier also people to you will be pulled. wink

It for the decision 1 a checkout word ?
OLTP.
Certainly, configurations happen different, but what 1S to  to come, it absolutely a perversion.
And it is clear that for absolutely  it is necessary for a configuration at least 2 SSD, for the data and a broad gull but if SSD there will be all the same one needs to be left it for a broad gull.

14

Re: Layout of basis and file broad gull on disks

alexeyvg wrote:

if SSD there will be all the same one it is necessary to leave it for a broad gull.

How much I remember, at MS SQL to a broad gull there is a serial record and never reading. Zero
Positioning time thus does not offer any advantage in difference from a principal file
DB at which main loading it  reading. And speed of serial record at
SSD it is normal more low, than at HDD.

15

Re: Layout of basis and file broad gull on disks

Dimitry Sibiryakov wrote:

it is passed...
How much I remember, at MS SQL to a broad gull there is a serial record and never reading. Zero
Positioning time thus does not offer any advantage in difference from a principal file
DB at which main loading it  reading. And speed of serial record at
SSD it is normal more low, than at HDD.

quite right. To a broad gull  speed not so is important, as to the data.
But performance of a command data modifications (transaction) is completed, when broad gull file recording is completed.
Therefore speed of a sequel for the client is defined by a broad gull, considering that the data normally effectively . If there not  loading type as above noted BOBKA.UA, that is not a read and write of the big arrays.
Certainly, if from a disk it is necessary to read much speed of operation with the data file too becomes important. But at the HARDWARE basis only 65 ; I hope, their PC used as the server, has at least 16  frames, and hit in a cache the high?

16

Re: Layout of basis and file broad gull on disks

Under a broad gull it is better to take 2 disks 10\15 (15 better) to unite in a mirror (but not to do 5\6- arrays if many disks are), and basis and _ already on SSD, under system the couple normal SATA suffices.

17

Re: Layout of basis and file broad gull on disks

Seed88 wrote:

which basis it is planned to allocate on SSD a disk

basis Layout on single disks it is fraught with the full loss of the information.  have bad property to die instantly and irrevocably. Storage commercially valuable  should imply redundancy on disks. Time redundancy, means spot-check the controler, and is  it should be able to cache including record and record caching strongly levels  drives on record: though , though .
Extremely it is recommended to add in the circuit  the controler with battery (or , depending on the controler version) the unit.

18

Re: Layout of basis and file broad gull on disks

In the general, caching of record without a battery - here is possibility to lose basis more abruptly any died disk. Since any failure of a supply and basis it was covered with a copper basin.
Generally, the battery is not recommended, and it is required in all docks on DBMS adjustment at a switched on cache on record.
IMHO

19

Re: Layout of basis and file broad gull on disks

Leonid Kudryavtsev;
What else battery if it is a question of two disks?
At the HARDWARE normal office machine with the system which reliability of operation is not important (starting with some iron)

20

Re: Layout of basis and file broad gull on disks

As a variant to take two SSD with built in  which includes a cache on record, but I in arrays did not use them, I do not know, how they are synchronized.
From budgetary - to take hybrid HDD, all will be faster, than normal.