Exclusions

• 
  Hi @DBADave !
  
  I'm afraid it's not possible to exclude a folder at the moment. Can you please add a feature request for this on our uservoice forum? https://redgate.uservoice.com/forums/141379-sql-compare
  
  Just to confirm though, are you mainly looking to exclude static data? You should be able to do this via the  /Include:StaticData switch.
  
  >>If not, then what's the /exclude:Table syntax to exclude any table starting with a #
  
  Just to confirm, do you mean temporary tables in a pre/post deployment scripts?
  
  

  Jessica R December 11, 2019 01:57

  - 0 +
• 
  @DBADave - what are you trying to achieve? Are you just needing to deploy schema changes and not static data? If so, can you explain why?

  David Atkinson December 11, 2019 10:16

  - 0 +
• 

  Jessica R said:

  Hi @DBADave !
  
  I'm afraid it's not possible to exclude a folder at the moment. Can you please add a feature request for this on our uservoice forum? https://redgate.uservoice.com/forums/141379-sql-compare
  
  Just to confirm though, are you mainly looking to exclude static data? You should be able to do this via the  /Include:StaticData switch.
  
  >>If not, then what's the /exclude:Table syntax to exclude any table starting with a #
  
  Just to confirm, do you mean temporary tables in a pre/post deployment scripts?
  
  

  Yes, it's to ignore scripts with # or ## table names in them.  These are sometimes created for data migration purposes and developers often use the same #table names in multiple scripts.

  DBADave December 11, 2019 10:30

  - 0 +
• 

  David Atkinson said:

  @DBADave - what are you trying to achieve? Are you just needing to deploy schema changes and not static data? If so, can you explain why?

  I'm trying to compare my local Git repository with a database.  When building the snapshot if there's multiple files in my Scripts folder that contain a reference to the same #temp table then the snapshot creation fails.

  DBADave December 11, 2019 10:33

  - 0 +
• 
  @DBADave - In your opinion should the snapshot creation succeed (ie, is this a bug in SQL Compare) or do you think these #temp tables shouldn't be used in your scripts?

  David Atkinson December 11, 2019 12:23

  - 0 +
• 
  @David Atkinson - Yes I think the snapshot should succeed as these scripts are manipulating data rather than creating database objects.  Would it be fair to say if the static data exclusion is used then these files would get ignored if they were in the StaticData folder?

  DBADave December 11, 2019 13:10

  - 0 +
• 

  DBADave said:

  @David Atkinson - Yes I think the snapshot should succeed as these scripts are manipulating data rather than creating database objects.  Would it be fair to say if the static data exclusion is used then these files would get ignored if they were in the StaticData folder?

  I would _guess_ that the contents of the Data folder would be ignored if this option is used. Howevever, if this turns out to be a SQL Compare bug, it might be best to open a support ticket, particularly if you can attach the simplest example of a failure case scripts folder, as having something reproducible makes it easier for us to consider a fix.

  David Atkinson December 11, 2019 13:43

  - 0 +
• 

  Jessica R said:

  Hi @DBADave !
  
  I'm afraid it's not possible to exclude a folder at the moment. Can you please add a feature request for this on our uservoice forum? https://redgate.uservoice.com/forums/141379-sql-compare
  
  Just to confirm though, are you mainly looking to exclude static data? You should be able to do this via the  /Include:StaticData switch.
  
  >>If not, then what's the /exclude:Table syntax to exclude any table starting with a #
  
  Just to confirm, do you mean temporary tables in a pre/post deployment scripts?
  
  

  Yes, it's to ignore scripts with # or ## temp table definition.

  DBADave December 13, 2019 11:12

  - 0 +

Add comment

Please sign in to leave a comment.