July 3, 2011 at 1:42 am
Hi everyone,
Recently, an application team requested me to restore a database from development to production. Now they have the same permissions on both the environments, enough to script out the stored procedures.
Now after restoration, they are not able to access the sprocs as it shows a little lock symbol and gives the "property textheader is not available for stored procedure....text is encrypted." After little research I found this error occurs when the sprocs are encrypted.
But then I am surprised they are able to access the sprocs on the dev server. I tired to restore a copy of the same database on our DBA test servers and created a login with similar permissions. I was able to access them on a server with SQL Server 2005 SP4 but I got the same issue with SQL Server 2005 SP3.
The dev server is SQL Server 2005 SP4 while the Prod is SQL Server 2005 SP3, so this is consistent with my findings. Can anyone let me know if its a known issue or if there is any article related to this. I want to persuade them to apply SP4 earlier than scheduled.
Still worse, is this a bug in SP4 where it is allowing the user to script out encrypted sprocs??
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply