Automate and integrate using the SQL comparison API
Moderators: Chris Auckland, David Atkinson, Michelle Taylor, chengvoon.tong
There's a slight bug when generating an output script in the case of foreign keys which affects formatting (and in our case, parsing the script).
When generating a comparison script between tables with foreign keys, you get the below sample results.
PRINT N'Dropping foreign keys from [dbo].[tblTable2]'
ALTER TABLE [dbo].[tblTable2] DROP CONSTRAINT[FK_NamedId]
PRINT N'Dropping constraints from [dbo].[tblTable]'
ALTER TABLE [dbo].[tblTable] DROP CONSTRAINT [df]
PRINT N'Dropping constraints from [dbo].[tblTable3]'
ALTER TABLE [dbo].[tblTable3] DROP CONSTRAINT [df_tblTable2_value]
If you look closely, you can see that DROP CONSTRAINT [...] has a space between CONSTRAINT and the bracketed object name. When it generates the script for foreign keys, it does not have a space, and CONSTRAINT and the '[' are next to each other. This doesn't prevent the script from running, but does interefere with our parsing routines that occur on the generated script which is expecting to find a space between them. If this could be resolved that would be appreciated.
- Posts: 28
- Joined: Sun Apr 01, 2012 5:24 am
Thanks for pointing this out. I've logged a bug, reference SC-5727 to get it looked at.
I can't make any promise of timescale, however if it's a simple fix it may be possible to get done quite quickly.
- Posts: 1144
- Joined: Wed Jun 16, 2010 11:10 am
- Location: My desk.
Return to SQL Comparison SDK 10
Who is online
Users browsing this forum: No registered users and 0 guests