sql server - Visual Studio 2013 database project - deployment / publishing - filegroup PRIMARY -
traditionally have created simple databases using sql server management studio, taken backup , restored empty database online. preferred way of hosting server.
i started using visual studio 2013 database project options because prefer environment. used http://sanderstechnology.com/2013/schema-modelling-with-visual-studio-2013-preview/12336/#.vijncnkfo71 guide.
there differences - don't have post deploy scripts option have created databases using publish seems fine. there 1 quirk differs in examples i've looked at. when publish, creates database name chose , appends _primary
. in database properties shows database name above shows filegroup = primary
, i'm assuming why? when view db via vs2013 or sql server management studio, shows db name if want attach db project have attach _primary.mdf
file.
in ignorance assuming _primary
wrapper around database? wondering why vs2013 , if deploying way do, explained above, going cause issues? or doing wrong..
the database project automatically creates filegroup named primary database. becomes default filegroup unless change (see project properties > project settings > database settings > operational tab), typically don't need to.
the database project automatically uses filegroup name in primary data file's name, example mydatabase_primary.mdf
. convention follow in case need have multiple data files (ex: mydatabase_secondary.ndf
, mydatabase_filedata.ndf
, etc).
what vs doing fine. data file names arbitrary anyway. if need more control on how data file named read how name filenames of database , set location in visual studio 2015 database project?
i suggest reading more files , filegroups in files , filegroups architecture.
Comments
Post a Comment