Editing SQL Server Best Practices
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 2: | Line 2: | ||
* Put the SQL database on a separate drive, not the C drive | * Put the SQL database on a separate drive, not the C drive | ||
− | ** By default, SQL places the database in program files on C, but this is not a good location. C drive is already busy handling the operating system, so best to | + | ** By default, SQL places the database in program files on C, but this is not a good location. C drive is already busy handling the operating system, so best to but on a separate drive. |
* Put SQL database on a separate physical drive | * Put SQL database on a separate physical drive | ||
− | ** This will provide best performance by not | + | ** This will provide best performance by not competeing with the main OS drive running the SQL server program |
* Always provide maximum RAM memory that you can provide | * Always provide maximum RAM memory that you can provide | ||
** Ram memory tends to be inexpensive and always best to have plenty of memory for SQL | ** Ram memory tends to be inexpensive and always best to have plenty of memory for SQL |