User profile for Chris Auckland

The author of this post and I exchanged a few emails to try and get to the bottom of this, and it seems that a combination of the identical object names, and having IF EXISTS statements in the procedure/function code has caused this. We have logged a bug for this issue (SC-4539), and have scheduled it to be fixed in SQL Compare 8.2 I hope this information is helpful for anybody else that might encounter this. / comments

The author of this post and I exchanged a few emails to try and get to the bottom of this, and it seems that a combination of the identical object names, and having IF EXISTS statements in the proc...

0 votes

Thanks for your post. We have had a few users report this now with SQL Data Compare 8, but we have so far been unable to reproduce it here. I have opened a private support ticket for you with regards to this issue, so I will contact you through that to try and gather a bit more info. Hopefully we will get to the bottom of this before too long. / comments

Thanks for your post. We have had a few users report this now with SQL Data Compare 8, but we have so far been unable to reproduce it here. I have opened a private support ticket for you with regar...

0 votes

Thanks for your post. The method of using multiple <exclude> is the way I would do it. I'm not aware of a limit that would cause a problem. E.g. <exclude>StoredProcedure:\[taRequesterItem0\]</exclude> <exclude>StoredProcedure:\[RequesterVariableAllocation1\]</exclude> Let me know if you have any problems. / comments

Thanks for your post. The method of using multiple <exclude> is the way I would do it. I'm not aware of a limit that would cause a problem. E.g. <exclude>StoredProcedure:\[taRequesterItem0\]</exclu...

0 votes

Thanks for your post. This issue is specific to SQL 2008, but it is really a problem with our script reader. We are not handling the syntax to change/set the compression when a constraint is added. It is probably because when the constraint is created on the heap, it will inherit the compression state of the heap unless a different one is stated, and if a different state is chosen when the constraint is created it will change the compression on the heap. Therefore, when we compare the objects we only really need to check the compression state on the heap, as it will be the same as for the constraint. However, when it comes to the scripts, as in your case, it doesn't expect the compression to be set in the ALTER TABLE statement and reports a syntax error. This should be fixed in the next major version of SQL Compare (v9). The bug tracking code for this is SC-4501. If you move the 'WITH (DATA_COMPRESSION = PAGE)' on the constraint to the create table statement, the script should parse. With regards TFS 2008, we don't technically support it, but as long as TFS 2008 is SCCI compliant, then it should work. You might need to install the SCCI provider plug-in. I hope this is helpful. / comments

Thanks for your post. This issue is specific to SQL 2008, but it is really a problem with our script reader. We are not handling the syntax to change/set the compression when a constraint is added....

0 votes

Thanks for your post. Does the script generated in SQL Data Compare 8 fail on your German servers? The reason I ask is because in SQL Data Compare 8 we added a line to the top of the script to set the date format, so that a difference in a servers date format wouldn't break the script. We now add the line: SET DATEFORMAT YMD GO The incorrect date format was a a known issue in version 7, but it shouldn't be a problem now in v8. I hope this helps. / comments

Thanks for your post. Does the script generated in SQL Data Compare 8 fail on your German servers? The reason I ask is because in SQL Data Compare 8 we added a line to the top of the script to set ...

0 votes

Thanks for your post. This feature has been on our wish-list for a while, and we hope to add it in the next major version. However, we don't have a current schedule for the next version. For your reference, the feature tracking code for this is DT-289. / comments

Thanks for your post. This feature has been on our wish-list for a while, and we hope to add it in the next major version. However, we don't have a current schedule for the next version. For your r...

0 votes

Thanks for your post. You can't exclude the identical objects when printing directly from the UI, but you can exclude the identical objects when generating a comparison report. To do this, uncheck 'Also include identical objects' from the 'generate Comparison results' dialogue. (Tools > Generate Comparison Results report). You can then print the report from the application you open it in. I hope this is helpful. / comments

Thanks for your post. You can't exclude the identical objects when printing directly from the UI, but you can exclude the identical objects when generating a comparison report. To do this, uncheck ...

0 votes

Why don't update this information on SQLCompare "Switches used in the command line" help. Please update the same. This will be updated shortly; we forgot to update the documentation with the new feature when SQL Compare 8.1 was released. / comments

Why don't update this information on SQLCompare "Switches used in the command line" help. Please update the same. This will be updated shortly; we forgot to update the documentation with the ne...

0 votes

There is some information on using filters in the UI helpfile. All you really need to do for the CL, is to build a custom filter through the UI, save it, and then reference it using /filter e.g. /filter:"D:\SQL Compare filter\myFilter.scpf" / comments

There is some information on using filters in the UI helpfile. All you really need to do for the CL, is to build a custom filter through the UI, save it, and then reference it using /filter e.g. /f...

0 votes

Thanks for your post. You don't need to do anything special to include all tables containing Log. The first example (/Include:table:Log) should include tables: Log LogA LogB New_Log If you only want a specific table, i.e. 'LogTest' you will need to use: /Include:table:\[LogTest\] If are looking to only include tables with a certain schema/owner, i.e. Log.Table_A Log.Table_B Then you will need to add a filter for the 'Log' schema/owner to the project. You can create a filter through the UI, and then reference it through the command line using /filter: I hope this is helpful. / comments

Thanks for your post. You don't need to do anything special to include all tables containing Log. The first example (/Include:table:Log) should include tables: Log LogA LogB New_Log If you only wan...

0 votes

How can we help you today?

Chris Auckland

Comments