I have a table created on default [DATA] filegroup (SQL Server 2008 R2)
If I script the table out using SSMS 2008 R2, it is scripted like this:
CREATE TABLE [IN].[Message](
[MessageID] [int] NOT NULL,
[MessageReference] [varchar](100) NOT NULL,
PRIMARY KEY CLUSTERED
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [DATA]
) ON [DATA]
When I import the database into VS 2012 with June SSDT, it is imported like this:
CREATE TABLE [IN].[Message] (
[MessageID] INT NOT NULL IDENTITY(1, 1) PRIMARY KEY CLUSTERED, [MessageReference] VARCHAR (100) NOT NULL,
Note that filegroup placement has not been imported. If a target database has PRIMARY as its default, the object will be create on the wrong filegroup.
Also, for some reason, SSDT is treating table filegroup setting as an error if clustered index also has it. This setting is ignored, so it should maybe be a warning, not an error. More importantly, as SSMS scripting produces create table scripts with filegroup specified for both table and index, these scripts will be flagged as error by VS.