Best practices to be followed while creating DataBase

  • HI,

    Anyone would tell the reason, why should we place data file and log file on separate Physical hard Disks?

    And Experts suggest that when choosing hard Drives please give priority to IOPs than Capacity of Hard Disk . IOPs indicates performance. Why had they suggested like this?

  • It's also recommended to use dedicated database servers.

    It depends on the size of your database(s). Planning for data is important to know.

    If your database is small, up to some tens of gigabytes, then you can put data and log on one hard drive. If your HDD is fast then you're extra fine. Today a fast HDD is one with RPM = 10K or 15K, or even faster the SSDs.

    If your database(s) is big, or you have multiple databases to put on an instance so that their size is (let's say) over 100 GB (I'm rounding the numbers), then you'd definitely better go with the Experts' recommendation to put the data on one HDD and the log on another. There you'll probably have more IOPs and having two or more HDDs is making data move faster (you've already paid for that by purchasing the HDDs).

    However, if you create a new database on one HDD, and later you see that the need to spread it on multiple HDDs then it's also possible.

    Igor Micev,My blog: www.igormicev.com

  • Physically separating data and log files is about more than performance - it's about recoverability, too. If you lose the disk that your data and logs are on, you've lost everything and you can only go back to your last backup. If they're on separate drives and you only lose the data drive, you can normally recover to any point up to the loss.

    John

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply