User profile for David Pond

Hi, We're planning to release the new version towards the end of March, there're still improvements we'd like to make. There will be opportunities to try early releases of SQL Search, for example we're keen to check the upgrade experience is smooth. If you'd like to try these early builds then please send me a PM with your e-mail address. The build for Lemosj was to fix the specific problem he was experiencing, but there were no new features in that build. And I'd prefer it was not widely distributed because it may prove incompatible with future releases. Best wishes, David / comments

Hi, We're planning to release the new version towards the end of March, there're still improvements we'd like to make. There will be opportunities to try early releases of SQL Search, for example w...

0 votes

Hmm... that's very odd. It's a long shot but did you uninstall SQL Search before reinstalling it? We've just started doing some work on SQL Search, we haven't released anything yet, but you could try an early build. [download URL removed] Let me know how you get on [david.pond@red-gate.com]... If it doesn't work hopefully we'll have a stable early access release available soon. / comments

Hmm... that's very odd. It's a long shot but did you uninstall SQL Search before reinstalling it? We've just started doing some work on SQL Search, we haven't released anything yet, but you could t...

0 votes

Are you using SQL Search v1.1.9? This version will not work in SSMS 2014. Sorry I thought maybe we had bumped the beta build versions to v1.9. You need to install the SQL Search beta from here: http://documentation.red-gate.com/displ ... eta2update You should probably join the beta mailing list too, so they let you know when it is released. / comments

Are you using SQL Search v1.1.9? This version will not work in SSMS 2014. Sorry I thought maybe we had bumped the beta build versions to v1.9. You need to install the SQL Search beta from here:http...

0 votes

If you installed SQL Search before installing SSMS 2014 you need to follow these instructions. http://documentation.red-gate.com/displ ... ent+Studio Let me know if that doesn't work for you. / comments

If you installed SQL Search before installing SSMS 2014 you need to follow these instructions.http://documentation.red-gate.com/displ ... ent+Studio Let me know if that doesn't work for you.

0 votes

The current beta builds should support SSMS 2014, you could join the beta program advertised at the top of the forum. Or wait for the release scheduled for the end of March. / comments

The current beta builds should support SSMS 2014, you could join the beta program advertised at the top of the forum. Or wait for the release scheduled for the end of March.

0 votes

Hi Joseph, You can join our Google group where we're discussing the development of migrations v2 here: https://groups.google.com/group/red-gate-migrations We've just released an early access build of SoC to demonstrate the approach we're considering. David / comments

Hi Joseph, You can join our Google group where we're discussing the development of migrations v2 here: https://groups.google.com/group/red-gate-migrations We've just released an early access build ...

0 votes

Snapshots only capture the database schema, so the addtional migration information is not available when comparing snapshots. The current implementation of Migrations requires a connection to your version control system. To generate a deployment script that includes your migrations you should compare revisions from SQL Source Control that are equivalent to the state of the deployed database. You might find some of the resources on this page interesting: http://www.red-gate.com/products/sql-de ... tegration/ I'm working on revising our approach to migrations at the moment, to improve branching and support Git and Mercurial. I'd love to get your feedback if you have time - I'll send you an e-mail. David Pond Software Engineer / comments

Snapshots only capture the database schema, so the addtional migration information is not available when comparing snapshots. The current implementation of Migrations requires a connection to your ...

0 votes

Just to clarify the "deprecated" issue, since this is all my fault. :oops: I initially decided to mark /migrationsfolderxml as deprecated because in the use-case I imagined it made more sense for people to use /migrationsfolder. But the feedback suggests that /migrationsfolderxml is actually more useful. I also accidently marked /scriptfolderxml as deprecated, it is not. We know this is a complicated part of the commandline and the plan is to improve this area as soon as possible (next month?). / comments

Just to clarify the "deprecated" issue, since this is all my fault. :oops: I initially decided to mark /migrationsfolderxml as deprecated because in the use-case I imagined it made more sense for ...

0 votes

Hi Robert, I've sent you an e-mail with a possible solution. We will be supporting this feature in SQL Compare 10.1 which will be released in the next couple of weeks. David / comments

Hi Robert, I've sent you an e-mail with a possible solution. We will be supporting this feature in SQL Compare 10.1 which will be released in the next couple of weeks. David

0 votes

I sent RobVK an early build of SQL Compare with a description of some new commandline switches. These switches are now in the current release of SQL Compare (see below). We're working on an easy to use solution, but you can get started with these commands. This is the landing page for information on CI for databases. http://www.red-gate.com/products/sql-de ... tegration/ RobVK needed to checkout his migrations folder and use the /migrationfolder switch. The /scriptsfolderxml switch is also required because SQL Compare will need to make additional checkouts from the version control system. /abortonwarnings: none | medium | high Sets the warning level at which SQL Compare command line will abort. /assertidentical Returns exit code zero in the event both database schemas are identical. This can be used at the end of the CI process to confirm that the local copy of the production DB has been successfully updated. /migrationfolder This is a path to a directory containing the migration scripts to be used. /migrationfolderxml [deprecated] /migrationfolder should be used instead of this option. By allowing the CI system to check out the migrations folder it can display information about recent commits. /revision1, /revision2 When used with /scripts, it allows SQL Compare to identify the correct migrations scripts. This is necessary because a script folder does not contain information on which revision it is. When used with /sourcecontrol it also specifies which revision will be checked out by SQL Compare. /scriptfolderxml This is a path to a text file that contains an xml fragment which describes a connection to a VCS. This fragment can be copied from the extended properties of a live database connected to SQL Source Control. /versionusername1, /versionpassword1 These are you username and password to connect to the VCS system. This is required when using /sourcecontrol or when migration scripts are being used. Sample from a Nant script: <target name="generate_upgrade_script_schema"> <exec program="${sqlcompare.executable}" resultproperty="returncode" failonerror="false"> <arg value="/scripts1:"${latest.scriptsfolder}""/> <arg value="/revision1:${latest.revision}"/> <arg value="/sourcecontrol2"/> <arg value="/revision2:${production.revision}"/> <arg value="/scriptsfolderxml:${repo.location.xml}"/> <arg value="/migrationfolder:${migration.folder}"/> <arg value="/AbortOnWarnings:high"/> </exec> </target> / comments

I sent RobVK an early build of SQL Compare with a description of some new commandline switches. These switches are now in the current release of SQL Compare (see below). We're working on an easy to...

0 votes

How can we help you today?

David Pond

Comments