5940
by pmcevoy
|
May 12 2010
2:53 PM
|
Being evaluated
|
Further to my suggestion on http://sqlazuremw.codeplex.com/Thread/View.aspx?ThreadId=212421 I'm submitting this patch to ScriptDatabase.cs based off 45611 source changeset. It's pretty basic: if the BCPDataDir appsetting is specified, then we'll use that directory as the location to output BCP files, and each file will be the name of the table that the we are creating the dump for. (eg Users.bcp for table called Users). If the setting is not specified, then we use the legacy behaviour
|
|
Download
|
7005
by joshmaletz
|
Oct 6 2010
5:53 PM
|
Applied
|
Added features: - Added command-line batch TSQL file migrator. Will take the dbproj tsql output file, or any tsql file, and create the azure deploy script. - Added ability to remove a parsed not-supported command from the output script entirely. "RemoveCommand" bool attribure in NotSupportedByAzureFile.config.
Required code changes: - I moved the ScriptDatabase, NotSupportedByAzureFile.config, and SMOScriptOptions to the Utils project - I added a file, TsqlFileMigrator, to the utils project as well, which contains all the logic moved from the ScriptWizard to parse the tsql file. - I then added an interface, IMigrationOuput, and added a console class, ConsoleMigrationOutput, to the utils project. The existing ScriptWizard now implements implement it as well. This just directs the sql analysis and script output to the correct destinations. This allowed me to not pass the ui to the TsqlFileMigrator, but rather the migration output instance which contains the delegate for writing the output accross threads. - I also added an enum for the function codes.
:
Took suggested changed and put them in SQLAzureMW v3.4
|
|
Download
|