How can we help you today? How can we help you today?
rgribble
hopefully that includes file extensions other than .sql files as well? / comments
hopefully that includes file extensions other than .sql files as well?
0 votes
Adding to these comments, it would be great if there could be options for how to name the scripts, and whether to create a subdirectory heirarchy underneath the given folder. Currently all scripts are created as [dbo].[object].sql I would prefer to name them without the brackets, and im sure others again would prefer not to have the dbo at all. I also dislike using .sql as the extension for everything... we use different extensions for different object types, such as .TAB for table, .PRC for stored proc, .UDF for function and so on (these file extensions come originally from enterprise manager, but we have extended/expanded this and defined our own extensions for 2005 objects too, such as ASM for assembly, SYN for synonym, XSC for XmlSchemaCollection etc). We also like to store our objects in subfolders root folder /Functions /StoredProcedures /Tables /Views and so on. I think ultimately you could provide users with a fair amount of flexibility by giving us a settings page allowing us to specify a file extension, and subfolder for each object type. This would allow users like Andrew to put all 200 objects in the root folder, and 2005 objects in a single subfolder, and having all files with a .sql extension, while allowing those like myself to configure a separate directory and file extension for each object type! There should also be a global option for the filename part of the scripts - should they contain the owner/schema, should they have square brackets, maybe they should all be prefixed with the database name and an underscore. This could be implemented in a similar way to the arguments field in the application options, when specifying a custom program to view SQL scripts, by using placeholders like %SO% for schema/owner, %ON% for object name, %DN% for database name etc [%SO%].[%ON%] = [dbo].[ObjectName] %DN%_%SO%.%ON% = Database_dbo.ObjectName etc... very flexible! Supporting these kind of options will make this new feature infinitely more usable to a larger amount of your users / comments
Adding to these comments, it would be great if there could be options for how to name the scripts, and whether to create a subdirectory heirarchy underneath the given folder. Currently all scripts ...
0 votes