Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When importing programmable objects into your database SQL Change Automation project for the first time, you may notice that one or more scripts are placed into a folder called Unsupported, instead of the usual Programmable Objects folder. This can happen to a script containing a stored procedure/view/user defined function object if one or more of the following applies:

...

Changes to both the function, as well as the computed column that uses the function, can then be made by simply editing the programmable object file and deploying the database SQL Change Automation project.

Anchor
ScenarioC
ScenarioC
Scenario C: Security Policies with dependencies on Functions

...

Changes to both the function, as well as the security policy that uses the function, can then be made by simply editing the programmable object file and deploying the database SQL Change Automation project.

Anchor
ScenarioD
ScenarioD
Scenario D: Deploying natively-compiled objects 

...