This project has moved and is read-only. For the latest updates, please go here.
1

Closed

Can't create database in SQL Server 2012

description

SQLInstaller 1.2.6 can't create a new database in SQL Server 2012. It tries create a database with the size less than template model database (5 Mb).
Closed Sep 6, 2012 at 3:26 PM by bschloz

comments

bschloz wrote Aug 29, 2012 at 1:02 PM

I have activated this issue and will fix in the next release. In the meantime, you may alter the create script for the SqlServer provider to fix this issue. Go to the SQL Installer install directory (e.g. \Program Files\SQL Installer) and rename ProviderFactory.xml.orig to ProviderFactory.xml. Within this file you will find the Create script for the SQL Server provider. Adjust this script as necessary to fix the issue with SQL Server 2012.

bschloz wrote Aug 29, 2012 at 6:23 PM

After further investigation, I am unable to reproduce this issue with the latest version of SQL Server 2012. The current create script for SQL Server is identical to the default create script as generated by SSMS. Perhaps there is something specific to your installation which is causing the error. In any case, you may follow the advice in my previous post to workaround any problems for your particular installation if that is the case.

wrote Aug 30, 2012 at 12:59 PM

Halega wrote Sep 5, 2012 at 1:01 PM

Connecting to data source...
Creating database VDB...
sqlinstaller : error : The CREATE DATABASE statement failed. The primary file mu
st be at least 5 MB to accommodate a copy of the model database.
Completed with 1 error(s).

Create script for new db has SIZE = 5120KB (that is a model db size) in my installation of SQL Server 2012 Express. SQLInstaller tries to create a db with SIZE = 3072KB.

Fixed that in ProviderFactory.xml.

Thanks for help!

bschloz wrote Sep 5, 2012 at 4:15 PM

Cannot reproduce



** Closed by bschloz 8/30/2012 4:59 AM

bschloz wrote Sep 5, 2012 at 4:15 PM

Removing the SIZE parameter for the primary data file altogether will cause it to use the size of the model db's primary datafile by default. This would be a better default behavior that would accommodate installations that have a larger model primary data file.

wrote Sep 5, 2012 at 4:17 PM

wrote Sep 6, 2012 at 3:26 PM

Resolved with changeset 81394.

wrote Feb 14, 2013 at 3:40 AM

wrote May 16, 2013 at 9:05 AM

wrote Nov 29 at 2:18 AM