Solution to error in automatic database Growth Value Setting

Today, some netizens asked about the database at the 51cto technical forum-the auto-growth value is 12800%. They asked for help and saw this wonderful name. So I decided to go in and see if I could do my best. I did not expect this.

Today, some netizens asked about the database at the 51cto technical forum-the auto-growth value is 12800%. They asked for help and saw this wonderful name. So I decided to go in and see if I could do my best. I did not expect this.

Today, some web hosting users asked about the database at the 51cto technical forum-the auto-growth value was 12800%. for help, I saw this wonderful name and rented the Hong Kong server. So I decided to go in and see it, to see if I can do my best.

After reading this, I did not expect it to help me. Although this is not a part of my management, it can also help me one or two.

Why can I solve this problem? Because I once met. SQL SERVER sometimes has some inexplicable problems, such as this friend mentioned. At first glance, the growth volume is 12800%. Are you scared?

In this case, it is very common for us to click the edit button to modify the server in Hong Kong. Then, if the server can be modified smoothly, so I think this blog post is unnecessary. Obviously, it will give you the following points during the modification:

My friends and I are stunned. Isn't it difficult? Since it should be between the minimum and maximum values, how can this happen? Complaints are all complaints, and the problem must be solved by yourself.

Looking for a solution... 10 thousand words are omitted here.

Suddenly a flash, T-SQL statements are forgotten? It seems that I am so worried that I am used to convenient GUI operations and almost forgot the commands. Fortunately, I finally remembered it when I spent 0.2 billion of my brain cells.

USE [master] [DbName] MODIFYFILE (NAME = n' filelogicalname', FILEGROWTH = 100%) GO

DbName is the name of the database to be modified.

FileLogicalName is the logical name of the data file or log file, not the disk file name. (Pay attention to this .)

FILEGROWTH is automatic Growth

After running it, I learned a word, tigger, and So Easy!

Tips. Thanks to this friend for the error:

FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005