|
Sunday, 01 July 2007 |
|
Here you will find some technical information of Sync For SQLServer. If you cannot find the answer to your technical question here and in our FAQ please do not hesitate to contact us at info [AT] SleepyAnt [DOT] com.
It is very important for us to have your feedback.
Technical RequirementsRequirements: - Windows XP, Windows Vista or Windows 2003 Server
- Microsoft .NET Framework 2.0 (Be sure to have the .NET Framework installed before installing Sync For SQLServer)
- Crystal Runtime (included in the download package, or the Sync For SQLServer page)
You can download the .NET Framework from the Microsoft website here Sync For SQLServer 1.5- Microsoft Office 2005 style
- Small Object Explorer like in SQL Server
- SQL syntac based Difference View for objects like in WinDiff
- Workspace Explorer to administer your files for a database update packacke.
- Output window to view actions or messages.
- Tables present in the data source and missing in the destination will be added to the destination including indexes, unique keys, primary keys and foreign keys.
- Tables present in the destination and missing in the data source will be removed with its constraints in the destination.
- Tables which are different will be altered. Or if this is not possible unloaded into a tmp table, dropped, added with the new schema and again loaded from the tmp table. All foreign keys are added in the correct order. Default values (any kind of SQL expression) can be defined for new table columns.
- Default value information for columns in a destination DB table is archived in an XML file for future update uses. You can put them under source control. Your "default value knowlege" thus wont be lost.
- The change script includes user tables with its constraints, default values, extended properties, checks, user defined types, user defined functions, stored procedures and views.
- The change script can contain transaction code according to your selected options.
- SQL editor with syntax highlighting for editing the SQL scripts.
- Running the change script and data migration scrips with detailed output of the results.
- Data Migration one of the core features. Pure SQL script based.
- Data Migration control file determines an execution order for the data migration scripts. Database dependencies are resolved into a linear list.
- Data Migration Settings XML file. You can save your settings or put it under source control.
- Very simple, just a few clicks.
|
|
Last Updated ( Tuesday, 04 November 2008 )
|