The ModifyCustomerDatabaseFile modifies settings for a specified
database. You can only change one attribute at a time - for
example, file size.
There are T-SQL issues when modifying database attributes with
the ModifyDatabaseFile method.
In SQL Server 2005 Standard Edition with SP2, T-SQL calls that
alter the file growth size to unrealistic numbers, such as growing
the log file of the database by 3TB, will result in a log file
growth of 1MB. This is an inconsistency of the SQL Server since the
SQL Admin Provider is merely passing through the statements to the
server. Also, this is not an API issue, rather it is the result of
the server not processing the "corrupt" value.
Values of file growth size over 1 TB will not generate an error
message, but rather will report a completed transaction and leave
the log file growth at the default of 1MB.
The Lightweight Directory Access Protocol (LDAP) path of the
The name of the database to be modified.
The name of the preferred domain controller.
Size of file in megabytes (MB) (you must specify the unit). If
not specified, the model database size of the primary file is used.
Requires that the dataFile/logicalName node exist and be non-null.
A request to set the fileSize value directly from a small value
to a very high value may timeout. To avoid this problem, use
smaller increments when setting this value. For example, to set
this value to 1GB when it is currently 10MB, use incremental
changes of a few hundred MB.
Designates a growth increment in KB, MB, GB, or percentage (you
must specify the unit. ). The default is 10 percent and the minimum
value is 64 KB. Requires that the dataFile/logicalName node exist
and be non-null. If unit is not specified, then the default MB unit
Maximum size in KB, MB, or GB for the file . The default is
megabyte (MB) and must be a whole number. The default is unlimited.
Requires that the logFile/logicalName node exist and be
New logical name for the file.
Logical name for the file.
The user name for connecting to the SQL server via SQL
Authentication. If this node is present, the connection will be
made via SQL Authentication rather than Windows Authentication. The
existence of this node also requires that the <sqlUserPass/>
The password for connecting to the SQL server via SQL
Authentication, using the username indicated by
<sqlUserName/>. If the <sqlUserName/> node is not
present, this node is ignored.