wise-coders
commented
1 year ago Thank you for writing about this. Here is a quick fix: Please edit in Model / Settings / Database Specific / SQL Syntax/ Table / Options to
ON ~partitionSchemeOrFileGroup~ | TEXTIMAGE_ON ~fileGroup~ | FILESTREAM_ON ~partitionSchemeOrFileGroup~ | WITH ([MEMORY_OPTIMIZED=ON |DURABILITY={SCHEMA_ONLY|SCHEMA_AND_DATA} |SYSTEM_VERSIONING=ON [(HISTORY_TABLE = ~schema.table~ [, DATA_CONSISTENCY_CHECK = {ON|OFF}])] |DATA_COMPRESSION ={NONE|ROW|PAGE} [ON PARTITIONS ({~partitionNumberExpression~|~range~})] |FILETABLE_DIRECTORY=~directoryName~ |FILETABLE_COLLATE_FILENAME={~collationName~|database_default} |FILETABLE_PRIMARY_KEY_CONSTRAINT_NAME=~constraintName~ |FILETABLE_STREAMID_UNIQUE_CONSTRAINT_NAME=~constraintName~ |FILETABLE_FULLPATH_UNIQUE_CONSTRAINT_NAME=~constraintName~ |SYSTEM_VERSIONING=ON [(HISTORY_TABLE=~schemaName.historyTableName~ [, DATA_CONSISTENCY_CHECK={ON|OFF}])] |REMOTE_DATA_ARCHIVE={ ON [(~tableStretchOptions~)]|OFF ( MIGRATION_STATE=PAUSED)} |LOCATION=~locationOrPath~ |DATA_SOURCE=~externalDataSourceName~ |FILE_FORMAT=~externalFileFormatName~ |REJECT_TYPE=~value~ |REJECT_VALUE='~value~ |REJECT_SAMPLE_VALUE=~rejectSampleValue~ |REJECTED_ROW_LOCATION='~location~'])and SQL Settings / Data Providers to:
partitionScheme.sql: SELECT name FROM sys.partition_schemes
partitionSchemeOrFileGroup.sql: SELECT name FROM sys.filegroups UNION SELECT name from sys.partition_schemes
fileGroup.sql: SELECT name FROM sys.filegroups
collationName.sql: SELECT name FROM sys.fn_helpcollations()
this one needs the empty lines between. I am not sure if the queries are really fine. The CREATE TABLE syntax is
CREATE TABLE
{ database_name.schema_name.table_name | schema_name.table_name | table_name }
[ AS FileTable ]
(....)
[ ON { partition_scheme_name ( partition_column_name )
| filegroup
| "default" } ]
[ TEXTIMAGE_ON { filegroup | "default" } ]
[ FILESTREAM_ON { partition_scheme_name
| filegroup
| "default" } ]
[ WITH ( <table_option> [ ,... n ] ) ]and I don't know how to get the partion_column_name.
See this in action in the Table Dialog / Options Tab / Suffix.
Daniel-Pavic
Dear dbschema-Team,
we recently purchased the Pro Edition of dbschema. After working for more than a decade with different ERD-Tools I might be a bit spoiled - but the pro version lacks (IMHO) of quite some relevant features (if I did not miss something):
One of the most "severe" one - performancewise - is the ability to assign a table to a specific filegroup - or to assign a text-filegroup for (n)varchar(MAX)-colums using the physical modeler (SqlServer)
The only option I see is to disable the "GO"-Statement after each table creation and to put the following Append Script (Options) after each and every table within the ERD:
ON [my_filegroup] TEXTIMAGE_ON [my_filegroup_txt] GO
This isn't very handy - especially having lots of tables and the need to rename a filegroup.
Is there any other way to obtain the assignment of a table to a filegroup (which is pure physical modeling imho ;) There are also no filegroups to maintain or select within dbschema, right?
Thank you in advance for your reply! Best regards, Daniel