on primary

Question

on primary

super48

SSCrazy

Points: 2682
More actions
April 1, 2013 at 5:36 am

#275926

why on primary is used while creating a table is it necessary
ex:
create table temp
(name varchar(50),age smallint,salary int)on primary

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

AndrewSQLDBA SSC-Insane Points: 21827 More actions · Answer 1

Because that you can have more than one filegroup. And that tells SQL Server to create the object in a certain file group. Yes, it is required. That is, I have always typed it. You can look in the SQL BOL to be sure.

Andrew SQLDBA

Lowell SSC Guru Points: 323504 More actions · Answer 2

AndrewSQLDBA (4/1/2013)
Because that you can have more than one filegroup. And that tells SQL Server to create the object in a certain file group. Yes, it is required. That is, I have always typed it. You can look in the SQL BOL to be sure.
Andrew SQLDBA

technically it's not required as far as the CREATE TABLE command goes, but if you leave it off, it gets created on the PRIMARY file group anyway, because that is the default group.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

It's not required. Leave it off and the table or index gets created in the default filegroup. That's Primary by default, but can be changed

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Steve JP Ten Centuries Points: 1070 More actions · Answer 4

Get into a habit of leaving the "on primary" off all your code. When the code gets released the DBA can decide if it is appropriate where the objects (tables, indexes) are supposed to be by defining which filegroup is the default. In general its the DBA and not the developer who is responsible for the file & object placement on the system and in an agile environment under pressure you try getting 20 developers environments to accept multiple file groups!

To turn the auto scripting of then is SSMS

Menu->Tools -> options-> Sql Server Object Explorer->Scripting

scroll down to "Table and view options" then find "Script File Groups" and set the option to false.