We have some databases which use encrypted stored procedures, however when differencing them with DBGhost the result is that the delta script drops the stored procedure from the target database, even if it has not changed. Is there any way of ignoring encrypted stored procedures so we can handle them separately?
Graham McPhee *Senior Configuration Manager* Cirrus House Configuration Management Team NHS National Services Scotland
In the latest version of the CompAndSync DLL (the engine behind the Change Manager) there are options to encrypt objects on the target database dynamically during the sync and delta script creation.
This means that you can have all stored procedures etc. in clear text on the source and let Ghost handle all the encryption on-the-fly thus saving you any manual workaround for encrypted objects.
Would that work for you?
regards,
Malcolm Leach www.innovartis.co.uk DB Ghost Build, Compare and Synchronize = Change Management for SQL Server
We currently only need a handful of stored procedures encrypted and ideally an option to not script the difference between encrypted stored procedures would have been ideal. However if you can supply the link to the latest version we will try that out.
Graham McPhee *Senior Configuration Manager* Cirrus House Configuration Management Team NHS National Services Scotland
Stored Procedure Encryption
Posted - 06/05/2008 : 04:31:50
Posted - 06/05/2008 : 04:33:55
