You may not have used the advantages of these details when optimizing your database. The following are 10 questions about your database performance. Ask yourself.
1. assume that your database does not need the ability to store special characters, especially those characters specified in the Unicode standard, have you replaced the nchar type with various applicable field types such as char in the system?
2. Are you using the smalldatetime type instead of datetime? If you do not know the differences between the two types, this is a simple introduction: The smalldatetime type can store dates from January 1, to January 1, and the datetime type extends this range to January 1. Do you need such a large scope?
3. Do you routinely use the bit type instead of the smallint type? If so, do you know the price? This is for youProgramIt may not be affected, but the smallint type can be used to create an index, but the bit type cannot.
4. SQL Server 2000 allows null values in BIT fields, which is the default value. Some people want this, and some do not.
5. How do you deal with null values in fields? The default method is to allow null values, but a better way is to disable null values and allow zero-length strings.
6. Have you thought about the maximum number of rows in a table? Have you compared the value with the size of the data page in 8060 bytes?
7. Do you make good use of standard fields? (Go to the tool> Options> standard fields in the menu)
8. Is there a timestamp field in your table? If not, do you know when this field will be useful?
9. Do your tables have block indexes? Do you know when a table should have block indexes and when it is worthless?
10. Do you use the SP _ prefix when naming stored procedures? Do you realize the impact of this on performance?