Suggestion: list SQL errors before synchronisation

• 
  Thanks for the suggestion. Correct me if I'm wrong, but I'm guessing that many of the errors you refer to are due to "invalid objects" that reference other objects that no longer exist or have been renamed?
  
  The good news is that we are hoping to add a feature to SQL Prompt that will identify such objects, allowing you to fix all the problems in your database in one go.
  
  Kind regards,
  
  David Atkinson
  Red Gate Software

  David Atkinson February 22, 2010 07:37

  - 0 +
• 
  Hi David
  
  Objects that no longer exist or have been renamed pretty much sums it up.
  
  Glad to hear that SQL Prompt will fix it in the future. However, it would also be useful to be able to run a check from SQL Compare because that's where the problem will be mercilessly exposed.
  
  Crispin

  CrispinH February 22, 2010 07:54

  - 0 +
• 
  Good point. I hadn't really thought about it from that point of view. It might well be worth our while putting the functionality into both tools.
  
  David

  David Atkinson February 22, 2010 08:03

  - 0 +
• 
  I generally work around this problem by taking the script and running it in SSMS, which will tell me all the errors (although sometimes with some bonus ones from previous operations being rolled back).

  Michelle T March 03, 2010 11:35

  - 0 +

Add comment

Please sign in to leave a comment.