Hi,

Here is a catch 22 case. We had 2 triggers we created several months ago and

then deleted them. SQLDBControl has them checked as deleted. Today I created

those 2 triggers again under SQL Server Management Studio but with

completely different logic than the original ones. When I get back to

SQLDBControl and try to get them from the server, the get latest from server

option is disabled because SQLDBControl did not check again to see if these

exist on the server. Apparently what SQLDBControl does is to check its

database and if the objects are in there then it does not check the server.

This is not right. SQLDBControl should always check the server for the

existence of the object if the object does not exist in the SQLDBControl

database or it has been deleted from it as is in my case.

 

Regards,

Costas

---

SQLDBcontrol Support

support@sqldbcontrol.com

Hi Costas,

Thanks for highlighting this situation.  Checking the server for the existence of the object is possible but could affect performance when loading a big list of objects for display in the summary list.  As such, how about we enable the Get Latest from Server option for deleted objects?

In this instance, the act of getting the latest from server will automatically un-mark the deleted state of the object.  If the object you're trying to get the latest for does not exist then we could provide you with a dialog box and option to recover the deleted object instead.

Does that sound like a reasonable option that would work for you?

---

SQLDBcontrol Support

support@sqldbcontrol.com