Search

Default datafile settings not applied by rklimes

Closed
as By Design Help for as By Design

3
0
Sign in
to vote
Type: Bug
ID: 778069
Opened: 1/31/2013 10:34:38 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
The model database settings for Autogrowth/Maxsize for mdf and Initial Size and Autogrowth/Maxsize for LDF do not get applied to new databases if T-sql is used and you do not specify an initial size or autogrowth.
Details (expand)

Product Language

English

Version

SQL Server 2012 SP1

Category

SQL Engine

Operating System

Windows Server 2008 R2 (all editions)

Operating System Language

US English

Steps to Reproduce

change the initial file size and auto growth settings on both files in the model database.
create database using t-sql without specifying size of growth.
ie create database test;

Actual Results

auto growth for both files and initial size for ldf on the new database are the delivered defaults for model data files

Expected Results

expected the file setting to be the same as the changed model file settings

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 4/25/2013 at 12:48 PM
Hello,
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing this bug as a viable workaround is available.
Thanks again for reporting the product issue and continued support in improving our product.

Thanks,
Ajay
Senior Program Manager
Microsoft Corporation
Posted by Pieter Vanhove on 3/20/2013 at 3:32 AM
According to BOL
The following example creates the database mytest and creates a corresponding primary and transaction log file. Because the statement has no <filespec> items, the primary database file is the size of the model database primary file. The transaction log is set to the larger of these values: 512KB or 25% the size of the primary data file. Because MAXSIZE is not specified, the files can grow to fill all available disk space.
Would be nice to also use the default autogrowth setting.
When you create a database with the GUI of the SQL Server Management Studio, then it's using the default settings of the model DB. When you script it, it's actually using the size option in the T-SQL script.
Sign in to post a workaround.