RE: Storing source as DDL instead of DDS

Backups. I put the risk assessment for your scenario to be very low. I think you're tremendously more at risk by keeping source that IMO has a high likelihood of being out of date.



-----Original Message-----
From: Birgitta Hauser [mailto:Hauser@xxxxxxxxxxxxxxx]
Sent: Saturday, February 25, 2017 5:01 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: Storing source as DDL instead of DDS

We don't have any reason to keep DDL source at all.

What happens if a DDL described database object gets lost, i.e. an Index or a view or even worse an view based on multiple views gets deleted.
What if a trigger or constraint is deleted?

How will you recreate it, if the object does no longer exist, so reverse engineering is no longer possible?

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"
"Train people well enough so they can leave, treat them well enough so they don't want to." (Richard Branson)