How can we help you today? How can we help you today?
rgribble
I think there may be some confusion over terms here... i have noticed alot of people say "check out" when they arent actually checking out a file to edit it... they really should say "synch" or "get". The idea of using SQL Compare 6's new script folder abilities to "build" a database is one i am looking forward to as well... like Granted, i have an inhouse build routine which essentially takes all of the database scripts and "builds" them into an empty staging database, that can then be snapshotted and/or used as a source to synchronise schema changes to a live DB. Currently my DB build is pretty dumb... it just uses a queued approach and hammers scripts at the staging database, if one fails it gets requeued at the end and tried later... It works for the most part but is ugly and inefficient. But i didnt want to get into the nitty gritty of actually interpretting the script files and figuring out some kind of dependancy order. I plan to change my build routine to create the empty database, then use SQL Compare 6 to compare the script folder source, to the empty database, and synchronise all changes across. I can let redgate worry about the dependancies and order that the objects need to be created! [image] We use the SQL Compare Toolkit edition (c# libraries to use in our .NET apps) to do this kind of thing here, but i believe that the "Pro" edition of SQLCompare supports commandline invocations as well, so that may be what you can do Granted. I agree with David, in terms of building a database from the scripts, no integration with source control on the part of RedGate itself is strictly necessary... most of us would probably have our existing build scripts or visual build applications like Visual Build Pro, FinalBuilder etc, anyway, and these can handle synching to the desired label/revisions of scripts and creating the empty database, before invoking redgate to do the actual "build". Then assumedly there are cleanup steps afterwards that our build script will do too. In my case this is comparing the built database to the snapshot stored in perforce, and if this is different checking out the snapshot and generating a new one ready to check back in. These tasks are accomplished by an application i wrote, which uses the SQLToolKit libraries / comments
I think there may be some confusion over terms here... i have noticed alot of people say "check out" when they arent actually checking out a file to edit it... they really should say "synch" or "g...
0 votes
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